Privacy policy

The controller of your personal data is Tomas Grygar, Karlova 190/1, 110 00 Prague 1, Czech Republic. For any privacy question or request, write to info [at] dubairealestatedata.com.

Browsing the public pages creates no account and, by default, sets no tracking cookie. Our hosting provider processes ordinary server request logs (such as IP address and browser type) to deliver pages and to protect the service against abuse, which is our legitimate interest under Article 6(1)(f) GDPR. A Google measurement script is present in consent-denied mode; anything it could store or identify happens only with your consent, described next.

We use Google Analytics 4 to understand which pages help visitors. Its measurement script loads in Google's consent mode with every signal denied by default: until you choose "Accept analytics" in the cookie banner it sets no cookies and stores no identifier, and Google receives only cookieless, aggregate pings. Full measurement with cookies starts only after you agree. The legal basis for that measurement is your consent under Article 6(1)(a) GDPR, and you can withdraw it at any time via Cookie settings in the footer, which also removes the analytics cookies.

When enabled, Google Analytics processes usage data such as pages viewed, approximate location derived from a truncated IP address, and device and browser type, stored under a random identifier in first-party cookies (prefixed _ga). We do not use it for advertising, remarketing or cross-site profiling, and Google's advertising signals are switched off. The processor is Google Ireland Ltd (with Google LLC as sub-processor); transfers to the United States rely on the EU-US Data Privacy Framework. We see aggregate statistics, never a named visitor.

The second tool is Microsoft Clarity, and it does more than count visits, so it is worth being precise about. Clarity records how a page is used — pointer movement, clicks, scrolling and the sequence of pages — and can replay that as a session recording, which we use to find layouts and controls that do not work. Because that is a recording rather than a counter, its script is not loaded at all until you choose "Accept analytics": decline the banner or ignore it and nothing from Clarity is fetched or run. It stores a random identifier in first-party cookies (_clck, _clsk). The processor is Microsoft Ireland Operations Ltd, with transfers to the United States under the EU-US Data Privacy Framework, and Microsoft states that Clarity data is not used to build advertising profiles of the people recorded. The legal basis is again your consent under Article 6(1)(a) GDPR, withdrawable at any time via Cookie settings in the footer, which stops the recording and removes the cookies.

The third tool is PostHog, which we use for product analytics: which pages and tools people actually reach, and where a journey stops. Like Clarity it goes beyond counting — it captures interactions automatically and can record a session replay — so it is treated the same way: its code is not downloaded at all until you choose "Accept analytics", and declining or ignoring the banner fetches nothing from PostHog. It stores a random identifier in a first-party cookie (ph_<id>_posthog) and in local storage. The project runs on PostHog's US cloud, so the data is transferred to the United States under the European Commission's standard contractual clauses; the processor is PostHog Inc. The legal basis is your consent under Article 6(1)(a) GDPR, withdrawable at any time via Cookie settings in the footer, which stops the capture and removes the cookie. We do not identify visitors in PostHog: a person profile is created only for someone who signs in.

Microsoft Clarity and Google Analytics are linked. The link collects nothing new: both tools already ran, and both still run only once you accept analytics. What it adds is that the two records can be matched, so visits counted in Google Analytics can be traced to the corresponding session recordings in Clarity, and those recordings can be filtered using Google Analytics dimensions. We use it to understand why a figure moved, never to identify a visitor. It rests on the same random identifiers described above, it creates no new cookie, and withdrawing consent via Cookie settings in the footer ends it on both sides at once.

None of the tools receives anything you type. Recordings capture interaction, not the contents of form fields, and this site asks for no personal detail in the first place: it has no search box that identifies you, no contact form and no payment page. If you sign in, that happens on Google's own page, never on ours.

We store only what the account needs to work:

• From Google, when you choose to sign in: your name, email address and profile picture URL. We never receive your Google password.
• A sign-in record so you stay signed in, which includes the IP address and browser user agent of the session, plus its creation and expiry time.
• The list of areas you follow, and any comparison or filter you save.

The legal basis is Article 6(1)(b) GDPR: this data is necessary to provide the account you asked for. We do not build profiles, we make no automated decisions about you, and we do not use your data to target advertising.

Five processors are involved, each only to run the service: Google (sign-in, and analytics if you consented), Microsoft (Clarity session analytics, only if you consented), PostHog (product analytics and session replay on its US cloud, only if you consented), Vercel (hosting) and Turso (the account database). Some of them process data outside the European Economic Area, in which case transfers rely on the European Commission's standard contractual clauses. We share your personal data with nobody else, and we never sell it.

Account data is kept until you delete your account, which erases it immediately and permanently. Sign-in records expire on their own within 30 days. Deleting your account also deletes your followed areas.

Under the GDPR you may request access to your data, correction, erasure, restriction of processing, portability, and you may object to processing. Erasure and access are built into the site: everything we hold is listed on Account and data, with a button that deletes it. For anything else, contact the controller above. You also have the right to complain to your national data protection authority.

Two kinds of cookies can exist here, both under your control. First, the session cookie that keeps you signed in; it appears only after you sign in and is strictly necessary for the account, so it needs no consent. Second, analytics cookies, which appear only if you accepted analytics in the banner: Google Analytics writes _ga and _ga_<id>, Microsoft Clarity writes _clck and _clsk, and PostHog writes ph_<id>_posthog. Your choice itself is remembered in your browser's local storage. There are no advertising or cross-site tracking cookies. If you never sign in and never accept analytics, no cookie is set at all, and declining also removes any analytics cookie left from an earlier visit.

The property figures published here come from official Dubai Land Department open data and are aggregate statistics. They describe registered transactions, not identifiable people, and they are never linked to your account. See data sources and the methodology.

This site is a professional data service and is not directed at children. We do not knowingly create accounts for anyone under 16.

If this policy changes, the date at the top changes with it. Material changes affecting account holders will be shown in the site before they take effect.