Legal
Privacy Policy
Last updated: November 15, 2026
هذه الصفحة متوفرة بالإنجليزية فقط — النسخة الإنجليزية هي الملزمة قانونياً.
This Privacy Policy explains how Diojen Tech FZ-LLC (“Duqqan,” “we,” “us”), licensed by the Ras Al Khaimah Economic Zone Authority (RAKEZ) under e-commerce licence No. 45008154 and registered at VUPR0809, Compass Building – Al Hulaila, Al Hulaila Industrial Zone-FZ, Ras Al Khaimah, United Arab Emirates, collects, uses, and protects information when you use Duqqan at duqqan.app, the owner panel, and demos. We are the data controller for that information and we process personal data in line with the UAE Personal Data Protection Law (Federal Decree-Law No. 45 of 2021).
1. Scope
This policy covers the data we process to run Duqqan. It does not cover the content or visitor data of our customers’ own websites — on a published customer site, and on a demo a customer is building in its own Duqqan account, the customer is the controller of its visitors’ data — what they send through its forms, the technical data their browsers send to deliver the site and protect it, the visit counts we make for its analytics page, and their cookie choice — and we act as their processor, under our Data Processing Agreement, which forms part of our Terms. Two things on every demo are ours, not the customer’s: the access-code gate we run ourselves in front of it, and our record that the demo was viewed. What they process is ours, as section 2 describes. A demo we prepared ourselves to show a business that has no Duqqan account is different: until that business takes it on, we are responsible for what is sent through it, and this policy covers it. Every such site and demo a visitor can open carries its own privacy notice, at /privacy on that site, which names who is responsible for its visitors’ data. On a demo still locked by its access code, that page says only what our access-code gate processes and that the full notice is shown to visitors who have the code.
2. What information we collect
- Account data — your name and email. You sign in with a one-time code we email you; we keep only a hash of each code, for the ten minutes it works. Where the sign-in page offers it, you can also sign in with a Google or Facebook account, and we then keep which one and its identifier for you, and the date you connected it (section 12). There is no password. A password set in the few minutes our switch to sign-in codes took — on an account created then, or by a password reset then — is kept as a hash, which no sign-in accepts, until the account’s first sign-in with a code deletes it. If you turn on two-step verification, which is optional, we also store the secret your authenticator app uses and your backup codes, both encrypted, until you turn it off.
- Business and site content — the business information, text, and media you provide or upload.
- What you tell us when you start a site — when you sign up for a demo yourself: your business’s name, your email, and your WhatsApp number, which the demo shows on its WhatsApp buttons, and on its call button unless your Google listing or website shows another number; which of our services you are interested in (we record this as interest only — it buys nothing); your city or area, the site’s language and, if you give one, a link to your Instagram account, Google Maps listing or website; and, if you write or add them, a one-line description of your business, what you offer, and your photographs. Your photographs are stored privately: no public address opens them, only short-lived links our systems sign — to show them back to you while you fill in the form, and, when we build your demo, to let the AI provider that builds it look at them and choose the ones that suit each page. The build publishes on the demo only the ones it uses, like the demo’s other images, and the originals stay private. If the link that brought you to the start carries them, your sign-up also keeps where your visit came from: the campaign tags in that link (utm_source, utm_medium and utm_campaign), the category of site you arrived at duqqan.app from, and the page of duqqan.app you landed on — so that we know which campaigns and pages bring sign-ups. A link from duqqan.app adds them for you; nothing about your visit was stored on your device to do it. All of this is kept with your sign-up: one you leave unfinished is not deleted on a schedule but kept until you ask us to delete it (section 15), and your photographs are deleted with it when you do.
- Lead and prospect data — contact and business details, including information we gather about a business from public sources (its Google Maps listing and its own website) to prepare a demo. When we build the demo of a business’s website — whether the business asked for it or we prepared it to contact them — we may also read the latest public posts of the business’s own Instagram account, and the demo may use their captions and photographs. We also use a business’s public details, and a picture of its website’s home page that we keep with our record of it, to decide which businesses to contact first (section 6).
- Payment data — handled by Stripe. We receive billing status and details but never store full card numbers.
- Order and applicant data — when a business uses Duqqan’s order desk, the people it serves submit what that business’s service requires. Depending on the service that can include identity details (passport and Emirates ID numbers, date of birth, nationality), uploaded documents such as passport scans and photographs, and — for services that need them, such as medical or visa applications — health information (for example blood group or chronic conditions) and criminal-record details. Duqqan is the processor for this: it is collected by the business, for the business, under its own terms with its customer, and we handle it on that business’s instructions. The sensitive fields — among them the identity numbers, the date of birth, the health answers and the criminal-record details — are encrypted at rest, field by field, with a key unique to the business; the yes-or-no answer to whether a person has a criminal record is not. Uploaded documents are stored privately and reachable only through a short-lived signed link — never a public URL.
- Domain registration details — if you buy a domain through Duqqan, the registrant details the registry requires (name, organisation, postal address, email and phone). We pass them to our registrar, Openprovider — a trade name of Hosting Concepts B.V., of Rotterdam, the Netherlands (Chamber of Commerce no. 24277249), an ICANN-accredited registrar that acts under its own registration agreement — and it passes them to the registry for that extension, which may publish them in the public registration data (WHOIS/RDAP). If you chose WHOIS privacy where we offer it, we switch it on as soon as the registrar allows it; until then your registrant details are published in WHOIS as the registry requires, which on a new registration can last several days. This is a requirement of registering a domain, not a choice we make about your data.
- Communications — messages you send us.
- Technical and usage data — IP address, browser/user agent, timestamps, and limited tracking of whether our emails were opened or clicked and whether a demo was viewed. We also count visits to duqqan.app ourselves, without any outside tool: for each hour, how many times each page was viewed and in which language, how many visits arrived and how many reached the first screen of our start wizard, the category of site each visit came from (a search engine, a social network, an AI assistant and the like — never the address of the page), the campaign tags in the link that brought it (utm_source, utm_medium and utm_campaign) and whether the device is a phone, a tablet or a computer. Those totals are all we keep: no cookie, no identifier and no IP address. Your browser sends the address of the page you came from and its user agent with each count; we reduce them to that category and that device class as they arrive and keep neither, and the campaign tags and pages counted in an hour are also held, with nothing else, for two hours, to cap how many different ones an hour can store. Nothing is stored on your device for this and nothing an earlier visit stored there is read, so it does not wait for the cookie banner: we count on our legitimate interest in knowing how our site is found and used. On duqqan.app we also measure traffic with Google Analytics 4 — which pages are read and where visitors arrive from — and use Microsoft Clarity, which records how a visit moves through a page (scrolling, clicks) and aggregates those visits into heatmaps. Each loads only after you allow it in the cookie banner, and both are limited to our own marketing pages. Google Analytics measures for us, as our processor, and we load it with every one of Google’s advertising signals refused. Clarity is different: Microsoft Corporation is not our processor for it but an independent controller of what it collects on those pages, and may use that data for its own purposes — including to build profiles for advertising — under the Microsoft Privacy Statement. On a preview’s access-code page, which we run ourselves as a security control whoever the preview is for, we count the attempts made from your IP address, for ten minutes from the first one, to stop the code being guessed; a correct code, or the preview link we send, sets a cookie that remembers for eight days that this browser may open the preview. That gate is ours, as controller. So is our record that a demo was viewed: the first time a demo is opened past its gate — not inside a frame, as our back office shows it, and not through the signed preview links we give our team and the business’s own members — its page tells us, and we record on our lead record for that business the time of that first view and that the demo has been viewed, with no IP address, browser details or visitor identifier. Your IP address is used only to limit how often a page can send that signal, and is counted for sixty seconds. The visit counts are limited the same way: your IP address keys that limit for sixty seconds and is never kept with the counts. The other technical data a customer’s own pages and demos receive — to deliver them and protect them from abuse — we process for that customer, as its processor (section 1). So are the visit counts we make on a customer’s published pages, for its analytics page in the Duqqan panel: for each hour, how many times each page was viewed, where the visits came from as a category such as a search engine or a social network, whether the device is a phone, a tablet or a computer, and how many taps its WhatsApp, call, email and directions links had — totals only, with no cookie and no identifier, deleted with the customer’s business. A browser in which the customer’s own team opens those pages from the Duqqan panel keeps a note in its local storage, duq_self, that stops it being counted (see our Cookie Notice).
- Your cookie choice — when you accept or reject analytics on duqqan.app, we keep a record of that decision: the date, which of the two categories you allowed, the version of the notice you were shown, and a random reference your browser generates. It holds no IP address and no analytics id. A refusal is recorded too, for the reason set out in the Cookie Notice — showing that we honoured a “no” requires having kept it.
3. How we collect it
We collect data directly from you, automatically as you use the Services (see our Cookie Notice), and — when we build a demo of a business’s website — from publicly available sources about that business.
4. Why we process it (lawful basis)
Under the UAE PDPL we rely on: performance of our contract with you (to provide the Services); our legitimate interests (to prepare business demos, count visits to duqqan.app and know which campaigns bring sign-ups, improve the product, and prevent fraud and abuse); your consent where it is required; and compliance with our legal obligations.
One case is worth naming because it is easy to get backwards. The analytics tools in our cookie banner run on your consent. The record that you gave or refused that consent is kept under our legal obligation instead — we are required to be able to demonstrate it, and a record you could withdraw would be no evidence at all. That is why refusing analytics still leaves a record of the refusal.
5. How we use it
- to generate, host, and serve your website;
- to send account, billing, and service communications;
- to take payments and manage subscriptions;
- to improve and secure Duqqan, prevent abuse, and know which pages and campaigns bring visits and sign-ups;
- to send you marketing about Duqqan, where permitted (see below);
- to demonstrate that you gave or refused consent to analytics, and when;
- to comply with our legal obligations.
We do not sell personal data.
6. AI processing
We use two AI providers. OpenAI, via the OpenAI API, generates content from your inputs and publicly available information about your business. It also prepares what we send to businesses we contact — their demo website and our first message to them — from publicly available information about the business and the name and contact details of the person we write to. At OpenAI, your business content is not used to train third-party AI models; it is processed under enterprise data-protection terms that prohibit training on your data. The same provider powers a business’s WhatsApp assistant, part of the WhatsApp add-on, which answers as soon as WhatsApp sending is live on Duqqan: it is on for a demo and, for an active business, only once that business has switched it on. When someone who asked, on that business’s Duqqan site, to be contacted on WhatsApp writes to the business there, the assistant reads the recent conversation, the enquiry they sent and the business’s catalogue and answers on the business’s behalf — saying that it is an AI — and can place the order the customer confirms and send them its link. Replying STOP ends it, and the business’s team can take the conversation over at any time, which silences the assistant. Anthropic’s Claude does one thing for us: it ranks the businesses we may contact, so that we know which to contact first — and when we choose it instead, OpenAI does the same ranking. For it we send public facts about the business — its name, category and area, its Google rating and review count, and whether it has a website or an Instagram account — and the business’s own home page as it publishes it: the page’s address, its text with email addresses and phone numbers masked, and a picture of its top, which can show what the business itself publishes there, such as its phone number, email address, social accounts or names. We never send the contact details we hold about the business — its phone number, email address, contact person or Instagram account’s name — nor its map coordinates or map link, and a website address on a social, messaging or map site is sent as the name of that site alone. We follow a business’s website through its redirects and through a refresh tag that moves a visitor on shortly after the page opens, and the page it ends on is the one we read; when that is such a page, we send only the name of that page’s site and take no picture of it. We do not follow a page’s scripts: the picture shows what our browser shows when it opens the page, which can be another page and, like any picture, what the business publishes. The ranking is ours alone: it sends nothing to the business and builds nothing. Claude does this on our own Claude subscription, under Anthropic’s consumer terms — not under enterprise terms — and model training is turned off on every Claude account we use, so what we send it is not used to train Anthropic’s models.
7. Automated decision-making
Duqqan uses AI to generate website content and suggestions, to answer WhatsApp enquiries and to rank the businesses we may contact, as described in section 6, but we do not make decisions producing legal or similarly significant effects about you solely by automated means. You always review and control what is published, and an order the WhatsApp assistant places reaches the business’s order desk for its team to handle. The assistant takes no payment itself: for an active business it sends the customer that business’s own order page, where the customer pays the business if it takes online payment, and for a demo a demo page that takes no money.
8. Service providers (sub-processors)
We share data only with the providers we need to run Duqqan, and only the minimum necessary. Each provides its service to us under its own terms; the table names the company we contract with for each, and the notes below it say what about a row is not yet confirmed.
| Provider | Contracting entity | Purpose | Region |
|---|---|---|---|
| OVHcloud | Hébergement OVH Inc. (Montreal, Canada) | Application and database hosting | Germany |
| Cloudflare | Cloudflare, Inc. (San Francisco, CA) | DNS, CDN, media storage (R2), bot protection (Turnstile), custom domains, and rendering the public web pages we read about a business to prepare its demo or to decide whether to contact it | Global |
| Stripe | Stripe Payments Europe, Limited | Payment processing and subscription billing | Not stated by Stripe — see below |
| Telr | Telr PTE LTD | Card payments, for businesses that select it | Not stated by Telr — see below |
| Resend | Plus Five Five, Inc. (San Francisco, CA) | Transactional and notification email | USA |
| Browserless | browserless.io, Inc. (Battle Ground, WA, United States) | Headless browser rendering of public web pages about a business, and screenshots of generated sites | Not stated by Browserless — the endpoint we call is in Amsterdam |
| Bright Data | Bright Data Ltd. (Netanya, Israel) | Reading the public posts of a business's own Instagram account when we build a demo of its website | Not stated by Bright Data — see below |
| OpenAI | OpenAI OpCo, LLC | AI content generation, vision, and translation — including the demo website and the first message we prepare for a business we contact, with the name and contact details of the person we write to; the WhatsApp assistant's replies to a business's customers; and, when we choose it for that, the AI ranking of the businesses we may contact, from public facts about the business and its own home page as published, never the contact details we hold about it | Not stated by OpenAI — see below |
| Anthropic | Anthropic, PBC | AI ranking of the businesses we may contact, from public facts about the business — its name, category and area, its Google rating and review count, whether it has a website or an Instagram account — and its own home page as published: its text, with email addresses and phone numbers masked, and a picture of its top, which can show what the business publishes there; never the contact details we hold about it | Not stated by Anthropic — see below |
| Google Cloud EMEA Limited (Dublin, Ireland) | Places / Maps data for business information | Not stated by Google — see below | |
| Google Workspace | Google Cloud EMEA Limited (Dublin, Ireland) | Email and support correspondence — every message to legal@, hello@ and [email protected] is held there | Not stated by Google — see below |
| Google Analytics | Google LLC | Traffic and behaviour measurement on duqqan.app, after cookie consent | Not stated by Google — see below |
| WhatsApp (Meta) | WhatsApp LLC | WhatsApp Business messaging, for businesses that connect a number | US / EU |
| Openprovider | Hosting Concepts B.V. (Rotterdam) | Domain registration — registrant contact details are passed to the registry | Netherlands |
| Slack | Slack Technologies Limited (Dublin) | Operational alerting to our own team | Ireland |
| Sentry | Functional Software, Inc. d/b/a Sentry (USA) | Error reports from Duqqan's servers and from its console, backoffice and marketing pages — an error's type, scrubbed message, stack trace, route template and coarse tags; never IP addresses, cookies, request bodies, URL query strings, email addresses or a site visitor's data | EU (Frankfurt, Germany) |
- Cloudflare — Cloudflare's Self-Serve Subscription Agreement names Cloudflare, Inc. of San Francisco. 'Global' describes its network, which serves our traffic from data centres around the world, not a processing location Cloudflare has stated for our data; its data processing addendum would confirm one.
- Stripe — Stripe's Services Agreement names Stripe Payments Europe, Limited for a Stripe account in the United Arab Emirates, as ours is, but does not say where Stripe processes our data. Its data processing agreement would confirm it.
- Telr — Telr's privacy policy names Telr PTE LTD and says Telr is regulated by the Central Bank of the UAE, from an address in Dubai, but it does not say where Telr is incorporated or where it stores and processes card data. Telr's merchant agreement or a company registry record would confirm both.
- Browserless — Browserless's privacy policy names browserless.io, Inc. but does not say where it processes data; it names DigitalOcean as its infrastructure. We send our requests to its Amsterdam endpoint, which is where we connect rather than a processing location Browserless has stated. Its data processing agreement would confirm it.
- Bright Data — Bright Data's Master Service Agreement names Bright Data Ltd. of Netanya, Israel, for a client outside the US, but does not say where it processes data. Its Data Protection Addendum would confirm it.
- OpenAI — OpenAI's Services Agreement names OpenAI OpCo, LLC for a customer outside the EEA and Switzerland, as we are, but does not say where OpenAI processes our data. Its data processing addendum would confirm it.
- Anthropic — Anthropic's Consumer Terms, under which this ranking runs on our own Claude subscription, name Anthropic, PBC for a user outside the European Economic Area, Switzerland and the UK, as we are, but do not say where Anthropic processes our data. A statement of the processing location from Anthropic would confirm it.
- Google — Google's contracting-entity page names Google Cloud EMEA Limited for a customer billed in Europe, the Middle East or Africa, as we are, but does not say where Places and Maps requests are processed. Google's own terms for the Maps service, where they name a location, would confirm it.
- Google Workspace — Google's contracting-entity page names Google Cloud EMEA Limited for a Google Workspace customer billed in Europe, the Middle East or Africa, as we are, but does not say where Workspace stores mail. The data-region setting of our Workspace account would confirm it.
- Google Analytics — The Google Analytics Terms of Service name Google LLC, but Google does not say where Analytics data from a property like ours is processed, and Google Analytics offers no choice of location. A Google statement of the processing location would confirm it.
The list above is the processors we instruct — including Google Analytics, which measures traffic on duqqan.app itself once you allow it in the cookie banner. Microsoft Clarity, which records visits there after the same consent, is not on it, because Microsoft collects that data as an independent controller rather than on our instruction (section 2). The list does not include the analytics or advertising tags a business may switch on for its own site — Meta Pixel, Hotjar and the rest, and a business’s own Google Analytics or Clarity property too. There, that business chooses the vendor and is the controller for what it collects, and we render what it configured. Its Google tags — Google Tag Manager included — load with the page in Google’s consent mode, which tells them to store no analytics or advertising cookies on a visitor’s device until the visitor allows them, though Google may still receive basic signals from them without cookies. The tags a business adds inside its own Tag Manager container follow the consent settings that business gives them there. Every other tag we render loads only after the visitor allows it in the consent banner on that site, and not at all if they reject it. Our Cookie Notice lists those separately, and Integrations shows which are available. Some websites we build — demos, and the sites made from them until the business replaces those photographs — use licensed stock photographs from Unsplash. Unsplash requires those photographs to be loaded from its own servers, so when you view such a page, or see those photographs in the Duqqan panel, your browser sends Unsplash your IP address and the usual details of the request. Each photograph is credited to its photographer in the page’s footer. When a business owner connects a WhatsApp number from the Duqqan panel, the panel opens Meta’s own sign-up window, which loads Meta’s software from connect.facebook.net in the owner’s browser, so Meta Platforms receives that browser’s IP address and the usual details of the request, under Meta’s own terms.
9. WhatsApp Business Platform data
When a business using Duqqan connects its own WhatsApp Business number, orders, bookings, and enquiries reach it on WhatsApp. Sending on a connected number — the business’s replies, the messages its customers agreed to and its WhatsApp assistant’s answers — is part of the WhatsApp add-on, and starts as soon as WhatsApp sending is live on Duqqan. We operate that connection to the WhatsApp Business Platform on the business’s behalf and under its instructions. For the conversations between a business and its customers, the business is the controller and we are its processor. WhatsApp LLC (WhatsApp Ireland Limited for customers in the EEA and the UK) processes those messages as part of delivering WhatsApp, under Meta’s own terms.
When a business connects a number, we receive and store only what the feature needs (“Platform Data”):
- Account identifiers — the WhatsApp Business Account ID, phone number ID, the display phone number, and the access token that authorises us to send on its behalf.
- Message content and metadata — the text and media of messages sent to and from the business’s number, the customer’s phone number and WhatsApp profile name, message identifiers, timestamps, and delivery/read statuses.
- Message templates — the templates a business registers with Meta and their approval status.
We use Platform Data only to deliver the messaging feature to the business that connected the number: routing an incoming message to that business, sending its replies and the messages its customers agreed to by ticking the WhatsApp box on its enquiry form or its order form, showing its conversation history in its own panel, reporting delivery failures, and — for a customer who asked on the business’s site to be contacted there — letting the business’s WhatsApp assistant answer (section 6). We do not sell it, use it for advertising or ad targeting, build profiles from it, use it to train AI models, or share it with any business other than the one it belongs to. Each business’s conversations are isolated at the database level, the same way the rest of its data is (see “How we keep it safe” below).
A business may disconnect its number at any time from its Duqqan settings. We then unsubscribe from that account’s messages, stop sending on it, and delete our stored copy of the access token. Deleting our copy does not revoke it at Meta — only you can do that, at any time, from Meta’s own Business settings — but it means we can no longer act on your account. The number’s two-step registration PIN stays encrypted with the rest of the record, because re-registering the same number needs the PIN it already has; it is deleted with the rest of the business’s data. We retain conversation history — together with the internal notes the business’s team adds to a conversation, which are never sent to the customer — for as long as the business uses Duqqan, because it is the business’s own record of its customer enquiries; it is deleted with the business ninety (90) days after its plan ended — for a plan that ended before 6 November 2026, ninety days after that date — or once a domain the business registered through us has ended or moved away, if that is later, and not while we have it suspended if it started a plan with us or paid us by bank transfer or cash (section 15); or sooner on request. When a customer sends STOP to a business’s number, we keep a record of that number and when it sent STOP, for that business only, so that the messages the business starts stop reaching it until the customer opts in again; the record is deleted with the business’s data. To have WhatsApp data deleted — whether you are a business or a customer who messaged one — see Data Deletion or email [email protected].
10. Shopify store data
A connected Shopify store is a separate add-on, coming soon; this section applies once that add-on is available. A business using Duqqan can then connect its own Shopify store so that its catalogue and orders appear alongside its conversations. As with WhatsApp above, the business is the controller and we are its processor: we read from that store on its instruction and only for as long as it keeps the connection. Shopify is the business’s own platform, not a sub-processor we instruct on our own behalf, which is why it does not appear in the table in section 8.
When a business connects a store, we receive and store only what the feature needs:
- Store identifiers — the
.myshopify.comdomain, the store identifier, the scopes granted, and the access and refresh tokens that authorise us to read on its behalf. Both tokens are encrypted with a key unique to that business. - Product data — title, handle, description, status, price range, variants and the address of the product image, which stays on Shopify’s servers rather than being copied to ours. None of this is personal data.
- Order data — order number, total, currency, payment and fulfilment status, the date it was placed, and the line items. Where the order carries them, we also store the customer’s name and phone number, each encrypted with that business’s own key.
We deliberately do not copy the customer’s email address, billing or shipping address, or any payment detail — a Shopify order contains all of them, and none is needed for what this feature does.
We use this data only to deliver the feature to the business that connected the store: showing its catalogue and orders in its own panel, and matching an incoming WhatsApp conversation to that customer’s orders so the business can answer with context. The match is on an exact, per-business hash of the phone number, so the same customer is not identifiable across two businesses. We do not sell this data, use it for advertising, build profiles, or message a customer because their number arrived in an order — a phone number in a Shopify order is not consent to contact it, and nothing is sent unless the business confirms its own lawful basis and the customer has opted in on WhatsApp.
A business can disconnect at any time from its panel. When it does, or when it uninstalls the app, the store connection and everything mirrored from it is deleted. A connection still in place when the business’s plan ends is deleted with the rest of its data ninety (90) days after the plan ended — for a plan that ended before 6 November 2026, ninety days after that date — or once a domain the business registered through us has ended or moved away, if that is later, and not while we have the business suspended if it started a plan with us or paid us by bank transfer or cash (section 15). We also action Shopify’s own customer data requests and erasure requests when a merchant or a customer raises one through Shopify.
11. Demos from public information
For our outbound flow we may build a private demo site for a business using its publicly available information and email a link to it. If you are that business and would prefer we did not, tell us and we will delete the demo, its lead record, and its images and files, and not contact you again (section 15 explains the one thing we keep to hold to that): email [email protected].
12. Social logins
You can register and sign in with your email address and a one-time code we send to it, or with a Google or Facebook account where the sign-in page offers them. Which of them it offers can change. When you continue with Google, it sends us your name, your email address, whether Google has verified that address, a link to your profile picture and an identifier for your Google account. Facebook sends us your name, your email address, a link to your profile picture and an identifier for your Facebook account. We ask for nothing else: Google’s openid, email and profile scopes and Facebook’s email and public_profile. We keep your name and email address, which provider it was, that account identifier and the date you connected it. We do not keep a password or your profile picture. The provider also hands us short-lived tokens for that one sign-in; we use them only then, to read the details above, and keep none of them, so we cannot read or post anything in your Google or Facebook account later, and we get no list of your friends or contacts. Facebook never joins an existing Duqqan account by itself: if an account already uses your email address, sign in with the email code and connect Facebook from Your account › Security. Google joins an existing account only when Google confirms that the address is verified. If you turned on two-step verification, you sign in with the email code and your authenticator code; Google and Facebook cannot be used for that account. To tie the provider’s answer to the browser that asked, which protects against a forged sign-in, continuing with a provider (or connecting one in Your account › Security) sets a cookie for five minutes (see the Cookie Notice) and keeps a record of the attempt for up to ten minutes. Google (Google LLC) and Meta (Meta Platforms, Inc., or Meta Platforms Ireland Limited for people in the European Region) handle your sign-in with them under their own privacy policies, as independent controllers of it; they are not our sub-processors. You can disconnect Google or Facebook at any time in Your account › Security, and we email the account’s address whenever one is connected or disconnected. Disconnecting, or deleting your account, removes the link we keep. It does not remove Duqqan from your Google or Facebook account; you can do that in their settings too (see Data Deletion).
13. Sharing your information
Beyond the providers above, and the domain registrar and registry described in section 2 when you buy a domain through us, we share personal data only when required by law, to protect our rights, or as part of a business transfer (such as a merger or sale), in which case we will continue to protect it under this policy. We never sell your personal data.
14. International transfers
Some of our providers process data outside the UAE (for example in the EU or US). Where that happens, we rely on appropriate safeguards to protect your data.
This includes our own infrastructure, which is worth stating plainly rather than leaving it to be read out of the table in section 8: our application and database are hosted in Germany (OVHcloud), and encrypted backups are held with Cloudflare. So data you give us is processed outside the UAE from the moment we receive it — not only when a third-party tool is involved.
15. How long we keep it
Demos expire after about seven (7) days. An expired demo goes offline — its address shows a “page not found” page and the access code no longer opens it — but it is not deleted at once: it is kept for the period below, so that the business can still choose a plan and bring the site back. A job that runs every day then deletes it with its images and files, but keeps the lead record behind it; the images and files of a version we replaced earlier are removed separately, as the table shows. The schedule, what it never touches, and what outlives a deletion:
| What | When it is deleted |
|---|---|
| A sign-up abandoned before its demo was built | Not deleted on a schedule — kept until you ask us to delete it |
| A demo that expired and was never bought — no plan, no free trial and no payment to us | Ninety (90) days after it expired |
| A demo we built but never sent, that was never bought — no plan, no free trial and no payment to us | Ninety (90) days after it was built |
| A demo we took offline (we archived or suspended it) that was never bought — no plan, no free trial and no payment to us | Ninety (90) days after it was taken offline |
| Our record of a business we built a demo for, or whose plan ended — its name, the contact details we hold, our notes and the files we collected for it — after the demo or the business itself is deleted | Not deleted on a schedule — kept until you ask us to delete it |
| Our record of a business we may contact and have not built a demo for — its public details, the contact details we hold, our notes, its outreach score and the picture of its website’s home page we keep with it | Not deleted on a schedule — kept until you ask us to delete it; the score and the picture are deleted with the record |
| Images and files of a site version we replaced | Deleted by a daily clean-up once nothing has been written to them for seven (7) days |
| A business whose plan ended — a free trial that ended included — with its site, its images and files, its orders and their documents, its customers’ enquiries and its WhatsApp conversations | Ninety (90) days after the plan ended — for a plan that ended before 6 November 2026, ninety days after that date; a business still holding a domain registered through us goes once that registration has ended or moved away |
| A business that started a plan with us (a free trial included) or paid us by bank transfer or cash, and that we have suspended | Not on this schedule while it stays suspended |
| An account — the login itself | Never on this schedule — only at your request |
| A deleted record, in our database backups | Seven (7) days after the backup was taken — each backup is kept that long, then deleted |
| A copy of an image we published for a site or a demo — a photo, a logo, a screenshot — already fetched into Cloudflare’s cache or a viewer’s browser | Up to a year after we delete the original, because these images are published with a one-year cache lifetime |
| Payment records | Not deleted — the law requires payment records to be kept: Stripe, our payment processor, keeps its own record of every payment made through it; we keep the payment notifications we received; and we keep the record of each payment made to us by bank transfer or cash — its amount, currency, period, date and method, with nothing that names you |
| The do-not-contact fingerprint described below | Never — it has no expiry |
| A record that the deletion happened, with no name or contact details | As long as we keep deletion records |
| If we found the business in Diojen Tech’s own prospect pool, which Duqqan shares with other Diojen Tech products: the pool’s record of its public details, such as its name, phone, email, website and social profiles | Not deleted — it stays in the pool; a deletion at your request, or of a record we had marked do-not-contact or of the demo we built for it, marks it do-not-contact for Duqqan |
| If the business bought or ordered a domain through us: the domain’s DNS zone in our Cloudflare account, which holds the domain name and its DNS records and nothing else about you | Not deleted with the business — it stays in our Cloudflare account until it is removed |
When we delete a demo, a business, a lead record or an account at your request, we keep a one-way, keyed fingerprint of the email addresses and phone numbers in the business’s own contact and billing details and in our lead records for it, of the email address a deleted account signed in with, and of the Google Maps place ID and our internal lead reference where we hold them — never the details themselves. We keep the same fingerprint whenever a record we had marked do-not-contact is deleted, or the demo we built for it is — because the person asked us not to contact them, or because their address rejected our email or reported it as spam — whether that happens at their request or on the schedule above. The fingerprint has no expiry, because that promise has none, and we use it for nothing but recognising those details if they reach us again, so that we do not contact that person again. It never stops anyone signing up with us on their own. To have a demo, a business, a lead record or an account deleted sooner than the table says, or at all where it says never, email [email protected].
Records of your cookie choice (section 2) are kept for twenty-four (24) months from the date of the decision, then deleted by a daily job. The bound is measured from when you decided, not from when the record reached us, so a choice made long ago is not held longer because we learned of it late.
Orders mirrored from a connected Shopify store (section 10) have two fixed bounds, applied by a daily job. After twelve (12) months the customer’s name and phone number are erased from the mirrored order while the order itself — amount, date, line items — remains, because that record belongs to the business and outlives our need to hold the person. After twenty-four (24) months the order is deleted outright. Both bounds are measured from the date the order was placed, not from the date we received it, so a store’s existing history is subject to them from the moment it connects.
16. How we keep it safe
We protect data in transit with encryption, isolate each business’s data at the database level, and restrict internal access. Administrative access is separate from customer accounts and protected by two-factor authentication. No method of transmission or storage is 100% secure, but we work to protect your data using appropriate measures.
17. Data breaches
If a personal-data breach occurs that is likely to affect your rights, we will notify the relevant authority and affected users as required by the UAE PDPL.
18. Marketing communications
We may send you product news and marketing about Duqqan where permitted. You can opt out at any time with the “Product news and tips” switch on the Security page of your account in the Duqqan panel, or by emailing [email protected]. We will still send essential service and billing messages.
19. Your privacy rights
Subject to applicable law, you may request access to, correction of, or deletion of your personal data; object to or restrict certain processing; and withdraw consent. To exercise a right, email [email protected]. You may also complain to the UAE Data Office.
20. Do-Not-Track
Some browsers send a “Do-Not-Track” signal. As there is no agreed standard for it, we do not respond to it specifically. Instead, analytics cookies load only if you accept them, and you can change or withdraw that choice at any time using the Cookie settings link in the footer (see our Cookie Notice). Withdrawing stops the analytics; it does not erase the record that you had allowed them earlier, which is kept for the period in section 15 and is what shows the withdrawal was honoured.
21. Children
Duqqan is for businesses and is not directed at children. We do not knowingly collect data from anyone under 18; if we learn we have, we will delete it.
22. Reviewing, updating, or deleting your data
You can review and update most of your information from your account settings, including the email you sign in with. Your profile page also downloads a copy of your account data — your account, the sign-in methods connected to it and when each was connected, sign-in sessions, memberships, invitations, email preferences, connected AI assistants, and the business details, WhatsApp number, interests, description and offer you gave when you started a site, where the visit that brought you there came from, with a list of the photographs you added (the photographs themselves are not in the file). A business’s published website and its orders are downloaded from inside the business, where its plan and your role allow it. To request a copy of anything else, or to have your data corrected or deleted, email [email protected] and we will respond within a reasonable time, subject to applicable law.
23. Changes and contact
We may update this policy and will revise the date above; for material changes we will give reasonable notice. Questions about this policy or your data? Email [email protected]. Diojen Tech FZ-LLC, VUPR0809, Compass Building – Al Hulaila, Al Hulaila Industrial Zone-FZ, Ras Al Khaimah, United Arab Emirates.