Skip to content

Privacy Policy

Last updated: October 2026

This Privacy Policy explains how Coda One ("we", "us") collects, uses, and protects your information when you use codaone.ai ("the Service") and the Coda One Chrome extension.

1. Analytics

We use four analytics sources, each with a specific purpose:

  • First-party event tracking — our own endpoint /api/track records usage events (which tool was used, when a daily limit was hit, checkout intent, install and update events from the extension) into our database. Each event row stores the event name, event metadata (for example tool: "humanizer"), a shortened one-way hash of your IP address, user agent, referrer, and page path. We never record the text you process with the tools. After you accept optional cookies, the browser also keeps a session note (coda_entry) of the landing path, an optional ref, and the referring host. That note is not written before you accept, and it is removed if you reject or close the tab.
  • Plausible Analytics — privacy-friendly aggregate pageviews. Plausible does not use cookies and does not collect personal data.
  • Google Analytics 4 (GA4) — helps us understand acquisition channels and device breakdowns when it is enabled. Google's analytics script is not loaded, and nothing is sent to Google Analytics, until you accept. After you accept, analytics storage is turned on and advertising storage stays off. Page-view auto-send stays off; we fire custom events for the same funnel signals described above. If no measurement ID is set at build time, GA4 is not loaded.
  • Ahrefs Web Analytics — complements Plausible with SEO-specific signals (organic search traffic, Core Web Vitals). Cookie-free.

None of these analytics sources receive the text you paste into our tools. Event payloads are metadata only (tool name, mode, plan tier, referrer, hashed IP).

Usage records. Each time a writing tool runs, we record the tool, the mode, word counts, timing, whether the result came from the cache, the model that answered, any referral tag on the request, which test version of the page you saw, your account ID if you are signed in, and a shortened one-way hash of your IP address. Daily counters enforce the free limit: by account if you are signed in; otherwise by a random ID stored in your browser (codaone_client_v1, see the Cookie Policy) together with a looser count per IP hash, or by the IP hash alone if browser storage is unavailable. These records never contain your text.

Legal basis: Legitimate interest for the first-party event records, Plausible, and Ahrefs. Those three do not set cookies. The session note above is written only after you accept. Consent for Google Analytics and for the partner-attribution cookie (coda_aff_ctx). Nothing is sent to Google Analytics until you accept.

2. The Writing Tools — What Each One Sends, and Where

We run the AI Detector, AI Humanizer, AI Rewriter and Grammar Checker. They do not all behave the same way, so this section takes them one at a time. In every case the text travels over HTTPS and is used only to answer that request. We do not use it to train any model, and we do not license it to anyone for training.

  • AI Detector (/api/tools/detect) — scored entirely on our own servers by our own code. Your text is not sent to any AI provider or other third party.
  • AI Humanizer, AI Rewriter, Grammar Checker (/api/tools/humanize, /rewrite, /grammar) — your text is sent to a large-language-model provider to produce the result: OpenAI (GPT-4o mini) by default. If that request fails, it is retried with Google (Gemini), then DeepSeek, on every plan, signed in or not. Each provider receives the text under its own API terms. OpenAI's API terms say API data is not used to train its models by default, and Google's Gemini API terms say the same for paid use, which also covers a UK developer's unpaid quota. DeepSeek's Terms of Use (section 4.3) allow it to use de-identified, encrypted inputs and outputs to develop and improve its services, including its models, and its API offers no way to opt out of that. The site always asks for OpenAI first. A request on a paid plan can name Gemini or DeepSeek instead, and then goes to that provider first; otherwise a request reaches DeepSeek only when OpenAI and Google have both failed.

Caching. Tool results are cached at Cloudflare's edge under a SHA-256 hash of the input, so an identical submission returns instantly instead of being re-billed: up to 24 hours for the detector and up to 6 hours for the humanizer and grammar checker. The cached result contains text: the detector's result includes your text split into sentences, because it scores each one; the grammar checker's includes the corrected text; the humanizer's includes the rewritten text. A cached result is returned only to a request with exactly the same text and settings, and it expires on its own. The rewriter is not cached.

Detector feedback. If you report a detector result as wrong, we keep the label you chose, the score, the word count, your note, and a random ID stored in your browser. Your text is kept with the report only if you tick the box to share it, and then only up to 6,000 characters, and a person may read it. We use these reports to review where the detector goes wrong.

Legal basis: Contractual necessity (running the tool you asked us to run).

3. Cookies

For full details, see our Cookie Policy. Strictly necessary cookies: the login session, the record of this choice, and three short-lived sign-in cookies (oauth_state and oauth_return_to for 10 minutes during Google sign-in, codaone_pending_totp for 5 minutes during two-step sign-in), listed in the Cookie Policy.

  • codaone_session — A session identifier set when you log in. HttpOnly, Secure, SameSite=Lax. Expires after 30 days or when you log out. This cookie is strictly necessary for the Service to function for logged-in users and does not require consent under PECR.
  • coda_consent — Remembers whether you accepted or rejected optional cookies, and when. Written by the page, so it is not HttpOnly. It expires 13 months after the choice and is not renewed on later visits. The same choice is also kept in this browser as consent_v1 (localStorage) so the page can apply it before the next request. That record expires with the choice.

