Cookies and browser storage

1. First-party browser storage

The website code does not set first-party cookies or use localStorage or sessionStorage for preferences, visitor analytics, or advertising. Language is selected through the page URL. Form submission identifiers and challenge tokens are held temporarily in the page while the form is used, rather than saved as a browser preference.

2. Turnstile form security

Cloudflare Turnstile processes browser and connection signals to distinguish visitors from automated abuse. A successful challenge normally produces a short-lived, single-use token that our server validates before accepting a form. This token is not an advertising identifier. Turnstile has its own privacy practices, explained in the linked Privacy Addendum.

The third-party widget runs in a Cloudflare frame at challenges.cloudflare.com and can create its own localStorage, including an entry named cf.turnstile.u. This differs from our website’s preference or analytics storage and from the form token. Cloudflare controls the entry’s behavior and retention, so we do not state a fixed expiry. Browser storage settings and clearing Cloudflare site data can remove or affect it.

3. Cloudflare security cookies

Cloudflare security services may use cookies depending on their configuration. Optional Turnstile pre-clearance can set a cf_clearance cookie, whose duration follows Cloudflare’s challenge settings. A security cookie is distinct from the form token and the widget’s localStorage. The linked provider documentation explains these features; this notice does not assert that a particular optional setting is enabled or that every visit is cookie-free.

4. Choices and future optional technologies

You can inspect or clear cookies and browser storage in your browser settings. Blocking necessary security features can prevent a form from being accepted. The current website code includes no optional analytics or advertising storage. If a nonessential technology is introduced, we must explain its provider, purpose, and duration and obtain any required consent before using it, with a way to withdraw that consent. This notice alone does not provide consent.

5. Privacy signals and questions

The website code has no specific response to Do Not Track or Global Privacy Control signals. Those signals do not switch off necessary form security. For information or a privacy request, email privacy@coxencode.com. See the website privacy notice for data use, retention, and rights.