TraceSpec Cookie Policy
Effective date: 29 August 2026 Last updated: 31 August 2026
This Cookie Policy explains how Elyven Ltd, trading as TraceSpec (“TraceSpec”, “we”, “us”, or “our”), uses cookies and similar technologies on our website and platform.
It should be read alongside our Privacy Policy.
1. What are cookies?
Cookies are small text files stored on your device when you visit a website. Similar technologies include local storage and other browser storage technologies that store or access information on your device.
Cookies and similar technologies can help websites work properly, keep accounts secure, remember preferences and support requested services such as authentication and payment.
2. How TraceSpec uses cookies and similar technologies
At launch, we use cookies and similar technologies primarily:
- to operate our website and platform;
- to enable account login, authentication, session management and security through Clerk;
- to remember cookie preferences where a preference needs to be stored;
- to process subscriptions and payments through Stripe-hosted Checkout; and
- to support the security and delivery of those services.
TraceSpec does not currently use analytics, advertising, remarketing, session-recording or behavioural-marketing technologies on the TraceSpec website or application.
If we introduce non-essential analytics, performance or marketing technologies in future, we will update this policy and, where required, ask for consent before those technologies are enabled.
3. Types of cookies and similar technologies we use
3.1 Strictly necessary technologies
Strictly necessary technologies are required for TraceSpec or a service you request to operate securely and correctly. They may be used for authentication, account sessions, security, bot/fraud prevention, cookie-preference storage and subscription checkout.
These technologies are not optional where they are necessary to provide the requested service. You may be able to block or delete them using your browser settings, but parts of TraceSpec may then stop working correctly.
3.2 Analytics and performance technologies
TraceSpec does not currently enable Google Analytics, Vercel Web Analytics or another optional analytics provider at launch.
If optional analytics or performance technologies are introduced in future, we will update this policy and apply the appropriate consent controls before they are enabled where required by law.
3.3 Functional technologies
Some technologies may remember choices or configuration needed to provide a requested feature. Where a technology is necessary for the requested service, we treat it as strictly necessary. Any future optional functional technology will be assessed before it is enabled.
3.4 Marketing technologies
TraceSpec does not currently use advertising pixels, remarketing technologies or behavioural-marketing cookies at launch.
If we introduce them in future, we will update this policy and request consent where required before they are enabled.
4. Current cookie and browser-storage table
The table below reflects our production browser observations on 31 August 2026, together with the implemented TraceSpec consent-preference configuration.
The table distinguishes between technologies set on TraceSpec-controlled domains and payment/security technologies encountered on Stripe-hosted Checkout after a user chooses to start a subscription.
| Cookie / technology | Provider | Where used | Purpose | Type | Duration / persistence |
|---|---|---|---|---|---|
__client_uat and related Clerk client-state variants | Clerk | .trace-spec.com | Supports Clerk authentication/client state and session freshness | Strictly necessary | Approximately 7 days in the production scan |
__client | Clerk | .clerk.trace-spec.com | Supports Clerk client and authentication state | Strictly necessary | Approximately 7 days in the production scan |
__cf_bm | Cloudflare, used in connection with Clerk infrastructure | .clerk.trace-spec.com | Bot-management and security protection | Strictly necessary | Approximately 30 minutes in the production scan |
_cfuvid | Cloudflare, used in connection with Clerk infrastructure | .clerk.trace-spec.com | Security and request/client distinction | Strictly necessary | Session in the production scan |
__clerk_environment | Clerk | Local Storage on www.trace-spec.com | Stores Clerk frontend environment/authentication configuration used by the sign-in experience | Strictly necessary | Persistent browser storage until cleared or updated |
tracespec_cookie_consent | TraceSpec | TraceSpec website/application origin, when a preference is stored | Stores the versioned cookie-preference state and choice timestamp | Strictly necessary preference storage | 180 days |
| Stripe-hosted Checkout security and payment technologies | Stripe | Stripe-controlled Checkout domains after a user chooses to start a subscription | Supports hosted payment processing, checkout security, fraud/bot prevention and related payment functionality | Strictly necessary for requested checkout/payment functionality | Varies by Stripe technology |
No TraceSpec application Session Storage was observed during the clean unauthenticated/sign-in scan.
No optional analytics, advertising, remarketing, heatmap, session-replay or behavioural-marketing storage was observed on the TraceSpec origin during the scan.
The exact cookies or storage technologies used by third-party providers can change as those providers update their services or security systems. We will keep this table under review and update it where material changes occur.
5. Consent and cookie settings
At launch, TraceSpec has no active optional analytics or marketing provider. Accordingly, a first-time visitor is not required to make an optional cookie choice simply to use the public website.
Cookie Settings remain available so you can review the current position.
If we introduce a non-essential technology in future, we will update our consent configuration so that the relevant technology is not enabled before the required choice has been made.
Where consent is used, you may withdraw or change that consent through the available cookie settings controls. Withdrawing consent does not affect the lawfulness of processing carried out before withdrawal.
6. Managing cookies in your browser
Most browsers allow you to block, delete or manage cookies and browser storage through browser settings.
If you block all cookies or browser storage, TraceSpec may not work correctly, particularly account login, authentication, security and subscription functionality.
7. Third-party services
Some strictly necessary cookies and similar technologies are operated by third-party providers that help us deliver TraceSpec.
These currently include:
- Clerk, which provides authentication, account login and session-management functionality;
- Cloudflare infrastructure used in connection with Clerk, which may provide security and bot-management functionality; and
- Stripe, which provides our hosted subscription Checkout and payment functionality.
TraceSpec is hosted using Vercel infrastructure. Vercel Web Analytics and Speed Insights are not enabled as optional browser analytics technologies at launch.
Our backend database services are provided through Supabase, but the launch architecture does not use Supabase browser authentication or a Supabase browser client that sets customer-facing Supabase authentication cookies on the TraceSpec website.
Third-party providers may process information under their own privacy and cookie policies as well as under our contractual arrangements with them.
8. Changes to this Cookie Policy
We may update this Cookie Policy from time to time, including when we add or remove providers, cookies, browser-storage technologies or product features.
The updated version will be posted on our website with a revised “last updated” date.
We also re-review the cookie/storage inventory after material changes to authentication, payments, analytics, marketing or other browser technologies.
9. Contact
For cookie or privacy questions, contact:
TraceSpec / Elyven Ltd Email: privacy@trace-spec.com