Privacy policy

The short version

Browsing AQARCHECK requires no account and we do not ask for personal information to read anything on the site. We collect data only where you give it to us or where it is needed to keep the service running.

What we collect

When you just browse

Our hosting provider records standard technical data for every request — IP address, browser type, the page requested and the time. This is used for security, abuse prevention and aggregate traffic measurement. We do not use it to build a profile of you.

When you contact us

If you email us, we keep your message and address so we can reply and follow up. Nothing more.

If you create an account

Reading the site never needs one. An account stores your name and email address, and a phone number if you choose to give one. A buyer account additionally stores the projects you save and any private note you attach to them — those are visible to you and to nobody else, including us in any aggregated form and including the developers concerned.

An agent or developer account stores the business details that appear on the material they share: company or agency name, broker registration number, contact number and profile photo. Where account features involve submitting ownership documents for verification, those documents are used solely to confirm the claim is genuine, are visible only to our reviewers, and are never published.

What we do not do

• We do not sell personal information.
• We do not pass your details to developers, brokers or agents. If a developer wants to reach you, that has to come from you.
• We do not run advertising trackers or cross-site ad profiling.

Cookies

The site uses cookies and equivalent local storage only where needed to make features work — keeping you signed in, or remembering an interface preference. We do not set advertising cookies and we run no third-party analytics script anywhere on this site.

Shared property cards

An agent can send you a link to a single property card, at an address beginning aqarcheck.com/c/. Those pages — and only those pages — measure how the card is used, so the agent who sent it knows it arrived and what you were interested in. Nowhere else on AQARCHECK does this.

On a shared card we record:

• that the card was opened, which of its sections came into view, how far down the page you scrolled, roughly how long the page was open, and whether you tapped the WhatsApp or callback button;
• the country and city your request came from, the kind of device (mobile, tablet or desktop) and the app or site you arrived from — all derived at the moment of the request. We do not store your IP address.

To count one person opening a card three times as one viewer rather than three, we set a first-party cookie named aqarcheck_vidholding a random identifier. It is not readable by any script, is not shared with anyone, is never linked to your name, and is set only when you open a shared card.

The agent who sent the link sees this activity for that link. They do not learn who you are: no name, no phone number, no email, no IP address. If you fill in the callback form, the name and number you type go to that one agent, because that is what asking for a callback means. Developers never receive any of it — they see counts only, and never a buyer's identity.

Processors we rely on

We use third parties to run the service. Each processes data only on our instructions:

• Vercel — hosting and content delivery.
• Supabase — database, authentication and file storage.
• Resend — sending email, such as address verification and notifying an agent that someone asked for a callback.

How long we keep things

Technical logs are retained for a short period for security purposes and then discarded. Correspondence is kept for as long as needed to deal with the matter it concerns.

Your rights

You can ask us what we hold about you, ask for it to be corrected, or ask for it to be deleted. Write to us via the contact page and we will respond.

Changes

If this policy changes materially, the updated date above will change and the new version will be posted here before the change takes effect.