Privacy policy

The platform is a property market operating in the United Arab Emirates, with two surfaces over one database: the customer portal you are reading this in, and an internal admin console reached only by a member of staff signed in under their own name with their permissions bounded. This policy covers both surfaces and everything that passes between them.

It addresses everyone who touches the platform: the visitor browsing without an account, the user who created one, the owners, brokers and hosts who publish, the subscribing agencies, and whoever books a unit or settles an invoice.

Wherever "the platform" appears, it means the operator of the service as data controller under Federal Decree-Law No. 45 of 2021 on the protection of personal data and its executive regulations, together with the federal and local property legislation that bears on it.

And what this document describes is what the system does. The figures you read in it are not estimates: they are read as the page is rendered, from the very module config files the server runs on.

Data is collected in proportion to what its subject does rather than to what might be useful to hold: a visitor browsing is asked for nothing, whoever publishes a listing is asked for what proves their right to publish it, whoever books is asked for what completes the booking, and whoever pays is asked for what completes the invoice.

Card numbers are not stored on the platform's servers. The card is entered at the payment gateway, and what comes back to the platform is a token standing in for it, the last four digits, the card type and its expiry — and that alone is what you see under "Manage cards".

• From you directly: what you write in your account, your listing, your ticket or your comment.
• From your device: the session cookie, the language and theme, and the network address the request arrived from.
• From the three sign-in doors: Google proves a mailbox, Firebase proves a telephone number, and the UAE digital identity proves a person — and that last alone earns the trust level that opens what lies behind it.
• From the competent authorities: the permit reference held by Trakheesi in Dubai, Adrek in Abu Dhabi, and Tasdiq and Dari beyond them, according to the property's emirate.
• From the payment gateway: the outcome of the transaction and the card token, never the card details.
• From the agency you belong to if you are a broker in it: your standing there, the state of your licence and of its subscription.

Your data is not sold, not rented, and not used in any third party's advertising; no cross-site advertising profile is built from it.

A listing has a declared road: draft, then awaiting document review, then published — or rejected. Nothing is published without a valid permit from the competent authority in its emirate. What is published lives 60 days and then expires automatically unless it is renewed.

And the portal shows only the published. Whatever is a draft, awaiting review, rejected or expired is never shown to a visitor, and is not opened by an address typed by hand: the search for the item asked for runs over the set allowed to be displayed rather than over all the data, so there is no side door into what was not published.

Telephone numbers are masked in every administrative surface: the member of staff reviewing does not need to read the whole number to do their work.

And contact details on marketing requests sit behind a three-part gate: being a broker, having an accredited file and a current licence, and having a live subscription for your agency.

• The photographs you upload are shown publicly with your listing, so do not upload in them what you do not want seen.
• The property's location is drawn on the map at the coordinates you chose yourself; what you enter is what is seen.
• Ownership and authority documents are never shown: they go to a private disk rather than a public one, are not opened by whoever guessed the address, and are seen only by a member of staff authorised to review them — whose opening of them is itself recorded in the audit trail.
• A comment you write on a listing is published publicly under its name. It is the one thing in the portal written by a stranger to the platform, so it carries a rate limit of no more than 10 comments a minute and a hidden field that turns machines away.

When a booking completes, the host sees what they need to receive you: your name, a means of contact, the dates, the number of guests. They do not see your payment method or your card details.

The platform's cut and the owner's payout are stored on the booking record as calculated at the time of booking rather than at the time of display: a booking that happened is never re-priced because a rate changed after it. That safeguard is yours and the owner's alike.

Cancellation is free up to 48 hours before check-in; after that one night is due. Check-in is from 15:00 and check-out until 11:00, unless the unit states otherwise.

An invoice falls due within 14 days of issue and then goes overdue. The base currency is AED.

Three identities that never meet: staff, users and advertisers — each with its own table, its own guard and its own session. An account in one realm does not open another realm's surface even with details perfectly valid in its own: the exclusion lives in the data source rather than in a condition written in one controller and forgotten in the next.

