Privacy Policy
Version: v3.1-2026-10-02
Who we are
This site belongs to REVISION REAL ESTATE BROKERAGE L.L.C, a real estate brokerage in Dubai: DET licence 1221216, RERA ORN 37083, Trakheesi permit 178739, address: Office 347-1, Al Quoz Industrial 1, Bur Dubai. We decide why and how your data is used, so we are its controller. A marketing contractor builds and runs the site for us and handles data only on our instructions. Send any question about your data to contact@revision.estate. This policy covers the site and the chats you start with us from it, and explains how we handle data under the UAE personal data law (Federal Decree-Law No. 45 of 2021) and, if you are in the EEA or the UK, under the GDPR, the UK GDPR and the rules on cookies and similar technologies.
What we receive on the site
The site has no fields for your name, phone or email. We receive your answers to five questions: goal, budget range, how you plan to pay, when you might need the money back and your stage. With them come the page language and version, how long the quiz took and what your browser sends by itself: IP address, browser and device type, and the country we work out from the IP. From the link that brought you here we take the ad parameters: the Meta click id (fbclid), UTM tags, and the campaign, ad set and ad ids. Where your country's rules and your choice allow it, we also read Meta's browser ids _fbp and _fbc. When you open your result, all this is saved under a short code. We count quiz steps (started, answered, finished) under a random id, without your IP address.
When you tap a messenger button
The line above the Telegram and WhatsApp buttons says what the tap does. On tap, we save your request and a record of your consent: the exact line you saw, the time, your IP address, the language and the version of this policy. Your messenger then opens with a ready message: your code and answers (goal, budget, how you plan to pay, and sometimes when you might sell). Nothing is sent until you send it yourself. Our server sends nothing to Meta at this step.
When you write to us
On WhatsApp we receive your number, profile name and messages. We store the number and the chat with your request, and the profile name too if your first message has no code. The number and name appear on a card in our team's internal Telegram chat so that one of us can pick up your request. On Telegram we read the code from your message; your username and display name appear only on that card, and we do not store them or your Telegram messages in our database: they stay in Telegram itself, in your chat with us and in our team chat. We never write first: the conversation starts with your message, and our licensed brokers reply in the same messenger.
Why we use your data and on what basis
We use your data to reply with options that fit your answers and to take the steps you ask for: under the GDPR, steps at your request before a possible contract (Article 6(1)(b)). We measure which of our ads bring real enquiries, to spend on the ones that work, and protect the site from abuse, for example by limiting requests from one IP address: this is our legitimate interest (Article 6(1)(f)), which you can object to (see below). In the EEA and the UK, the Meta pixel and any storage on your device run only with your consent (Article 6(1)(a)). We keep the record of your consent and, if a deal happens, accounting records because the law requires it (Article 6(1)(c)). Under UAE law, replying to your request rests on the steps you asked for before a contract, and keeping records on our legal duties. You do not have to give us any data: the calculation works without contact details, and whether to write to us is your choice.
Meta pixel and Conversions API
The Meta pixel tells Meta which pages of the site were visited. When your first message reaches us, our server sends Meta one event: an enquiry came from an ad. If your request moves on, for example to a viewing or a deal, the server may send more events, and for a deal a value in dirhams. An event can carry SHA-256 hashes of your WhatsApp number (if we have it), your country, our internal request id and your WhatsApp profile name (if we stored it), plus your IP address, browser details, the version of the page you saw and the Meta click and browser ids (fbc, fbp) we hold. A hash is a one-way code, not the number itself. For visitors in the EEA and the UK, we and Meta Platforms Ireland are joint controllers for collecting these data and sending them to Meta; the main terms are in Meta's Controller Addendum (facebook.com/legal/controller_addendum). What Meta does with the data next is covered by Meta's Privacy Policy (facebook.com/privacy/policy), and you can also use your rights with Meta directly. Meta, as a third party, may use cookies, pixels and similar technologies to collect information from this site and elsewhere on the internet and use it to measure ads and choose which ads to show to whom. We do not build ad audiences from your number, upload contact lists or sell your data.
Your choice about the pixel
If you are in the EEA or the UK, or we cannot tell your country, the pixel and any storage on your device start only after you tap “Accept” in the banner. If you decline, the pixel does not load, and we neither write anything to your device nor read anything from it except your choice. We still count how many visitors start and finish the quiz, using an id that lives only while the page is open, is never written to your device and is never used for advertising audiences. If you decline, no event about your enquiry goes to Meta, neither from your device nor from our server. You can change your choice at any time with the "Advertising choices" link at the bottom of every page. Elsewhere the pixel loads by default. Wherever you are, you can limit ads based on your activity in your Meta ad settings (facebook.com/adpreferences), at youronlinechoices.eu in Europe or aboutads.info/choices, or by blocking third-party cookies in your browser.
What is stored on your device
revision.tracking_consent in local storage keeps your banner choice (accepted or declined); it is written only where the banner is shown, only after you choose, and stays until you clear it. revision.session_id and revision.attribution in session storage keep a random visit id and your click's ad parameters so that a reload does not lose them; they are written only where storage is allowed and are deleted when you close the tab. Meta's cookies _fbp and _fbc on this site's domain, and Meta's own cookies on its domains, come with the pixel: after “Accept” in the EEA and the UK, by default elsewhere. Meta sets _fbp and _fbc for about 90 days. The fbclid click id comes in the link from the ad: we read it from the page address, not from your device.
Who receives your data
Inside REVISION, the licensed brokers handling your request see it in our team's Telegram chat and in our database. Our marketing contractor runs the site and the database for us. Providers: Supabase (the database, in the EU, in Frankfurt); Vercel, a US company (hosting: server functions in Frankfurt, static pages from Vercel's global network); Meta (the WhatsApp Business platform your WhatsApp messages reach us through, plus the pixel and server events). As with any chat, WhatsApp and Telegram also process your messages under their own terms and policies; our team chat runs on Telegram too. We do not sell your data, and we pass it to anyone else only if the law requires it or you ask us to, for example to reserve a property with a developer.
Data outside your country
We are in the UAE, so by using this site or writing to us you give your data directly to a company outside the EEA and the UK. The UAE has no adequacy decision from the EU or the UK. Your data are stored in the EU (Frankfurt), and our team works with them from the UAE. Where this counts as a transfer out of the EEA or the UK, we rely on it being necessary for the steps you asked for before a possible contract (Article 49(1)(b) of the GDPR and the UK GDPR). Some providers may also process data in the United States: Vercel and Meta are certified under the EU-US Data Privacy Framework and its UK Extension, and Supabase and Meta use the EU Standard Contractual Clauses. If you are in the UAE, your data leave the UAE for storage in the EU, under the GDPR's protection, and are used to answer your request.
How long we keep your data
We keep your request, answers and our chat for 24 months after our last contact with you, unless you ask us to delete them sooner; if you only visited the site, your answers and technical data are kept for 24 months after the visit. The record of your consent is kept as long as we may need to prove it. If a deal happens, the records the law requires, such as accounting records, are kept as long as the law says.
Your right to object
Where we rely on our legitimate interest, above all when we send Meta events to measure our ads, you can object at any time without giving a reason. Write to contact@revision.estate and we will stop sending Meta events about you and using your data to measure our ads.
Your rights
You can ask for a copy of your data, its correction, deletion, restriction of its use or export in a machine-readable format, and you can object as described above. You can withdraw consent at any time; this does not affect what we did before. For any of these, write to contact@revision.estate: we answer within one month (30 days) and may ask you to confirm it is you, for example by writing from the same WhatsApp number. To stop our messages, reply STOP or СТОП in WhatsApp: you get one confirmation and nothing more from us. In Telegram, just tell us in the chat and we will stop writing. If you think we handle your data wrongly, you can complain to the data protection authority in your EEA country, the ICO in the UK or the UAE Data Office.
Age and automated decisions
This site is for adults and not meant for anyone under 18; we do not knowingly accept requests from them. We make no automated decisions about you with legal or similarly significant effects: the result screen is arithmetic on your answers.
Changes to this policy
The policy version is at the top of the page. When the text changes, so does the version, and the record of your consent keeps the version you saw.