We serve no advertising cookies and sell no data to ad networks. Two other cookies may be present:

  • _ga, _ga_P59Q97VD1N — set by Google Analytics 4 only after you accept, to distinguish one browser from another across visits. Analytics, not advertising; we do not use them for ad targeting or remarketing. Change the choice from Cookie settings in the footer or on the cookie policy page.
  • coda_aff_ctx — attribution, set for 30 days. HttpOnly, Secure, SameSite=Lax. It holds the partner code if you came through a partner link, the landing page, the referring site, any utm parameters, and the time. It is set only after you accept optional cookies, and only if you arrived through a partner link or with a utm_ campaign parameter. Until 27 August 2026 it was also written on any first visit from another website, which meant most organic arrivals carried it; that arm has been removed. It never contains your name, email, or the text you put into a tool.

Plausible and Ahrefs Web Analytics are cookie-free. Affiliate destination sites may set their own cookies when you click outbound links.

4. User Accounts

You may create an account using Google OAuth, Telegram Login, or email and password. When you create an account, we store the following in Cloudflare D1 (edge database):

  • Profile data: email address, display name, avatar URL (from your OAuth provider, if applicable)
  • Authentication: for email/password users, a salted PBKDF2 hash of your password (we never store plaintext passwords); for OAuth users, provider ID
  • Sessions: server-side session records linked to your account, stored in D1
  • Activity data: favorites, collections, reviews you write

Telegram Login: When you sign in with Telegram, we receive your Telegram user ID, first name, last name, username, and profile photo URL from Telegram's servers. Telegram does not provide your phone number or email address to us.

Legal basis: Contractual necessity (providing the Service you signed up for).

5. Email Subscribers

If you subscribe to our newsletter, we store your email address to send you updates about AI tools and pricing changes. You can unsubscribe at any time via the link in every email. We never sell or share your email with third parties.

Legal basis: Consent (you actively subscribe).

6. User-Generated Content (Reviews)

When you submit a review, the following is stored: your display name, star rating, review text, and submission date. Reviews are publicly visible and associated with your account.

We apply anti-spam measures: reviews from new accounts with low ratings may be held for moderation. Reviews with multiple community reports are automatically hidden pending review.

You can edit or delete your own reviews at any time. If you delete your account, all your reviews are permanently deleted.

Legal basis: Consent (you choose to submit reviews) and legitimate interest (maintaining content quality).

7. Contact Form & Tool Submissions

When you contact us or submit a tool, we store your name, email, and message content. Contact messages are retained for 12 months, then deleted. Tool submissions are retained as part of our directory operations.

Legal basis: Consent (you choose to contact us) and legitimate interest (operating the directory).

8. Payment Processing

We use Stripe to process subscription payments. When you subscribe to a paid plan:

  • What Stripe receives: your name, email, payment card details, and billing address
  • What we store: Stripe customer ID, subscription ID, plan type, and billing status — we do not store your full card number, CVV, or other sensitive payment data
  • What Stripe stores: your payment method details are stored securely on Stripe's PCI DSS Level 1 certified infrastructure

Stripe may use your data in accordance with their Privacy Policy. We share only the minimum data necessary to process your payments.

Legal basis: Contractual necessity (processing payments for the Service you subscribed to).

9. Affiliate and Partner Links

Some links on this site are affiliate links routed through /go/[tool-name]. We log aggregate click counts (not personally identifiable). The destination site may use cookies to track the referral, governed by their own privacy policy.

Separately, if you arrive through a partner's link and you accept optional cookies, we record that click: the partner's code, the page you landed on, the referring URL, any utm parameters, your user agent, and a one-way hash of your IP address (not the address itself). This is how a partner gets credited if you later subscribe. If you accepted optional cookies and then create an account, the signup is linked to that click so the commission can be calculated. If you do not accept, the click is not recorded and the signup is not linked.

Legal basis: Consent for the attribution cookie and for the click record it points at.

10. Chrome Extension

The Coda One Chrome extension runs locally in your browser and only contacts https://www.codaone.ai. It requests the following permissions:

  • activeTab — read the current tab's selected text when you right-click or press a keyboard shortcut, so the selected text can be sent to the chosen tool.
  • contextMenus — show the "Coda One" submenu inside the right-click menu.
  • storage — remember your last-used writing mode, daily usage counter (for the popup display), and a short-lived cache of your Coda One plan tier so paid users don't see a free-tier counter inside the extension.
  • scripting — read the selected text via keyboard shortcut from any page.
  • host_permissions: https://www.codaone.ai/* — the only network destination the extension talks to.