Inside the console a member of staff is not granted a page at a time but a domain, and there are seven of them, each role carrying a map over them on an ordered ladder: none, then read, then write, then administer. Whoever reached a level has reached what is below it, and no link appears in anybody's menu that opens a refusal.

Every administrative action is recorded in an audit trail: who acted, what they did, on which record, from which network address, in which browser, and what changed. The trail is written and never amended — a correction there is a new row that explains rather than a change to the old — and it is kept 730 days.

Your data leaves for a third party only for a declared purpose and only so far as that purpose requires. These are all of them, not some of them.

The property cards the assistant attaches to its answer are chosen by the platform from its own table and are never named by the model, and only what is published is attached. The assistant is expressly forbidden from inventing permit numbers, market figures or prices.

Each category has its period, and nothing is kept without a reason. These periods are what the system runs on rather than what is hoped of it.

Deleting an account does not erase what the law requires be kept: the audit trail, invoices, and the record of a deal that happened. Everything else is deleted or stripped of what points to its subject. A single saved search is capped at 20 alerts a day, so that alerting never becomes burying.

• The password is not stored as text but as a digest, and its minimum length is 10 characters.
• Guessing meets two barriers rather than one: 5 attempts in 60 seconds from a single address, and a lock on the account itself after 10 attempts for 15 minutes — so changing address does not help an attacker, and neither does waiting out the minute.
• Refusal is one answer whatever its cause, down to the timing: when there is no account the password is compared against a dummy digest, so its existence cannot be read off how fast the answer came.
• Ownership and authority documents sit on a private disk rather than a public one, and telephone numbers are masked in the administrative surfaces.
• A short-term rental permit may require a second reviewer before it counts, because it opens real payments the moment it is accepted.
• Each realm has its own session, so signing into one surface does not sign you into another.

And no system is unbreachable. Should anything seriously affect your data you will be told, and so will the competent authority, within the period and in the form the law requires.

You have rights over your data under Federal Decree-Law No. 45 of 2021. These are they:

• To know what we hold about you, and to receive a copy of it.
• To have corrected whatever is wrong, incomplete or out of date.
• To ask for it to be erased, so far as no statutory duty to keep it or live contract stands against that.
• To restrict its processing, or object to it.
• To move it to another provider in a machine-readable form.
• To withdraw your consent to alerts at any time, without that touching the lawfulness of what happened before the withdrawal.
• To complain to the competent personal data protection authority in the country.

These requests are raised from inside your account through support, and answered within the statutory period. You may be asked to prove your identity before one is carried out — because carrying out an erasure request for somebody who is not the account holder is the very harm being guarded against.

• The session cookie: essential; authentication does not work without it, and it lives 120 minutes from the last activity.
• The form protection token: essential, and it stops a form being submitted in your name from another site.
• Language and theme: two preferences kept so the page opens as you left it — and switching language is an address on the server rather than state in the browser, so it works with JavaScript off.

There are no advertising cookies on this platform and no tracking across other sites. Refusing the essential ones means signing in will not work.

The service is addressed to those who have reached eighteen and have full capacity to contract. No minor's data is collected knowingly, and whatever reaches us is deleted once known of. Anyone who believes a minor's data has reached us should tell us so we can delete it.

Data is processed inside the country so far as the operating arrangement allows. Where something must go to a provider outside it — the assistant, the map tiles, the notification providers — only what that purpose alone requires is sent, and within the cross-border safeguards the Decree-Law permits.

This policy changes whenever what it describes changes. The last-updated date is written at its head, and means the day its wording changed rather than the day the file was deployed. A material change is notified to account holders before it takes effect.

For any question about this policy, or to exercise any of the rights above, this is the contact point:

No statutory contact address is configured in this build. Requests are raised from inside your account, through support.

Open a ticket from your account