Cookie Policy
Last updated: 26 April 2026
We use a small number of cookies and browser storage items to make KitchenCoCo work and to understand how it's used. This page lists exactly what they are and what they do.
Strictly necessary
These keep you signed in and remember basic preferences. They're always on — without them the site wouldn't function.
| Name | Purpose | Duration |
|---|---|---|
| payload-token | Keeps you signed in (HTTP-only cookie set when you log in). | 30 days for consumers, 7 days for company admins |
| kc-cookie-consent-v1 | Remembers whether you accepted analytics cookies, so we don't ask again. | Until you clear it (localStorage) |
| Audio player state | Persists the kitchen-blog audio player across page navigation. | Session only (sessionStorage) |
Analytics (optional)
Loaded only if you accept analytics in the cookie banner. We use Plausible, a cookieless EU-hosted analytics tool — even when enabled, it doesn't set tracking cookies and doesn't identify individual users.
| Name | Purpose | Duration |
|---|---|---|
| No cookies set | Plausible counts page views via aggregated, anonymised data only. | N/A |
Third-party services
Some pages embed content or scripts from other services that may set their own cookies when used:
- Stripe — only loaded on the company subscription checkout page when you click Upgrade. Stripe's own cookies handle fraud prevention and the checkout session.
- Google Fonts — fonts are loaded from Google's CDN. Google may record your IP address as part of standard CDN delivery; no cookies are set.
Managing your preferences
You can change your analytics preference at any time by clearing your kc-cookie-consent-v1 storage entry (use your browser's site-data settings) and reloading the page — the consent banner will reappear.
All modern browsers also let you block or delete cookies entirely. The strictly necessary cookies listed above are required to sign in, so blocking them will make the dashboard unusable.
More information
See our privacy policy for the full picture of what we collect and how it's used. Questions: [email protected].