Privacy

• Content you submit (text or a URL) so we can score, generate, or route it for review.
• Scan results (score, verdict, and the checks that ran) stored in your tenant's audit log.
• Account data: your email, a hashed password, and optional phone; plan and credit balance.
• Operational data: API keys, request metadata, and rate-limit counters needed to run and secure the Service.

• Submitted drafts can be stored with scan history, Core objects, saved drafts and review records in your workspace.
• We do not sell scan data, account data, or anything else.
• Optional analytics and performance telemetry, including Vercel Analytics and Speed Insights, load only after analytics consent and respect Global Privacy Control. We do not sell this data to advertising networks.
• We do not train any AI model on your content.

Where GDPR applies, we process personal data on these bases: to perform our contract with you (providing the Service, billing); our legitimate interests (securing and improving the Service, preventing abuse); your consent (optional features such as AI rewrites); and to meet legal obligations.

Account data (your email and a password hash managed by Better Auth) is stored in our own database (Supabase Postgres, US East). We do not use a third-party authentication provider. Purchases are processed by Paddle.com, our reseller and Merchant of Record. Paddle collects and processes your payment and billing details as an independent controller under its own privacy notice. We receive only what we need to manage your subscription (for example name, email, country, plan and transaction status). We never see or store your card details.

Scoring runs entirely on our servers and never sends your content to a third-party AI. If you request a rewrite or another AI feature, the content needed for that request is sent to a configured writing provider. MiniMax is currently used for rewrites. Configured alternatives include Zhipu AI (z.ai), Anthropic, or OpenRouter and its upstream model hosts. A request may fall back to another configured provider when one is unavailable. Dokeo does not train models on your content. Provider retention and data-use terms depend on the service and account configured; contact us for the current provider and terms before submitting sensitive material.

We use these subprocessors to run the Service:

• Modal - application hosting for the API (US East).
• Supabase - database for accounts, scans and settings (US East).
• Cloudflare - DNS and edge network in front of dokeo.co.
• Vercel - marketing site and app front end.
• Zhipu AI (z.ai) - optional AI features, when configured.
• MiniMax - writing and rewrites requested by users.
• Anthropic - optional writing provider, when configured.
• OpenRouter and its selected upstream hosts - optional model routing, when configured. Hosts must be reviewed before enabling customer traffic.
• Nango - connected-source authentication and API proxying, when enabled.
• Composio - sign-in and token storage for third-party apps you connect, when enabled.
• Brevo - verification and password-reset email delivery, when enabled.
• Paddle - payment processing as Merchant of Record. Paddle is an independent controller for payment data.

We will give notice of new subprocessors to customers under a DPA before they process your data.

We use a single first-party session cookie to keep you signed in. No third-party tracking cookies, no retargeting. Optional analytics, if ever enabled, are strictly opt-in.

The Service runs in the US today: the API on Modal and the database on Supabase, both in US East, with the front end on Vercel. EU / regional data residency is planned but not yet live, and we will not claim it until it ships. If you access the Service from outside the US, your data is transferred to and processed in the US; where required, such transfers rely on appropriate safeguards (e.g. Standard Contractual Clauses) available under our DPA.

We keep account data for as long as your account is active. Scan/audit-log entries are retained for your tenant until you delete them or close your account. On deletion we remove your data from production within 30 days, excluding data we must keep for legal or accounting reasons.

Traffic uses TLS (HTTPS) via Vercel, Modal and Supabase. Data at rest is encrypted by the hosting providers (Supabase disk encryption). Stored credentials are also encrypted by Dokeo with Fernet (AES-128-CBC with HMAC). API keys are stored only as SHA-256 hashes and checked in constant time. Pixel tokens and webhooks are HMAC-signed. Session cookies are HttpOnly, Secure, and SameSite=Lax. User-supplied URLs are SSRF-guarded before we fetch them. We have not completed a SOC 2 audit and do not claim one. See our Security page for the current details.

Depending on where you live (GDPR, UK GDPR, CCPA/CPRA and similar), you may have the right to access, correct, export, or delete your personal data, to object to or restrict certain processing, and to withdraw consent. We do not sell personal data. To exercise a right, email privacy@dokeo.co; we action verified requests within 30 days.

For customers who need one, we offer a Data Processing Addendum covering our processing of personal data on your behalf, subprocessors, and international transfer safeguards. Request it at legal@dokeo.co.

Dokeo is a business tool and is not directed to children under 16. We do not knowingly collect their data.

We will post the updated policy here with a new date and, for material changes, give at least 14 days' notice. The date at the top always reflects the current version.

Questions or a privacy request? Get in touch or email privacy@dokeo.co.