What the extension sends to our servers:

  • The text you select and run a tool on (Detect AI, Humanize, Rewrite, Grammar Check — the four tools in the v1.2.2 right-click menu) is sent over HTTPS to /api/tools/* for processing, and onward to the same subprocessors as on the website — see Section 2. If you are not signed in, it is not stored in your account after the response is returned. If you are signed in to codaone.ai in the same browser profile, the request is attributed to your account and, for Humanize, Rewrite and Grammar, the input and output are saved to your tool history — see Data Retention below.
  • Anonymous usage events (tool name, whether a daily limit was hit, when you opened the popup, install and update signals) are sent to /api/track. These events contain metadata only — the text you process is never part of an event payload.
  • If you are logged in to codaone.ai in the same browser profile, the extension will read your session cookie so the popup can show your paid plan status. No token or cookie leaves codaone.ai's domain.

What the extension never sends:

  • The full HTML or text of the pages you visit.
  • Your browsing history.

Remove the extension at any time from chrome://extensions/. Removal clears all extension-local storage (counters, preferences, plan cache).

11. Bot Protection

We use Cloudflare Turnstile on forms to prevent automated spam. Turnstile does not set cookies. To tell people from bots it processes your IP address and signals from your browser, under Cloudflare's Turnstile privacy terms.

12. Security

We protect the Service using HTTPS, Content Security Policy headers, rate limiting, PBKDF2 password hashing (100,000 iterations), and HttpOnly session cookies. No security measure is perfect — if you believe your account has been compromised, contact us immediately.

13. Data Storage & International Transfers

Data is stored in Cloudflare D1 (edge database) and processed on Cloudflare's global network, which means your data may be processed in countries outside your country of residence, including countries outside the European Economic Area (EEA).

Cloudflare is certified under the EU-U.S. Data Privacy Framework and maintains Standard Contractual Clauses for international transfers. For details, see Cloudflare's Privacy Policy.

14. Data Retention

  • User accounts: until you delete your account
  • Reviews: until you delete them or your account
  • Newsletter subscriptions: until you unsubscribe
  • Contact form messages: 12 months, then deleted
  • Tool submissions: retained indefinitely as part of our directory
  • Tool history (logged-in accounts only): when you are signed in, the text you submit to the AI Humanizer, AI Rewriter or Grammar Checker and the text it returns are saved to your account's tool history (up to 2,000 characters of each for the Humanizer, 5,000 for the other two), visible at /dashboard/tool-history. You can delete any entry, or all of them, from that page. Otherwise retained until you delete your account, which erases them. Entries saved by tools we have since withdrawn are still listed there and are deleted the same way. The AI Detector never writes to tool history, and neither does signed-out use of any tool.
  • Cached tool results (edge): up to 24 hours for the detector, 6 hours for the humanizer and grammar checker, then discarded automatically. Keyed by a hash of the submission; see Section 2.
  • Partner click and attribution records: kept while the partner account exists, because a commission has to stay auditable. Deleting your account unlinks you from any attribution row (see Section 9).
  • Sessions: 30 days, or until you log out
  • Payment records: retained as long as your account exists or as required by tax/legal obligations
  • First-party event records (page_events): kept for 18 months, then purged. Contains hashed IP, user agent, referrer, page path, event name, and event metadata — never the text you processed.
  • Tool usage records: kept for 18 months, then deleted. Never the text you processed; see Section 1.
  • Daily free-limit counters: 1 month, then deleted
  • Detector feedback reports, including any text you chose to share: 24 months, then deleted
  • Plausible Analytics: aggregated, no personal data retained
  • Google Analytics 4: collected only after you accept; kept for the retention period set on our Google Analytics property (2 months by default, 14 months at most), then deleted by Google
  • Ahrefs Web Analytics: aggregated, no personal data retained

15. Your Rights (GDPR)

If you are located in the European Economic Area (EEA), you have the right to:

  • Access your personal data
  • Rectify inaccurate personal data
  • Erase your personal data ("right to be forgotten")
  • Restrict processing of your data
  • Data portability — receive your data in a structured, machine-readable format
  • Object to processing based on legitimate interest
  • Withdraw consent at any time for consent-based processing

You can exercise most of these rights directly: delete your account from Dashboard settings, unsubscribe from emails, or delete your reviews. For other requests, chloe@codaone.ai. We respond within 30 days.

You also have the right to lodge a complaint with your local data protection authority.

16. Your Rights (CCPA — California Residents)

If you are a California resident, you have the right to:

  • Know what personal data we collect and how it is used
  • Request deletion of your personal data
  • Opt out of the sale of personal data — we do not sell personal data
  • Non-discrimination for exercising your rights

Contact chloe@codaone.ai to exercise these rights.

17. Children

The Service is not directed at children under 16. We do not knowingly collect personal data from children under 16. If you believe we have collected such data, please contact us and we will delete it promptly.

18. Data Breach Notification

In the event of a data breach that poses a risk to your rights and freedoms, we will notify the relevant supervisory authority within 72 hours and affected users without undue delay, in accordance with GDPR Article 33 and 34.

19. Changes to This Policy

We may update this policy from time to time. Changes are posted on this page, and the "Last updated" date at the top reflects the most recent revision.

20. Data Controller & Contact

The data controller is Coda Web3 Creative Ltd, a company registered in the United Kingdom, operating the Coda One service at codaone.ai.

For privacy-related inquiries: chloe@codaone.ai
For general inquiries: Contact form or chloe@codaone.ai