AtelierPlate Back to the studio

Legal · 03 of 04

Cookie policy

Four entries, one of them optional. The full list, with no dark patterns and no pre-ticked boxes.

Version 2.0 · in force from 18 August 2026

What we set

This site runs on flat files and one small script. Nothing loads before you choose, and there is no advertising technology anywhere on the domain. Two of the four entries below are not cookies at all: they are local storage keys, which never travel to a server.

The full list

NameTypePurposeLife
atelierplate.consentLocal storage, essentialRemembers whether you accepted analytics, so the notice does not reappear.Until you clear site data
ap_sessionCookie, essentialAnti-abuse token on the sign-up form. Contains a random string and nothing else.Session
atelierplate.prefsLocal storage, functionalKeeps your last plating style and palette filter so the page opens where you left it.90 days, then discarded on read
noneAnalytics, optionalOur analytics provider sets no cookie and no local storage key at all. Accepting simply allows the script to load.Not applicable

On analytics

We measure which recipes get read so we know what to shoot next. That is the whole purpose. Our analytics provider is Plausible, hosted in Estonia, which does not use a persistent identifier and reports only aggregates: page, referrer, country, device class. If you decline, the script is never requested, so nothing is loaded and nothing is blocked at your end.

Changing your choice

Clear site data for atelierplate.site in your browser settings, then reload any page and the notice will appear again. There is no separate preference centre because there are only two states, and hiding one of them behind five toggles would be theatre.

Third-party embeds

Recipe pages sometimes embed a technique clip. Those clips load from a privacy-enhanced player domain only after you press play, and the player sets its own cookies at that point, which we cannot see or read. Web fonts are served from Google Fonts. If you would rather they were not, block that domain and the site falls back to Didot and Helvetica, which is how the studio proofs the layout anyway.

Showcase build. The cookie names above match what this front end actually writes, with the exception of ap_session, which requires the production backend.