Privacy Policy

This policy covers duckk.org, the duckk chat assistant (web and any apps), guest access, the API gateway at api.duckk.org/v1, and related emails and support. The controller is Duckk, Inc. — reach us at privacy@duckk.org.

Developer note: if you send your own end-users' data through the API, you are the controller of that data and Duckk acts as your processor. You must give those users a privacy notice that covers processing by Duckk and the selected upstream model provider.

This policy does not cover the consumer products of upstream providers (for example the ChatGPT or Claude apps), which have their own privacy policies.

Directly from you: sign-up, conversations, uploads, checkout, feedback and support emails.

Automatically: server and CDN logs, quota metering, the first-visit attribution snapshot stored in your browser's localStorage (duckk.attribution.v1 — UTM parameters, gclid, fbclid, referral code, entry path), and optional Firebase Analytics.

From our providers: Clerk syncs your profile when you sign in; payment processors confirm transactions; Cloudflare Turnstile returns a human-verification result.

We do not use your conversations, prompts or files to train any model — see section 5.

When you chat, your message and conversation context are routed through our self-hosted gateway to the upstream provider of the model you selected (OpenAI, Anthropic, Google, Meta, Mistral, DeepSeek, Moonshot/Kimi and others in the catalogue). The provider processes this content to generate a response.

No training on your data: we do not use your content to train any model, and upstream providers are instructed — by contract or API configuration — not to train on traffic routed through duckk.

Features that call specialist services: file parsing sends your document to MinerU for text extraction; web search sends your query to Brave or Exa; code execution runs in an isolated E2B sandbox; image and presentation generation go to the relevant image model. Each receives only the data needed for that task.

Speech features use your browser's Web Speech API; audio is not sent to duckk.

We use only strictly necessary cookies — for authentication sessions (Clerk) and security (Cloudflare) — plus one localStorage entry for attribution (duckk.attribution.v1). No advertising cookies, no cross-site trackers.

Firebase Analytics (GA4) is optional and off unless you enable it; when on, your user ID is SHA-256 hashed before any event is sent to Google. You can withdraw consent at any time in settings, and you can clear attribution data by clearing site data in your browser.

We do not sell personal data or share it for cross-context behavioural advertising. Disclosures beyond this list happen only when the law requires it (court order, fraud investigation).

duckk is made for Africa and served through African points of presence, but some processing happens abroad: model inference typically runs in the provider's US or EU region, and several subprocessors listed above are US-based.

Where the GDPR, POPIA, NDPA or the Kenya Data Protection Act applies, international transfers are safeguarded by Standard Contractual Clauses (SCCs) or equivalent mechanisms with our subprocessors. You can request a copy of the relevant safeguards at privacy@duckk.org.

When you ask us to delete your account, we delete your account data — conversations, files and profile — and retain only the billing and compliance records the law requires.

We use TLS in transit, AES-256-GCM encryption for sensitive fields at rest, rate limiting, Cloudflare Turnstile bot protection, least-privilege access and audit logging of administrative actions.

No method of transmission or storage is 100% secure. If a breach is likely to affect your rights, we will notify you and the competent authority as the law requires. Report vulnerabilities to privacy@duckk.org — we acknowledge reports within 48 hours.

Under laws such as the GDPR, South Africa's POPIA, Nigeria's NDPA and the Kenya Data Protection Act, you may have the right to access, rectify, erase, restrict or object to the processing of your personal data, to data portability, to withdraw consent, and to lodge a complaint with your data-protection authority.

Built into the product: you can export any conversation and delete conversations or your whole account in settings. Deleting your account deletes your account data (conversations, files, profile); billing records are retained as required by law.

For anything else, email privacy@duckk.org from your account email. We respond within 30 days. Reasonable requests are free; manifestly unfounded or excessive requests may be declined with an explanation.

duckk is not directed at children. You must be at least 16 (or the age of digital consent in your country, if higher) to use the service. We do not knowingly collect personal data from children; if you believe a child has provided data, contact privacy@duckk.org and we will delete it promptly.

We may update this policy as the service evolves. For material changes we will notify account holders by email and show a banner on duckk.org at least 14 days before the new version takes effect. Prior versions are available on request.