Legal — Cookie policy
Last updated — 9 October 2026
This page explains the application’s use of browser storage, Cloudflare’s security cookies and the providers involved in serving this website.
01
No analytics or advertising cookies
The Specus application sets no analytics, advertising or tracking cookies. It does not write contact information or identifiers to local storage or session storage.
- No embedded visitor analytics, session recording or heatmaps
- No tracking — no pixels, no tags, no cross-site identifiers
- No advertising — no ad network, no retargeting, no audience lists
- No social embeds — no third-party players, widgets or share buttons
Cloudflare still processes technical request data and produces operational traffic statistics to deliver and protect the site. Those activities, and email processing, are described in the privacy policy. The absence of tracking cookies does not mean that no personal data is processed.
02
Language preference and security cookies
On an unlocalised URL, the site uses the browser’s Accept-Language header to choose a supported language, with English as the fallback. An explicit language URL is always respected. When you select and apply a language in the footer, the site stores that language code in a first-party session cookie named specus_language. It contains no visitor identifier, is not used for tracking and is not set by automatic detection. You can change it through the same selector or delete it in your browser. The cookie has no persistent expiry; browsers may restore session cookies when restoring a browsing session.
The public site is served through Cloudflare. Its security protections may challenge a request before allowing access. If a challenge is presented and passed, Cloudflare may set strictly necessary security cookies; these are not advertising or visitor-tracking cookies.
- cf_clearance — Cloudflare
- Stores proof that a security challenge was passed, so the visitor does not have to repeat it on each request. Challenge Passage is configured to 30 minutes, subject to Cloudflare’s documented technical allowances when validating clearance.
- cf_chl_rc_i, cf_chl_rc_ni, cf_chl_rc_m — Cloudflare
- Challenge-platform diagnostic cookies that Cloudflare may use to identify problems when running a security challenge. They serve the challenge’s technical operation; Cloudflare documents them in its security-cookie reference.
Bot Fight Mode is currently disabled for this domain. We therefore do not describe its __cf_bm cookie as an active feature of this site. Cloudflare cookie data may be processed in the United States; the transfer safeguards are described in the privacy policy.
Turnstile pre-clearance is disabled: the contact-form widget does not issue a cf_clearance cookie.
03
Assets and external services
Images and typefaces are served from this site’s own domain. The application does not load Google Fonts, analytics, advertising or social embeds.
The contact form loads Turnstile’s script and verification frame from challenges.cloudflare.com when you interact with it. This is an external security service.
Requests to our domain pass through Cloudflare and reach the Hetzner hosting server where needed. Cloudflare may serve its own security-challenge resources when protecting a request. Submitting the contact form sends the message through Cloudflare Email Service to the Outlook.com mailbox.
04
Why you see no consent banner
Only storage strictly necessary to provide the service you request is used. Optional analytics, advertising and profiling storage are not enabled, so there is no optional cookie choice for a consent banner to present. If optional tracking is added, any required consent will be requested before its cookies or similar storage are used.
You can delete or block cookies through your browser settings. Blocking a necessary Cloudflare security cookie may cause repeated challenges or prevent access to a protected request. Your browser may also cache page assets under its normal cache settings; that is separate from an application tracking identifier.
05
How changes are notified
This page and its date are updated before a change to browser storage, security-cookie settings or external page services reaches production. Any corresponding change to personal-data processing is also reflected in the privacy policy.
Questions about cookies go to hello@specus.ai. See also the privacy policy and the terms of service.