Legal
Cookie Notice
Last updated: November 13, 2026
This notice covers two different places. On duqqan.app we use strictly necessary cookies — to keep you signed in, to unlock private demos (on the demo’s own address), 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, but Microsoft collects what Clarity records as an independent controller and may use it for its own purposes, including advertising profiles, as set out below. We also count visits to our pages ourselves, with no cookie and nothing stored on your device, as the end of this notice explains.
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. Its Google tags — Google Tag Manager included — load with the page in Google’s consent mode and store no analytics or advertising cookies on your device until you accept, though Google may still receive basic signals from them without cookies; the tags the business adds inside its Tag Manager container follow the consent settings the business gives them there; every other tag we render loads only after you accept it in the consent banner on that site, and not at all if you reject it. 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 can serve the same purpose: your browser’s local storage, which keeps what a site writes until you clear that site’s data, and its session storage, which ends when you close the tab. The ones we use are listed under “Similar technologies” below.
Cookies duqqan.app sets
| Cookie | Purpose | Type & duration |
|---|---|---|
| __Host-duqqan.session_token | Keeps you signed in to your account in the Duqqan panel | Strictly necessary · 7 days, renewed to a fresh 7 when you use the panel a day or more after it was last renewed |
| __Host-duqqan.state | Set only when you continue with Google or Facebook, or connect one in Your account › Security: ties the provider’s answer to the browser that asked, which protects against a forged sign-in | Strictly necessary · 5 minutes |
| __Host-duqqan.two_factor | Set only if you turned on two-step verification: holds your sign-in open while you enter the code from your authenticator app | Strictly necessary · 10 minutes |
| __Host-duqqan.trust_device | Set only if you tick “Trust this device” when entering that code: lets this browser skip the authenticator code at sign-in | Strictly necessary · 30 days |
| Demo access | Unlocks a private demo when you enter its access code or open its emailed preview link. Set only on that demo's own address, never on duqqan.app itself | Strictly necessary · 8 days |
| duq_preview | Opens a private demo from a signed preview link that the business's owner or our team followed, for the rest of that browser session. Set only on that demo's own address | Strictly necessary · until you close the browser |
| Intake | Carries your answers through the site-creation flow | Strictly necessary · 24 hours |
| Cloudflare Turnstile | Protects forms from bots and abuse | Strictly necessary · short-lived |
| duq_claim | Remembers the demo you were invited to claim, so the link survives sign-up | Strictly necessary · 30 days |
| duq_consent | Remembers whether you accepted or rejected analytics here, so we do not ask again — and carries the reference for our own record of that choice | Strictly necessary · 6 months |
| NEXT_LOCALE | Remembers whether you read Duqqan in English or Arabic. Set on duqqan.app as you read it, and in the panel when you arrive from duqqan.app or change your language there | Preference · 1 year |
| sidebar_state | Remembers whether you left the panel's side menu open or closed | Preference · 7 days |
| __Host-duq_admin_session, __Host-duq_admin_2fa | Sign our own staff in to Duqqan's internal back office, and hold that sign-in open while they enter their authenticator code. Set only there — never for a customer or a visitor | Strictly necessary · 7 days; the second 5 minutes |
Each of these is either strictly necessary — the site cannot sign you in, open a private demo, or remember your cookie choice without them — or remembers a choice you made yourself, such as your language or the side menu, so they are set without asking. Some are set on the Duqqan panel or on a demo’s own address rather than on duqqan.app, as each row says.
Similar technologies
| Name | Purpose | Type & duration |
|---|---|---|
| theme | Remembers whether you chose the light or the dark look with the theme switch on duqqan.app or in the Duqqan panel. Set only when you use the switch | Preference · local storage, until you clear this site's data |
| duq_consent_logged:… | Notes that your cookie choice on duqqan.app has reached our record of it, so it is not sent again on every page. Holds only the reference and the time of that choice | Strictly necessary · local storage, until you clear this site's data |
| duqqan:cta-dismissed | On a demo's own address: remembers that you closed the bar at the bottom that says who the preview was made for, so it stays closed | Preference · session storage, until you close the tab |
| duqqan:claim-modal | On a demo's own address: remembers when you opened the first page of the preview and whether the box explaining it has been shown, so it opens by itself at most once and its timer does not restart on every page | Preference · session storage, until you close the tab |
| duqqan-wa-fab-shown | On a business's site: remembers that the WhatsApp button has already opened its greeting once, so it does not open it again | Preference · session storage, until you close the tab |
| duqqan:start:whatsapp-later:… | In the Duqqan panel, on the screen that shows your new demo when it is ready: remembers that you chose “Later” on the card offering to connect WhatsApp, so the card stays hidden for that sign-up in this browser. Holds only our reference for your sign-up | Preference · local storage, until you clear this site's data |
| duqqan:inbox-draft:… | In the Duqqan panel's inbox: keeps a reply or a note you have not sent yet, so it survives the page reloading. Kept for each team member and conversation, and removed when the draft is emptied | Strictly necessary · session storage, until you close the tab |
| duq.canvas.decisions.v1 | Holds the marks our own staff leave on a design review page in Duqqan's internal back office. Set only there — never for a customer or a visitor | Strictly necessary · local storage, until cleared |
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.
| Cookie | Purpose | Type & duration |
|---|---|---|
| _ga | Google Analytics — tells returning visits apart, so a repeat visitor is not counted as a new one | Analytics (non-essential) · 2 years |
| _ga_FB31YWK8SC | Google Analytics — keeps the state of your current visit (which pages, in what order) | Analytics (non-essential) · 2 years |
| _clck | Microsoft Clarity — links your visits to one anonymous id, so a returning visitor is recognised. Microsoft collects this as an independent controller and may use it for its own purposes, including advertising profiles | Analytics (non-essential) · 1 year |
| _clsk | Microsoft Clarity — joins the pages of a single visit into one recording. Microsoft collects this as an independent controller and may use it for its own purposes, including advertising profiles | Analytics (non-essential) · 1 day |
We keep this deliberately narrow: measurement is all we load. There is no Google Ads tag and no remarketing on duqqan.app, and we load both tools with their advertising storage refused. Google Analytics measures for us, as our processor. Microsoft does not process Clarity’s data for us: under Clarity’s terms, Microsoft Corporation is an independent controller of what Clarity collects on these pages and may use it for any purpose its privacy statement allows, including to build profiles for advertising. Neither Google nor Microsoft states where it processes this data, so treat it as leaving the UAE — a transfer 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 business decides which vendors run and is the controller for the data they collect; we render the tags it configured. Google’s tags — Google Analytics, Google Ads and Google Tag Manager — load with the page in Google’s consent mode, which tells them to store no analytics or advertising cookies on your device until you allow that category, though Google may still receive basic signals from them without cookies. The tags a business adds inside its own Tag Manager container load with that container and follow the consent settings the business gives them in Google’s tool, not in Duqqan. Every other tag we render loads only after you allow it in the consent banner on that site — which groups them as Analytics, Marketing and Chat & functional — and not at all if you choose “Reject.” That site’s own privacy notice, at /privacy on the site, names the business and says what it collects.
| Cookie | Purpose | Type & duration |
|---|---|---|
| duq_consent | Remembers the analytics choice you made on a business's site | Strictly necessary · 6 months |
| duq_order | Keeps you signed in to an order you opened with your confirmation code — it is what stops the portal asking for the code on every page | Strictly necessary · 1 hour from when your order code is verified |
| duq_self | Not a cookie: local storage on that business's own address, kept only in the browser of the business's own team. Set when someone opens the business's site from the Duqqan panel, and tells Duqqan's visit counter not to count that browser's visits, so the business's analytics show its visitors and not itself | Set for the business's team only · local storage, until you clear that site's data |
| _ga, _ga_* | Google Analytics — set only if that business enabled it and you accepted. Its tag loads with the page in Google's consent mode, but sets these cookies only after you accept | Analytics (non-essential) · 2 years |
| _clck, _clsk | Microsoft Clarity — set only if that business enabled it and you accepted | Analytics (non-essential) · 1 day – 1 year |
| Google Ads, Google Tag Manager | Set only if that business enabled them. They load with the page in Google's consent mode and store no advertising or analytics cookies until you accept | Advertising / analytics (non-essential) · varies by tag |
| Tags inside a business's Google Tag Manager container | Whatever tags the business put inside its container load with it, and whether they wait for your choice depends on the consent settings the business gives them in Tag Manager — the business, not Duqqan, chooses these and their settings | Varies by tag |
| Meta, TikTok, Snap, Hotjar, HubSpot | Set only if that business enabled them and you accepted — until then they are not on the page at all. The business, not Duqqan, chooses these | Analytics / advertising (non-essential) · varies by vendor |
| Tawk.to, Crisp, Trustpilot, Elfsight | “Chat & functional” in that site's banner — the live chat (Tawk.to or Crisp) and the reviews or Instagram widget (Trustpilot or Elfsight) the business added. None of them loads until you allow that category | Functional (non-essential) · varies by vendor |
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 not sell 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. Our own visit counts — on duqqan.app, and on a business’s site for that business’s analytics — use no cookie and no identifier, and store nothing on your device: a page view adds one to an hourly total, counted by page, by the kind of site the visit came from (and, on duqqan.app, the campaign named in its link) and by type of device — and on a business’s site a tap on its WhatsApp, call, email or directions link is counted the same way. Those totals are all that is kept. Nothing in them can tell one visitor from another, so they cannot follow you from one page, visit or business to the next. The one thing stored is the duq_self note above, in the browser of a business’s own team, which stops that browser being counted.
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].