Cookie Notice

This notice covers two different places. On duqqan.app we use strictly necessary cookies — to keep you signed in, to unlock private demos, to carry you through the site-creation flow, and to protect forms from bots — plus Google Analytics and Microsoft Clarity, which measure how the site is used and load only if you accept them in the banner. Until you do, no analytics tag is on the page at all. Clarity also records your visit — how you scroll and click through a page — so we say that plainly below. We run no advertising tags here.

On a business’s own site built with Duqqan, that business may switch on its own analytics or advertising tags. Those are the business’s choice and load only after you accept them in the consent banner on that site. They are listed separately below so it is clear who is setting what.

What are cookies?

Cookies are small text files placed on your device when you visit a website. They let the site remember things between page loads — for example, that you are signed in. Similar technologies (such as tokens in local storage) can serve the same purpose; we refer to all of these as “cookies” here.

Cookies duqqan.app sets

Every one of these is strictly necessary: the site cannot sign you in, open a private demo, or remember your cookie choice without them, so they are set without asking.

We keep a record of your choice

When you accept or reject, we also store that decision on our side — the date, which of the two things you allowed, and which version of this notice you were shown. Data-protection law puts the burden on us to be able to show that a choice was made and honoured, and a note that lives only in your browser cannot do that: you can clear it, and then neither of us has anything.

This applies to a refusal too. Choosing Reject writes a record that you refused — that is the half of the obligation that actually protects you, so we are explicit about it rather than leaving it to be discovered. The legal basis for keeping it is our own compliance obligation, not your consent; we do not ask permission to keep proof of permission.

The record is deliberately thin. It contains no IP address, no browser fingerprint, no page you visited, and neither of the analytics ids above — linking your choice to the measurement it governs is the one thing it must not do. What ties the record to you is a random reference your browser generates and keeps in the duq_consent cookie; it identifies nobody on its own, and if you clear the cookie the record is anonymous even to us. You can see that reference at any time under Cookie settings → Choose what to allow, and quote it if you ever want to ask us about it. We keep these records for 24 months, then an automated job deletes them.

Analytics cookies — only if you accept

We use Google Analytics 4 to see which pages people read and where they arrive from, and Microsoft Clarity to see how those pages actually behave — where people scroll, what they click, where they get stuck. Neither is loaded until you say so: before that the tags are absent from the page, not merely idle, and none of the cookies below exist. Choosing Reject keeps it that way — with the one exception named above, which is the record of the refusal itself.

These are two separate choices, and the banner lets you make them separately: Choose what to allow opens a toggle for traffic measurement (Google Analytics) and one for session recording (Clarity). Allowing the first and refusing the second is a real option — counting page views and filming the visit are different things to agree to, so we do not ask for them in one word. Accept allows both and Reject allows neither, each in one click.

Clarity works by recording your visit and replaying it as a video-like session, and by aggregating those visits into heatmaps. This is more than counting page views, so it is worth being exact about what it means: the recording captures your mouse movement, scrolling, clicks and the pages you move between. It does not capture your camera, microphone, or anything outside this site. Several of these pages do carry a text box — the one that asks for your business name, and the order-tracking box on /track — and what you type into a form field is masked before the recording is stored: that is Clarity’s default behaviour and we have not changed it. Clarity does not run on the sign-up flow, inside your account, or on a business’s own site.

We keep this deliberately narrow: measurement is all we load. There is no Google Ads tag and no remarketing on duqqan.app. Both Google and Microsoft process this data in the United States — a transfer outside the UAE, made on the basis of the consent you give in the banner and withdrawable at any time. For what each does with it, see the Google Privacy Policy and the Microsoft Privacy Statement.

Cookies on a business’s own site

A business that builds its site with Duqqan can switch on its own analytics or advertising tags from its panel. When it does, that businessdecides which vendors run and is the controller for the data they collect; we render the tags it configured. They load only after you choose “Accept” in the consent banner on that site, and not at all if you choose “Reject.”

For how those vendors use your data, see the Google Privacy Policy and the Microsoft Privacy Statement, or our Privacy Policy for the processors we use ourselves.

What we don’t use

We do not run advertising or cross-site retargeting cookies on duqqan.app, we do not track you across the businesses hosted with us, and we do notsell your data. The measurement above covers this site alone, and the Clarity recording described there is of this site’s own pages — not your screen, not your keystrokes, and nothing in another tab.

How to control cookies

You control analytics cookies through our consent banner: choose Reject to keep them off, or Choose what to allow to permit one and not the other. The Cookie settings link in the footer reopens the same choices at any time, so withdrawing is exactly as easy as agreeing was — and withdrawing one category leaves the other as you set it. Turning session recording back off also reloads the page, because that is the only way to stop a recorder that has already started. You can also block or delete cookies in your browser settings — but because the strictly necessary cookies above are required, blocking them will stop you from signing in or opening a demo.

Two things worth being clear about. Deleting the duq_consent cookie makes us ask again; it does not delete the records described above, which are kept for their retention period and are what we would rely on to show what you chose. And changing your mind does not erase the earlier choice — it adds the new one, so the history shows a decision that was made and then changed, which is what makes withdrawal demonstrable rather than merely claimed.

Updates to this notice

We may update this notice as our use of cookies changes, and will revise the date above. Where a change affects non-essential cookies, we will ask for your consent again.

More information

For how we handle personal data generally, see our Privacy Policy. Questions? Email [email protected].