Last updated · 27 April 2026

Cookie Policy

This Cookie Policy explains the cookies and similar storage technologies Veri5 uses, why we use them, and how you can control them. This Policy supplements our Privacy Policy.

The short version. We use only a small number of cookies, all of them strictly necessary or functional. We don't use advertising, profiling, or cross-site tracking cookies. There is no consent banner because there is nothing in our use of cookies that legally requires opt-in consent.

1. What Cookies and Similar Technologies Are

A cookie is a small text file a website stores on your device. Local storage and session storage are browser features that work similarly but with different lifespans. We refer to all of these collectively as "storage" in this Policy.

Storage can be set by us (first-party) or by services we embed (third-party).

2. Storage We Use

Strictly necessary

These are required for the Service to function. They do not require consent under UK PECR / UK GDPR because they are essential to deliver a service you have requested.

__session (Clerk)
Authentication session. Set by our auth provider Clerk when you sign in. First-party. Session cookie or short-lived persistent cookie. Without this you cannot stay signed in.
Other Clerk cookies (__client, __refresh, etc.)
Session refresh and CSRF protection. First-party. See Clerk's own privacy notice at clerk.com/legal/privacy.
Stripe payment cookies
Set on Stripe's payment pages and embedded checkout to support fraud prevention and the secure submission of payment details. Third-party. See stripe.com/cookie-settings.

Functional

These remember preferences you've set. We don't consider them strictly necessary, but disabling them won't break the Service — only personalisation.

localStorage: veri5-theme
Stores your light/dark theme preference so the page doesn't flash the wrong theme on load. First-party. Persistent.
sessionStorage: veri5_signup_type
Remembers which account type (User or Business) you picked at the start of signup, so a Clerk OAuth round-trip can't lose it. First-party. Cleared when you close the tab.
sessionStorage: veri5_signup_interval
Remembers whether you chose monthly or annual billing on the signup picker. First-party. Cleared when you close the tab.
sessionStorage: veri5_referral_code
If you arrived via a Business's referral link (?ref=...), this stores the code so it can be applied at signup. First-party. Cleared when you close the tab.

3. What We Do NOT Use

We do not set or rely on:

  • Advertising or marketing cookies;
  • Cross-site tracking pixels;
  • Third-party analytics that profile individual visitors (e.g. Google Analytics with default settings);
  • Social-network "like" / "share" widgets that beacon to third parties.

4. Managing Cookies

You can control or block cookies through your browser settings. Helpful pages from major browser vendors:

Disabling strictly-necessary cookies will prevent you from signing in or completing payment. Disabling functional storage will reset your theme and signup choices on each visit but won't otherwise impact the Service.

5. Changes to This Policy

If we add, remove, or substantially change the storage we use, we'll update this Policy and the "Last updated" date above. For material changes affecting your rights we'll also notify you in-app.

6. Contact

Questions about this Cookie Policy? Email privacy@veri5.app.