Legal
Cookie Policy
Last updated: September 1, 2026
This page lists everything AnswerPeek stores on your device, what each item is for, and how long it stays. It sits alongside our Privacy Policy, which covers what we do with the data once we have it.
“Cookies” is the word everyone uses, but the rules — and this page — cover any storage on your device, including local storage. That distinction matters here, because one of our tools uses local storage almost exclusively rather than cookies. It is treated exactly like a cookie: nothing in sections 3 to 5 below is written until you agree to that category.
1. Your choice, and where we ask for it
If you are visiting from the EEA, the UK or Switzerland, we show a banner before anything optional is written to your device. The banner offers three categories separately, because they are not the same question and you may reasonably answer them differently:
- Functional — the support chat inside the signed-in product.
- Analytics — how the site and the product get used, including heatmaps and session recording on our public marketing pages.
- Advertising — measuring our own ads on Facebook and Instagram.
Accepting analytics does not accept advertising, and nothing is pre-ticked. Strictly necessary storage, in section 2, is set whatever you choose. Elsewhere in the world no such law applies and we do not show the banner.
You can change your mind at any time using the Cookie settings link in the footer of any page. It brings the banner back and reloads the page, so that anything you have just withdrawn consent from stops running immediately rather than at your next click. Withdrawing also deletes what those tools had already written — the local-storage keys in section 4 and our own analytics cookies — because stopping a script while leaving its identifier on your device would be a withdrawal in name only. A cookie set by another company on its own domain is not ours to delete; the reload is what stops it being refreshed, and your browser can remove it outright (section 7).
2. Strictly necessary
These are set whatever you choose, because the site cannot do what you asked without them. Two of them exist to run the cookie banner itself.
| Name | Set by | What it does | Expires |
|---|---|---|---|
ap_consent | AnswerPeek | Remembers your answer to the cookie banner, so you are asked once rather than on every page. Also mirrored into local storage. | 182 days |
ap_region | AnswerPeek | Records whether your IP address is in a region where consent is legally required, so we know whether to show the banner at all. | 30 days |
sb-…-auth-token | Supabase | Keeps you signed in and is what proves a request is yours. Split across two numbered cookies when the session is large. Only set once you have an account. | 400 days |
3. Functional
One tool, one purpose: the support chat. It is offered as its own category because it is neither measurement nor advertising — it exists to answer you — but it does write to your device and does share your name and email with a third party, so it is still your choice.
| Name | Set by | What it does | Expires |
|---|---|---|---|
crisp-client/* | Crisp | Runs the support chat inside the signed-in app, and keeps your conversation open across page loads so you are not made to repeat yourself. Never loaded on the public site — only where you are signed in and support is part of what you are paying for. | Up to 6 months |
4. Analytics
None of these are written in the EEA, the UK or Switzerland until you accept analytics. They are what tell us which pages are worth keeping and where people give up.
| Name | Set by | What it does | Expires |
|---|---|---|---|
_ga | Google Analytics | Distinguishes one visitor from another so a return visit is not counted as a new person. | 400 days |
_ga_G522GTBNCP | Google Analytics | Holds the state of your current session for our specific analytics property. | 400 days |
ph_…_posthog | PostHog | Our main product analytics: which features get used, and where a flow is abandoned. The middle of the name is our project key. | 365 days |
plerdy_*, _suid, session_plerdy_v, id_page:::*, ip, country_code | Plerdy | Heatmaps and session recordings of our public marketing pages. Stored in local storage rather than cookies, which is why the names look unusual. Never loaded on the signed-in product, the sign-in pages, or white-label client reports. | Until you clear site data |
The Plerdy row is the one worth reading twice. It is the most invasive tool on the site — it records how a page was used, not just that it was visited — and it stores a value derived from your IP address on your own device. It runs only on our public marketing pages, only after you have agreed, and never anywhere your account data or a password field is on screen.
5. Advertising
Written only if you accept advertising, which is a separate answer from analytics. There is no cookieless version of the Meta Pixel — it exists to build an ad audience — so declining means it does not load at all.
| Name | Set by | What it does | Expires |
|---|---|---|---|
_fbp | Meta | Lets us measure whether our Facebook and Instagram ads led to sign-ups, and build audiences for them. | 90 days |
_fbc | Meta | The same, for a specific ad click — set only if you arrive here from one of our ads. | 90 days |
6. What happens if you decline
Choosing “Essential only”, or simply not answering, is a real answer and not a degraded one:
- Nothing from sections 3, 4 or 5 is written to your device.
- Crisp, Plerdy and the Meta Pixel do not load at all — none of them has a version that works without storage.
- Google Analytics still runs, with every storage type denied through Google Consent Mode. PostHog runs in its cookieless mode. Both add your visit to a total; neither can tell that the total includes you, or link this page to the next one you open.
- Everything in section 2 still works, so you stay signed in and are not asked about cookies again.
- Accepting one category and refusing another is a normal answer, not an all-or-nothing choice: taking analytics while refusing advertising leaves the Meta Pixel unloaded and everything in section 4 running.
Two events are sent from our servers rather than your browser and so happen either way — a finished free check, and a report you asked us to email. Neither carries an identifier when you have not consented. This is described in full in our Privacy Policy.
7. Controlling storage in your browser
Your browser can block or delete all of this independently of our banner, and its decision wins over ours. Every major browser offers this under Settings → Privacy, usually as “Cookies and site data”.
- Clearing site data for answerpeek.com removes everything on this page, including the local-storage keys that withdrawing consent leaves behind, and including your consent answer — so the banner will ask again.
- Blocking cookies entirely will sign you out and keep you signed out, because the session cookie in section 2 is how we recognise you.
- Browser-level “Do Not Track” and Global Privacy Control signals are not a substitute for the banner, which is why we ask you directly.
8. Changes, and questions
When we add or remove a tool, this table changes with it, and the “Last updated” date above moves. If a new tool needs consent, you will be asked again rather than opted in by default. Questions go to support@answerpeek.com.
A note on accuracy
The expiry times above were measured on the live site rather than copied from each vendor’s documentation. Where they differ from a number you have seen elsewhere — Google, for instance, describes _ga as a two-year cookie — the figure here is the one your browser will actually enforce. The single exception is crisp-client/*, which only ever appears for signed-in customers; that duration is the one Crisp documents.