Privacy policy
Last updated: 2026-11-14
This Privacy Policy explains what EFRAZ SAL (“Efraz”, “we”, “us”) collects when you use the Efraz website, map and related services, why, and what you can do about it.
The English version of this document is the binding one. The Arabic version is a translation provided for convenience only; where the two differ, the English version applies.
1. Who we are
The data controller is EFRAZ SAL, Qubic Center, 6th floor, Daoud Amoun Street, Herch Tebit, Sin El Fil, Lebanon, reachable at [email protected]. Full company details are on the Legal notice page.
2. What we collect
- Account data — email address, password (stored only as a hash by our authentication provider), and phone number, when you register; your Google account’s basic profile if you choose Google sign-in.
- Sign in with Apple — if you sign in with Apple, we keep the token Apple issues, encrypted, so we can tell Apple to disconnect efraz from your Apple ID when you delete your account. It is deleted with your account.
- Verification data — your phone number and the fact (not the content) of successful verification, when you verify by one-time code.
- Transaction data — the credit packs you buy, your credits, and the parcels you have revealed. For a Whish Pay purchase this includes the amount, the payment reference, and the Whish phone number that paid. For cash paid at a Whish Money branch it includes the amount, the payment reference, Whish’s transaction, branch and employee references, and the time Whish took the cash. For a card purchase it includes the amount, the payment reference, Cybersource’s own transaction number and result code for the payment, and the card’s brand and last four digits, and nothing else about the card.
- App Store purchases — when you buy credits in the efraz iPhone app, Apple tells us the product, its price and currency, and a transaction reference. We never see your card or your Apple account details.
- Card payment details — when you pay with our own card form, the name on the card and the billing address you type pass through our server on their way to Cybersource (Section 4); we keep them only if you choose to save your billing address. If you choose to save a card, we keep its brand, last four digits and expiry date and Cybersource’s references for the stored card. Cybersource stores the card itself; its number and security code never reach us.
- Contact data — name, email, phone number and message content when you write to us through the contact form, the support chat or by email.
- Usage data — first-party analytics about how the Service is used. When you are signed in this includes which towns and parcels you view, how often and for how long, the approximate area of the map you are looking at (rounded to about 100 metres), the places and lots you pick in search, how you reached each parcel, when you open the dialog to reveal a parcel (including when you do not go on to buy), and the time you spend in the app, and which map tools you open and finish using, such as the ruler, the building planner, the 3D view or the export, but never the lines, shapes or places you draw with them.
- Search targets — for everyone, signed in or not, the place or lot a search resolves to.
- Technical data — IP address, browser and device information, processed on our behalf by the infrastructure providers listed in Section 4 to deliver the Service.
3. What we do not collect
We do not receive or store payment card numbers or your Whish account credentials — Whish payments are handled by Whish Money (Section 4). Card payments are handled by Cybersource and NetCommerce (Section 4): your card number and its security code go from your browser straight to Cybersource and never reach us. We do not run advertising trackers, and we do not sell your personal data.
We do not store the free text of what you type into search — only the place or lot it resolved to. The behavioural interest data described in Section 2 is never sold, and it is not shared with anyone outside Efraz other than the service providers listed in Section 4 who host it on our behalf; we use it only inside Efraz.
4. Who processes data for us
Each provider processes data under its own terms and privacy policy. We share only what each integration needs to function.
When you buy credits with Whish Pay, we send Whish Money only the amount and a payment reference. Whish sends back the phone number of the Whish account that paid; we keep it with the payment record for support and accounting, also after you delete your account (Section 7).
When you pay cash at a Whish Money branch to buy credits, the branch employee enters your phone number and we tell Whish Money the name and email on the efraz account that holds it, so the employee can confirm the account with you before taking your cash. A lookup or a branch payment can also tell Whish Money that the account is suspended or not yet fully set up. Whish then sends us the amount, its own transaction, branch and employee references and the time it took the cash; we keep them with the payment record for support and accounting, also after you delete your account (Section 7). We keep a record of each such lookup, and of each branch payment we refuse because the number has no account we can credit (a one-way code of the phone number, the result and the time) for 180 days. After a branch payment, and when a branch asks to cancel one, we also tell Whish Money how many credits the account then holds. If a branch asks to cancel a payment after you have deleted your account, we tell Whish Money that the account was deleted.
When you buy credits by card, your card number and its security code are typed into fields that Cybersource runs on the Buy credits page. They go from your browser straight to Cybersource and never pass through our server, and your browser sends the card’s expiry date to Cybersource with them. The page shows one of two card forms. In our own form, only the card number and security code boxes are Cybersource’s. The expiry date reaches our server only inside the signed card token that Cybersource gives your browser; the token also holds the card’s brand and last four digits, and we hand it back to Cybersource to make the payment. With this form we send Cybersource the amount, the currency, a payment reference, the name on the card, your billing address (address lines, city, state, country and postal code) and your account’s email address. For your bank’s check of the payment we also send your IP address and these details of your browser: its Accept and User-Agent headers, its language, your screen’s size and colour depth, your time zone offset, and whether Java and JavaScript are switched on. In the other form, the whole card form is Cybersource’s: what you type into it goes straight to Cybersource and not to us, and what we send Cybersource about the purchase is the amount, the currency, a payment reference and the language of the page; nothing in it names you or your account.
Cybersource tells us whether the payment went through and gives us its own transaction number and result code; we keep those with the payment record for support and accounting, also after you delete your account (Section 7). We do not store your full card number or its security code. We store the card’s expiry date, the name on the card and your billing address only if you choose to save them, as described below. When our server asks Cybersource about a payment, the answer can include the card’s brand, its last digits and the billing details; we read the payment’s result from it, keep the card’s brand and last four digits with the payment record so your receipts can show which card paid, and keep none of the rest.
On our own card form you can choose to save your billing address, your card, or both, for later purchases. Nothing is saved unless you tick its box, and only once the payment is approved. If you save a card, Cybersource keeps the card number and its expiry date together with the name on the card, the billing address and the email address sent with that payment, and NetCommerce can see them as it sees other payment details. We keep the card’s brand, last four digits and expiry date, and Cybersource’s references for the stored card. If you save a billing address, we keep it together with the name on the card. A saved card is used only for a payment you start yourself, and that payment still asks for the card’s security code and your bank’s check; we never charge a saved card on our own. You can remove a saved card or a saved address at any time on your Profile page, and removing a card also deletes it at Cybersource. If we change how saved cards are used, we will announce it as Section 12 says.
Purchases in the efraz iPhone app go through Apple. If you ticked the box on the Buy credits page and later ask Apple for a refund, we tell Apple how many of that purchase’s credits you used and whether we think a full refund, part of one or none is fair, so Apple can decide the refund. If you did not tick it, we tell Apple nothing.
- Supabase — authentication and database hosting.
- Twilio — delivery of one-time verification codes by SMS or WhatsApp.
- Meta (WhatsApp) — when your code goes by WhatsApp, Twilio passes your phone number and the code to Meta’s WhatsApp service to deliver it.
- Resend — sends the emails efraz sends you, such as receipts and support replies, and the sign-in and sign-up emails; it receives your email address and the email’s content.
- DigitalOcean — hosts the server that runs efraz; everything you send to efraz passes through it.
- Google — sign-in, where you choose it.
- Apple — Sign in with Apple, where you choose it; purchases in the efraz iPhone app through the App Store; answers to Apple’s refund questions, where you ticked the box on the Buy credits page; and disconnecting efraz from your Apple ID when you delete your account.
- Mapbox and MapTiler — map imagery and tiles; your browser requests tiles directly from them, which discloses your IP address and browser headers to them.
- Cloudflare — hosting edge, security and delivery.
- Whish Money — processes online payments (Whish Pay).
- Cybersource — processes card payments and runs the card fields on the Buy credits page: either the whole card form, or the card number and security code boxes inside our own form. It receives your card number, its expiry date and its security code from your browser (with Cybersource’s whole card form, also the billing details that form asks for), your IP address and browser details, and from us the amount and a payment reference; with our own form we also send it the name on the card, your billing address and your account’s email address. To approve the payment it passes these to the card network and to the bank that issued your card, which may ask you to confirm the payment. If you choose to save a card, Cybersource stores it.
- NetCommerce — the payment company in Lebanon that provides our card service, which runs on Cybersource. Card payments reach us through NetCommerce, so it can see the same payment details as Cybersource.
- Sentry (Functional Software, Inc.) — error reports. When something breaks, Sentry receives the error details, the page address with personal values removed, your browser and device type, the app version, and your account number if you are signed in. Sentry stores no IP address, name, phone number or email, and keeps reports for 30 days.
- Anthropic — the AI behind efraz assistant on the support page. It receives what you write in a support chat and, when you are signed in, the account details the assistant looks up to answer you: your credits, your credit history, the parcels you revealed, your payments, and your earlier support requests with efraz’s replies. It never receives your password or the phone number that paid a Whish payment. Anthropic’s models also check each answer the assistant writes before you see it, and review support chats overnight, after each day they are used, to find answers that break efraz’s support rules.
- Telegram — when you open a new support ticket, a message goes to a private Telegram group read only by efraz staff. It carries the ticket’s reference, its category and a short summary of the problem, with email addresses and phone numbers removed. When the checks hold back one of the assistant’s answers, or the nightly review flags a chat, the message carries only the chat’s internal number and the rule concerned.
5. Why we process data (purposes)
- to create and operate your account;
- to verify your phone number and secure the Service;
- to process credit purchases and deliver Reveals;
- to respond to support requests;
- to prevent abuse, fraud and unpaid use;
- to understand aggregate usage and improve the Service;
- to understand which areas and parcels users are interested in — for internal market research and to develop future Efraz services, including real-estate-related services;
- to comply with legal obligations.
6. Cookies and local storage
We use strictly-necessary cookies for authentication sessions and to remember your language choice, and browser session storage for an anonymous visitor identifier that is discarded when you close the tab, plus local storage for interface preferences. That anonymous identifier is also recorded on the usage events we store, and ages out with them (Section 7). We do not use advertising or cross-site tracking cookies.
7. Retention
Account data is kept while your account is active. Raw usage events and server logs are kept for 180 days. The interest profile described in Section 2 is kept for as long as your account exists and is deleted when you delete your account. When you delete your account, associated personal data is deleted or anonymized, except records we must keep by law (for example, accounting records of purchases): your interest profile is deleted outright, and raw usage events still inside their 180-day window lose the link to your account.
Payment records — the amount, the payment reference, the status and its times, the Whish phone number that paid a Whish Pay purchase, and for cash paid at a Whish Money branch, Whish’s transaction, branch and employee references and the time it took the cash — and the entries for credits added and spent are kept for 10 years for accounting, also after you delete your account. A card purchase’s record also holds Cybersource’s transaction number and result code for the payment and the card’s brand and last four digits, and nothing else about the card. When you delete your account, we take your account (and with it your name and email) off those records. Unused credits are not kept for you: they are lost when the account is deleted. A separate audit entry noting that a credit purchase took place, and when, is also kept after deletion; it holds no amount and no phone number.
Saved cards and saved billing addresses are kept until you remove them on your Profile page or delete your account. When you delete your account, your saved billing addresses and our records of your saved cards are deleted at once, and the cards stored at Cybersource are deleted within a day. Until Cybersource confirms that, we keep only its references for those cards, with nothing that names you.
After you delete your account, we keep a scrambled form of your phone number. It cannot be turned back into the number, and it stops the same number getting a second sign-up bonus. The payment records kept after deletion stay linked to that scrambled form, so efraz can still find them from your phone number.
Messages you send us through the contact form are kept for 2 years, then deleted, whether or not you still have an account.
Support chats, the tickets they lead to, your ratings of the assistant’s answers, the record of what the assistant looked up, and the records of the checks on the assistant’s answers and of the nightly review of each chat are kept for 2 years after the conversation’s last message or reply, then deleted, whether or not you still have an account. When a ticket ends in a refund or a gift of credits, its short summary also stays in efraz’s record of changes to your credits, which is kept with your credit history.
Notes efraz staff write about an account, and the record of each time staff look up an account, are kept for 2 years after they are written, then deleted. When you delete your account, they lose their link to you at once.
8. Your rights
You may access, correct or delete your personal data. You delete your account yourself, while signed in, from your dashboard; the Delete your account page shows how. For your security, efraz staff cannot delete an account for you. Where Lebanese law — or, if it applies to you, another law such as the GDPR — grants additional rights (objection, portability, restriction), we honour them.
Efraz runs no advertising trackers, no third-party analytics and no advertising cookies. Error reports go to Sentry, listed in Section 4, an error-reporting service that sets no cookies. Efraz’s own usage analytics are first-party and fully disclosed here.
9. Security
We use TLS encryption in transit, hashed credential storage, scoped access controls and domain-restricted service keys. No system is perfectly secure; if a breach affects your personal data we will act as the law requires.
10. International transfers
Our providers process data outside Lebanon (including the United States and the European Union). By using the Service you consent to those transfers.
11. Children
The Service is not directed at persons under 18, and we do not knowingly collect their data.
12. Changes
We may update this Policy; material changes will be signalled on the website with a new “Last updated” date.
13. Contact
Privacy questions and requests: [email protected].