COOKIE POLICY
1. THE SHORT VERSION
Until you answer the question in the panel at the foot of the page, Accolade sets no cookies at all on its public pages. Browsing this site — the homepage, pricing, the legal documents, the comparison pages — stores nothing on your device. One cookie is set when you log in, because a login cannot work without one, and one small cookie is set when you answer the question, to remember what you answered.
We do not currently run analytics, advertising or social-media tracking on this website. The measurement tag is installed but inert: its identifier is still a placeholder, so no measurement container loads and no analytics cookie is created for anyone. The consent machinery was built and shipped before that identifier is filled in, which is the only order that works — on the day it is switched on, the answer you gave here is already the thing that decides whether anything loads.
You can change your answer at any time, in either direction, using Cookie settings in the footer of any page or the button in §5.
2. WHAT ARE COOKIES
Cookies are small text files stored on your device when you visit a website. They can keep you logged in, remember preferences, or track you across pages and sites. Only the first of those applies here.
3. COOKIES WE SET
Strictly necessary
These are the only cookies Accolade sets. They are exempt from consent under PECR reg.6(4) because the service you asked for cannot be provided without them, and they cannot be turned off from within the platform.
| Cookie | When it is set | Purpose | Duration |
|---|---|---|---|
| session | When you log in. Not set while you are only browsing the public site. | Keeps you signed in and holds your session state. It is signed by the server so it cannot be edited in your browser. | Until you close your browser, or until you log out |
| accolade_cookie_choice | Only when you answer the cookie question — either way. Declining sets it just as accepting does. | Records your answer so we do not ask again on every page, and so that a decline is honoured on your next visit rather than forgotten. It holds one word, allow or deny. Recording your preference is itself exempt from consent, because the alternative is asking again every time you load a page. |
12 months, then we ask again |
Cookies we do not set
Listed because their absence is the point, and because a previous version of this page said otherwise:
| Category | Status today | What would change it |
|---|---|---|
| Analytics | None set today, whatever you answer. The tag identifier is still a placeholder, so no measurement container is loaded on any page and there is nothing for it to store. | Switching the identifier on. From that moment, accepting will let Google Analytics set its own first-party cookies — the names and durations will be published in the table above on the same day, and declining will still set nothing. |
| Advertising and social | None set. No advertising cookies, no tracking pixels, no social-media embeds. Our tag configuration denies ad storage, ad user data and ad personalisation outright, and nothing on this site can grant them. | We have no plans to add these. |
| Preference | One, and only the one in the table above, which remembers your cookie answer. Nothing else on the public site remembers a choice between visits. | Nothing planned. |
4. THIRD-PARTY COOKIES
We use Stripe for payment processing. Stripe may set its own cookies when you reach a checkout page, for fraud prevention and to make the payment work. We do not control those cookies; see Stripe's privacy policy.
Our pages load web fonts from Google Fonts. Google Fonts serves font files and does not set cookies for that request, but it does receive your IP address as part of the request, as any host you fetch a file from does.
We embed no advertising cookies and no social-media tracking pixels.
5. MANAGING COOKIES
Your answer is stored on this device and you can change it here at any time, in either direction. Withdrawing takes exactly the same two clicks as giving it did.
The same control is in the footer of every page on this site, labelled Cookie settings.
With scripting turned off, no optional cookie can be set at all, because the tag that would set one cannot run either. In that case the browser controls below are the whole answer.
You can also control cookies through your browser. Blocking the strictly necessary cookie above will stop you being able to log in.
- Chrome: Settings → Privacy and security → Third-party cookies
- Firefox: Settings → Privacy & Security → Cookies and Site Data
- Safari: Settings → Privacy → Manage Website Data
- Edge: Settings → Cookies and site permissions
6. WHEN THIS PAGE WILL NEED UPDATING
This policy describes the site as it is built today, and one thing about it is deliberately half-finished.
The analytics tag is installed but inert: the container identifier is still a placeholder, so nothing loads and nothing is stored, whatever you answer. The machinery that asks you, records your answer and refuses to load anything without a yes is finished and running — that part shipped first, on purpose. Under PECR reg.6 analytics cookies require your consent before they are set, not after, and the only way to guarantee that is for the question to already be in place on the day the identifier is filled in.
What still has to happen on that day, and not the day after: the analytics cookie names and durations go into the table in §3. Until then, the honest statement is the one in §1 — no analytics cookie is created for anybody, including the people who accepted.
7. UPDATES
We may update this Cookie Policy as our use of cookies changes. The "last updated" date at the top always reflects the current version.
8. CONTACT
Questions about cookies? Email our Data Protection Lead at privacy@accolade.live.