Skip to content

Cookie Policy

Last updated: October 2026

This Cookie Policy explains how Coda One ("we", "us") uses cookies and similar technologies when you visit codaone.ai ("the Service"). We keep it simple because our cookie usage is minimal.

1. What Are Cookies?

Cookies are small text files stored on your device by your browser. They help websites remember information about your visit, like your login status and preferences.

2. Cookies We Use

Eight cookies can be set. Five are strictly necessary. The other three stay off until you accept:

Name Purpose Type Duration
codaone_session Keeps you logged in after authentication Essential (first-party) 30 days or until logout
oauth_state, oauth_return_to Sign in with Google: checks that the reply comes from the sign-in you started, and returns you to the page you were on Essential (first-party) 10 minutes
codaone_pending_totp Two-step sign-in: holds the first step while you enter your authenticator code Essential (first-party) 5 minutes
coda_consent Remembers whether you accepted or rejected optional cookies, and when you chose. A later visit does not restart that time Essential (first-party) Until 13 months after the choice
coda_aff_ctx Remembers how you got here — partner code, landing page, referring site, and any utm parameters on the link — so a partner is credited if you later subscribe Attribution (first-party) 30 days
_ga, _ga_P59Q97VD1N Google Analytics 4 — tells returning browsers apart so we can see which channels bring people here. Set only after you accept Analytics (third-party, Google) Up to 13 months

codaone_session and coda_aff_ctx are HttpOnly, Secure, and SameSite=Lax — they cannot be read by JavaScript and are only sent over HTTPS. coda_consent is written by the page so the server can honour the choice. It is not HttpOnly. It holds only the choice and the time it was made. The Google Analytics cookies are set by Google's script after you accept, and rejecting deletes _ga and _ga_* on this site.

Similar technologies. The site also keeps a few entries in your browser's localStorage (kept until you clear site data, unless a shorter time is given) and sessionStorage (removed when you close the tab). None of them is used for advertising.

Strictly necessary for the page or tool you are using:

  • consent_v1 (localStorage): the same choice as coda_consent, so the page can apply it before the next request. Expires with that choice.
  • codaone_client_v1 (localStorage): a random ID sent with each tool request so the free daily allowance is counted per browser rather than shared by everyone on the same network. It is not linked to your account or used for analytics. If you report a detector result, the report carries this ID.
  • coda_auth (sessionStorage): whether you are signed in and on which plan, for this tab.
  • codaone_checkout_intent (localStorage): the plan you clicked before signing in, so checkout can continue in this browser. Removed when used or after 30 minutes.
  • codaone_tracked_purchase_<invoice> (sessionStorage): that a purchase on the confirmation page has already been counted, so reloading it does not count it twice.

Saved on your device when you use a tool, so you can come back to your work. Not sent to us:

  • codaone_detector_tasks_v1, codaone_detector_tasks_migrated_v1 (localStorage): your recent detector checks, including the text, for up to 30 days. codaone_pdf_workflow_tasks_v1 does the same for PDF tasks.
  • codaone_detector_persona_v1 (localStorage): the role you picked on the detector page.
  • codaone_humanize_text (localStorage): text passed from the detector to the humanizer. Removed as soon as the humanizer opens it.
  • dt_uses, codaone_hz_history (sessionStorage): how many detector checks you have run in this tab, and this tab's humanizer results. An older dt_history entry, if present, is copied into your recent checks; clearing them removes it.
  • feedback_<page> (localStorage): that you already answered "Was this helpful?" on a page, so it is not asked again.

Only after you accept: coda_entry (sessionStorage) stores the landing path, an optional ref, and the referring host for this tab. Rejecting removes it. Closing the tab removes it.

coda_aff_ctx is set only after you accept optional cookies, and only if you arrived through a partner link (?aff=, ?via=, ?partner=) or with a utm_ campaign parameter. Until 27 August 2026 it was also written on anyone's first visit from any other website — a search result, a forum link — which cookied nearly every visitor for a feature none of them had used. That is no longer the case. It never contains your name, email, or anything you type into a tool.

3. Cookies We Do NOT Use

  • Advertising cookies — we do not serve ads or share data with ad networks, and we do not use the analytics cookies above for remarketing
  • Social media cookies — we do not embed social media trackers
  • Cross-site tracking — we do not follow you onto other websites

4. Bot Protection

We use Cloudflare Turnstile on forms to prevent 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.

5. Third-Party Services

These third parties load on our pages or receive a request from your browser:

  • Plausible Analytics — aggregate pageviews. No cookies, no personal data retained.
  • Ahrefs Web Analytics — SEO and Core Web Vitals signals. No cookies.
  • Google Analytics 4 — not requested from googletagmanager.com until you accept, and only when a measurement ID is set at build time. Until then it does not set _ga or _ga_*, and it does not send your IP address or the page URL to Google. With no measurement ID, the tag is not loaded.
  • Google Fonts — one webfont stylesheet is requested from fonts.googleapis.com. No cookies, but Google receives your IP address and user agent.
  • Cloudflare Turnstile — the bot check on our forms. No cookies (see Section 4).
  • Stripe — checkout happens on Stripe's own hosted page, so Stripe sets its cookies there rather than here. Nothing from Stripe loads on codaone.ai.

When you click outbound or affiliate links, the destination site may set its own cookies. These are governed by that site's cookie and privacy policies, not ours.

If you sign in with Google or Telegram, those providers may use their own cookies during the authentication flow. See their respective privacy policies for details.

6. Managing Cookies

Blocking codaone_session will prevent you from staying logged in. Blocking the Google Analytics cookies costs you nothing — every tool works without them. You can manage cookies through your browser settings:

  • Chrome: Settings → Privacy and Security → Cookies
  • Firefox: Settings → Privacy & Security → Cookies
  • Safari: Preferences → Privacy → Manage Website Data
  • Edge: Settings → Cookies and Site Permissions

You can also delete the codaone_session cookie at any time by logging out of your account. To change the optional cookies, use Cookie settings in the footer or the button on this page. To opt out of Google Analytics everywhere, Google publishes a browser opt-out add-on.

7. Cookie Consent

Strictly necessary cookies — our session cookie — do not require consent. Optional cookies do. Google Analytics cookies and coda_aff_ctx stay unset until you accept.

The choice is stored in this browser. Accept turns optional analytics and attribution cookies on. Reject leaves them off. You can change it later from Cookie settings in the footer or the button below. Closing the preferences panel without choosing is not treated as acceptance, and using the site is not treated as acceptance. We ask again after 13 months. The 13 months run from the original choice and are not restarted when you come back.

If Google Analytics is not enabled for the build, we do not ask you about it. The banner appears when Google Analytics is enabled, or when this visit would set the partner-attribution cookie. Rejecting stops us setting those cookies. Rejecting also deletes Google Analytics cookies (_ga, _ga_*) already stored for this site.

8. Changes to This Policy

If the cookies we use change, we update this page and the "Last updated" date at the top.

9. Contact

Questions about our cookie practices? Contact us at chloe@codaone.ai or use our contact form.

See also: Privacy Policy · Terms of Service