1. Who we are and what this notice covers
1.1. DIVAI LLC (“DIVAI,” “we,” “us”) is an Alaska limited liability company, Active and in Good Standing. We operate divai.ai and app.divai.ai. Contact: privacy@divai.ai.
1.2. This notice explains the cookies and similar technologies we use on divai.ai and app.divai.ai, and the choices you have.
1.3. Our Privacy Policy (Related policy) explains how we handle personal data more broadly.
2. Categories we use — two only
2.1. We use cookies and similar technologies in two categories only. We do not use advertising cookies, cross-site tracking pixels, social-media trackers, or remarketing technologies. Draft item pending confirmation before activation.
2.1.1 Essential (strictly necessary)
Required for the Service to function:
- authentication and session management (provided by our authentication provider);
- security and abuse prevention; and
- infrastructure functions such as load balancing.
These are described here to be verified against the live site before publication. Draft item pending confirmation before activation. They cannot be switched off because the Service cannot operate without them. They are not used for advertising or cross-site tracking.
2.1.2 Analytics (planned — Google Analytics 4)
If and when enabled, analytics help us understand aggregate usage so we can improve the product. Analytics are off by default. Analytics cookies and scripts are set only after you explicitly accept them. Declining means no analytics cookies or scripts are set or loaded at all.
3. Your choices — consent banner
3.1. When you first visit, the consent banner offers these options:
| Option | What it means | Technical effect |
|---|---|---|
| Accept | Essential (always on) plus analytics | Analytics script loads and analytics cookies are set; your choice and the time are recorded |
| Decline | Essential only | Analytics script never loads; no analytics cookies are created; your decline and the time are recorded |
| Manage | Granular per-category control | Essential is on and locked; the analytics toggle defaults to off; saving applies your choices and records them |
3.2. Accept and Decline are presented with equal visual prominence. There are no pre-toggled analytics switches and no extra friction on the decline path.
3.3. Consent is never assumed from continued browsing, scrolling, or closing the banner. Dismissing the banner without a choice means analytics stay off.
3.4. You can change or withdraw your choice at any time through the persistent “Cookie settings” entry point. Draft item pending confirmation before activation. Withdrawal takes effect immediately and stops all further analytics collection.
4. Permanent product rules (policy commitments)
These rules are permanent product policy. The published notice must never claim behavior the product does not implement.
4.1. Consent-gated analytics. No analytics cookie, script, or pixel loads or fires before explicit consent. Analytics are blocked at the script-loader level until consent exists.
4.2. Decline is effective. Selecting “Decline” results in zero analytics cookies or scripts being set or loaded.
4.3. No dark patterns. Accept and Decline are symmetric. No confirm-shaming. No hidden decline path.
4.4. No implied consent. Consent is never inferred from browsing, scrolling, or banner dismissal.
4.5. Consent record. Each consent decision (choice, categories, timestamp, notice version) is recorded and auditable. Draft item pending confirmation before activation.
4.6. Easy withdrawal. Withdrawing consent is as easy as giving it, takes immediate effect, and stops analytics going forward.
4.7. Global Privacy Control (GPC). We treat a GPC signal as a decline of analytics. Draft item pending confirmation before activation.
5. Cookie table (skeleton — complete and verify before publication)
| Cookie name | Provider | Purpose | Category | Duration |
|---|---|---|---|---|
| Pending confirmation — session cookie(s) | Authentication provider (Clerk) | Authentication / session integrity | Essential | Pending confirmation |
| Pending confirmation — security / CSRF token cookie | Authentication provider or first-party | Security, abuse prevention | Essential | Pending confirmation |
| Pending confirmation — load-balancer / hosting cookie | Hosting providers (Render / Hostinger) or CDN | Request routing | Essential | Pending confirmation — remove row if none are set |
| Pending confirmation — consent preference cookie | First-party | Remembers your accept / decline choice | Essential | Pending confirmation Draft item pending confirmation before activation. |
_ga |
Google Analytics (GA4) | Distinguish users in aggregate analytics | Analytics | Pending confirmation configured retention (default ~2 years) |
_ga_<container-id> |
Google Analytics (GA4) | Persist analytics session state | Analytics | Pending confirmation configured retention |
Rule for completion: every row must be verified against a real browser session on the live site and app before publication. No row may be published as guessed. No cookie or tracker may be added to this table unless it actually exists in the product.
6. Google Analytics configuration (planned)
6.1. GA4 is planned, not confirmed live. Before enabling it: Draft item pending confirmation before activation.
- confirm whether GA4 is on the marketing site only or also inside app.divai.ai;
- confirm consent-gating per rule 4.1;
- confirm IP handling and data-sharing settings; and
- confirm that GA4 configuration does not constitute a “sale” or “share” of personal data under applicable US state law. Draft item pending confirmation before activation.
7. Payments-related technologies
7.1. Payments are not yet active. No payment-related cookies or scripts (including any payment-processor fraud-prevention scripts) are described in this notice. This section will be updated, and the cookie table re-verified, before payments are activated. Draft item pending confirmation before activation.
8. Contact
8.1. Questions about this notice or your choices: privacy@divai.ai.
9. Language parity note (EN / AR / ES / FR / TR)
9.1. This notice and the consent banner will be translated into Arabic, Spanish, French, and Turkish. This English version is the canonical drafting source.
9.2. Consent given in any supported language is equally valid and is recorded identically.
9.3. Arabic requires a right-to-left-safe banner layout. Draft item pending confirmation before activation.
9.4. Prevailing-language clause (the English version governs in case of translation conflict): Draft item pending confirmation before activation.