[Policies and legal information](https://clarveni.com/policies)

 Cookie policy 
===============

Cookies, browser storage, analytics and related technologies used by Clarveni.

**Effective: 26 October 2026. Version 5.**

Contractual terms apply in accordance with the relevant agreement's acceptance and change-notice provisions.

 At a glance 
-------------

Session and security technologies support forms and sign-in. Optional analytics and preferences need a separate assessment and any required consent or objection control. A “cookieless” label alone does not settle that question.

Browser settings let you inspect and clear site data. They supplement any consent or objection choice we are required to provide on the site.

This summary helps you navigate the document; read the full provisions for their scope and exceptions.

On this page

1. [Cookies and similar technologies](#cookies-and-similar-technologies)
2. [Application cookies and browser storage](#application-cookies-and-browser-storage)
3. [Security, payment and external services](#security-payment-and-external-services)
4. [Analytics and your choices](#analytics-and-your-choices)
5. [Emails and brief-page activity](#emails-and-brief-page-activity)
6. [Browser controls and changes](#browser-controls-and-changes)
7. [Visitors outside the UK](#regional-cookies)

 Legal operator 
----------------

Clarveni is the trading name of Clarveni Ltd, a company registered in England and Wales, whose registered office is at 71-75 Shelton Street, Covent Garden, London, United Kingdom, WC2H 9JQ.

References to “Clarveni”, “we”, “us” and “our” mean Clarveni Ltd.

 1. Cookies and similar technologies 
-------------------------------------

Cookies are small records stored by a browser. This policy also covers local storage and other technologies that store information on, or access information from, a device. Scripts, pixels and fingerprinting may be covered by the same PECR rules even when they do not set a conventional cookie. Personal information associated with these activities is explained in the [privacy notice](https://clarveni.com/privacy).

The inventory below explains the application's cookies and browser storage, including default lifetimes. Names, expiry and which technologies you encounter depend on the feature you use and its configuration. Cookies on external services are controlled by those services.

 2. Application cookies and browser storage 
--------------------------------------------

  **Signup email handoff: clarveni.start-email (session storage)** When you submit a public email-capture form, first-party session storage temporarily keeps the work email you enter so the next signup step can fill it without putting it in the page URL. The application removes the stored value when that step reads it. If you do not reach that step, it can remain for the browser tab's session; it has no separate timed expiry. Blocking storage leaves the next email field empty so you can enter it there. This handoff supports the signup journey you requested and is not an advertising identifier. **Session cookie: configurable name, normally Clarveni's name followed by “-session”** First-party cookie used on session-enabled forms and authenticated areas to maintain the requested session and access state. It contains a session identifier rather than the full account record when the database session driver is used. The configuration default is 120 minutes, refreshed during use; a browser-close expiry can be configured. Your browser's site-data settings show the issued name, domain and expiry. Ordinary anonymous reads of guest-cached marketing pages are designed to set no application session cookie. **XSRF-TOKEN** First-party cookie, where issued, which enables the browser to supply a request-forgery protection token with form or interactive requests. It supports secure use of the requested service. Its expiry follows the configured session lifetime, normally 120 minutes, unless deployment settings change it. **remember\_\* cookie** First-party persistent authentication cookie where a sign-in flow offers and the user selects continued sign-in. The name includes the authentication guard and a framework identifier. The framework default is 576,000 minutes (400 days), subject to the configured lifetime. It stores authentication-related identifiers and a token; signing out or invalidating the token can end its usefulness before expiry. Your browser shows the expiry of an issued cookie. **developer\_grant** First-party cookie for a specifically authorised restricted-access grant, rather than ordinary public browsing. It contains a hash reference and an expiry, with a configured default of 480 minutes (eight hours). It is used to verify that grant and is not an advertising identifier. **Account interface preferences: theme, isOpen, isOpenDesktop and collapsedGroups** The account interface uses local storage for appearance and sidebar preferences where those features run. These records are scoped to the site's browser origin and can persist until cleared; local storage has no automatic cookie expiry. The keys present depend on the interface features you use. You can inspect and remove them through your browser's site-data settings. 

Session and request-security cookies support the service you request. The strictly necessary exception applies only where its legal conditions are met; secondary analytics or marketing use requires a separate basis. Persistent sign-in and appearance preferences need a proportionate duration and any legally required user choice.

 3. Security, payment and external services 
--------------------------------------------

Cloudflare Turnstile can load a security script and challenge frame on forms when enabled, processing relevant device and network information to assess abuse. Cloudflare's edge security can also use cookies depending on the selected features. For example, `cf_clearance` can arise from a challenge or pre-clearance configuration and `__cf_bm` from enabled bot-management features. These are conditional supplier examples, not a statement that every Clarveni visitor receives them.

For the purposes and lifetimes of Cloudflare's conditional security cookies, see [Cloudflare's cookie information](https://developers.cloudflare.com/fundamentals/reference/policies-compliances/cloudflare-cookies/) and [Turnstile pre-clearance documentation](https://developers.cloudflare.com/turnstile/additional-configuration/hostname-management/pre-clearance/). You can also ask us about a technology encountered on our site.

Mollie's hosted checkout may use its own payment and fraud-prevention technologies when you choose to pay. Its notice and controls apply on that service; opening Clarveni's public website does not itself mean a Mollie checkout cookie is issued. Company logos can load from Logo.dev, which receives the browser request. An external image request may disclose information even if no cookie is set.

 4. Analytics and your choices 
-------------------------------

The marketing integration supports Plausible or Fathom and is disabled when valid provider configuration is absent. When enabled, it can measure public-page visits and conversion events, sending page and referral information to the selected provider. The integration excludes private routes and URLs bearing credentials such as signatures, tokens or email parameters. This reduces exposure without proving that every URL or referrer is free of personal information.

A supplier describing analytics as “cookieless” does not by itself remove PECR duties. Optional device storage or access needs consent unless a specific exception applies. The statistical-purposes exception has conditions, including limited statistical use to improve the service, appropriate protection of information, clear information and a simple, free means of objecting. Advertising, cross-service profiling or other secondary purposes require separate consideration.

The site does not currently provide an analytics consent or objection control. Optional analytics requiring such a control must not be activated without it. Where consent is required, the technology must wait for an affirmative choice; rejecting or withdrawing must be straightforward. Where an exception requires a means of objecting, a general enquiry form is not an adequate substitute for that browser choice.

 5. Emails and brief-page activity 
-----------------------------------

The service records the first qualifying visit to a signed brief page. This is a server-side delivery record and differs from an invisible email-open pixel; an automated scanner or forwarded link can trigger it. Credential-bearing mail is designed to disable provider tracking. This is not a statement that every message type and supplier feature is tracking-free; contact us about a specific message if you need more information.

Any future email pixels, link-tracking technology or embedded services need a separate assessment, clear information and consent where applicable. Unsubscribing from a brief stops that recipient's delivery; it does not itself clear browser storage or cancel an account.

 6. Browser controls and changes 
---------------------------------

You can inspect, remove or block cookies and site storage through your browser's privacy or site-data settings. Clearing persistent sign-in or interface preferences can sign you out or reset the interface. Blocking necessary session or security cookies can prevent signing in or submitting a form. Browser controls supplement any consent or objection mechanism we are required to provide.

We review the inventory when features or suppliers change, identify the policy version and obtain a new choice where the law requires it. Contact us if you find an unexplained cookie or cannot exercise a required choice.

 7. Visitors outside the UK 
----------------------------

The UK PECR rules above do not replace applicable local requirements. Where required, Canadian consent, US state sale/sharing or targeted-advertising opt-outs, and other regional choices must address the actual technology and disclosures. Global Privacy Control is a preference signal distinct from blocking all cookies; it must be honoured where applicable law requires it. The site does not currently provide a Global Privacy Control handler or regional preference centre. These limitations do not waive your statutory rights; use the [regional privacy-request route](https://clarveni.com/privacy-requests#regional-requests) to contact us.

 Contact 
---------

Use our [contact form](https://clarveni.com/contact) for questions, privacy requests or complaints. State which policy your message concerns.

You can also email support@clarveni.com. Mark privacy correspondence “Data protection”.

[Back to top](#policy-top) · Use your browser's Print or Save as PDF option to keep a copy.

- [Privacy notice](https://clarveni.com/privacy)
- [Cookie policy](https://clarveni.com/cookies)
- [Website terms](https://clarveni.com/terms)
- [Subscription terms](https://clarveni.com/subscription-terms)
- [Acceptable-use policy](https://clarveni.com/acceptable-use)
- [Data-processing agreement](https://clarveni.com/data-processing-agreement)
- [Privacy requests and complaints](https://clarveni.com/privacy-requests)
