Skip to content
Value Accelerator Back to the homepage

Cookie policy

Last updated: 30 October 2026

This page lists everything this website stores in your browser: what sets it, what it is for, what it holds, and how long it lasts. Every duration below was measured in a browser on this site rather than copied from a vendor's documentation. It is a companion to our privacy policy, which describes the processing behind these items and the legal basis for each.

Two things worth knowing first

Every item below is stored under our own domain, the analytics ones included. PostHog's script runs inside your browser and keeps its identifiers here, not on a domain of its own, so there is no third-party cookie on this site at all. What reaches PostHog reaches it as network requests instead — which is why your consent, rather than where a cookie sits, is what governs them.

Nothing in the section "Only after you agree" is written until you choose "Accept". Until you choose, and permanently if you choose "Reject", those items are never created. You can change your answer whenever you like with the "Cookie preferences" button in the footer of any page.

Set before you choose

One thing is stored without asking you first. It holds a random identifier but nothing about who you are, and it is not used to measure or profile anything.

va-consent-v1 — local storage, not a cookie

Set by: us, at the moment you answer the consent banner.

Purpose: to remember your answer so we stop asking, to keep the analytics tools switched off for as long as that answer is "Reject", and to file each answer you give under the same identifier in our record of consent.

Contains: your choice, the time you made it and a randomly generated identifier. When you answer, those three are sent to us once, with the banner's text and the page you were on, and kept for two years as the record of your consent — our privacy policy describes that record in full.

Expires: local storage carries no expiry date of its own, so this entry stays until you change your choice or clear this site's browser storage.

Only after you agree

These appear the moment you press "Accept", or tick "Analytics & session recording" under "Customize" and save — and not one second earlier. All of them serve analytics: which pages get read, and where people get stuck. None is used for advertising.

ph_ plus our project's key, plus _posthog

Set by: PostHog, our analytics and session-recording tool. Its full name carries the public key of the PostHog project the site reports to, which differs between our live site and our testing one. It is written twice, as a cookie and in local storage, under the same name.

Purpose: to tell one browser from another, so somebody returning is not counted as somebody new, and to tell one visit from the next.

Contains: a randomly generated identifier, the current session's identifier and start time, and the page and referrer you first arrived from.

Expires: the cookie after 365 days; the local-storage copy has no expiry date of its own and stays until you withdraw your consent or clear this site's browser storage.

ph_ items in session storage

Set by: PostHog. There are up to four, each named ph_, our project's key, and one of _posthog, _primary_window_exists, _session_registered_properties or _window_id.

Purpose: to keep the state of this browser tab, so that a recording of your visit is not mixed up with another tab's.

Contains: a randomly generated window identifier and technical flags.

Expires: when you close the tab.

__ph_opt_in_out_ plus our project's key

Set by: PostHog, in local storage, only if you withdraw your consent or give it again while a page is open.

Purpose: to keep PostHog silent for the rest of that page after you withdraw.

Contains: a single flag.

Expires: a withdrawal's flag is removed by the next page you open here. A flag written because you agreed again stays until you withdraw or clear this site's browser storage.

Services you can reach from here, which set their own

One service is not loaded with our pages but can be reached from them. Once you use it, it runs in its own context and sets its own cookies there, so those are governed by its policy rather than this one.

Calendly — the booking calendar. Nothing from Calendly loads with the page or when you scroll to the calendar, only when you select "Show the calendar" or a booking button. From then on it runs in a frame from calendly.com, and your choice in our cookie banner does not reach it. When we measured it on 30 October 2026, that frame set cookies under calendly.com and m.stripe.com, and contacted services including Google (Analytics, Tag Manager, reCAPTCHA), Meta, Stripe, Segment, Sprig, Survicate and Airbrake. Calendly decides that list, and it can change. See Calendly's privacy notice.

Changing your mind, or blocking all of it

The "Cookie preferences" button in the footer of every page reopens the banner, and withdrawing consent there stops the analytics tools immediately and for good, until you say otherwise.

Independently of anything we offer, your browser can block or delete cookies for this site, and clearing its storage for us removes every item on this page — including the record of your own consent, which is why the banner will greet you again afterwards.

Blocking the two items under "Set before you choose" costs you nothing important: the site works without them, it will simply ask about cookies again on your next visit and may show you the other version of the homepage.

Changes to this page

If we add or drop a tool, this list changes with it, and so does the date at the top of it.

We use analytics and session-replay cookies from PostHog to understand how visitors use this site and to improve it. This page is the full list; you can change your choice any time from the footer.