Cookies
The three cookies
Each line names the cookie, what it does, when it’s set, when it expires, and the one-line argument for why it’s necessary.
| Cookie | Purpose | Lifespan |
|---|---|---|
md_locale |
Remembers whether you chose English or Spanish so your language preference persists as you click around. Set when you switch via the language toggle in the nav. | 1 year |
lang_hint_dismissed |
Remembers that you closed the “¿Prefieres este sitio en español?” banner so it doesn’t reappear on every page. Set only if you click the dismiss button. | 90 days |
md_session |
Keeps you signed in to the Workshop after you click a magic-link. Required for the optional account; never set for anonymous visitors. HttpOnly + Secure + SameSite=Lax. | 30 days, sliding |
Three cookies. That’s the entire list. There is no fourth, no advertising cookie, no third-party cookie set by an embedded widget. If a fourth ever ships, this page is the place where you find out.
Local storage
Some tools save your work in your browser’s local storage so you can come back to it later (audit history, plate-cost recipes, menu-engineering inputs, the Workshop save buffer). Local storage isn’t a cookie — it stays on your device, never makes a network request, and is per-origin. The keys are namespaced under md_* and workbench_*; you can clear them via your browser’s site-data controls.
Analytics doesn’t use cookies
The site uses Plausible Analytics, which is cookieless by design. Plausible counts page views in aggregate (URL, referrer, country, device type) without setting any cookie or persistent identifier. The tracker script is self-hosted from this domain (/assets/p.js) and the event-collection request is proxied through /api/event on this site’s worker, so your browser never connects to plausible.io directly. No cross-site tracking, no remarketing pixel, no Google Analytics, no Meta pixel, no LinkedIn Insight, no anything-else — this is a position the site won’t change. See /never/ #4 for the public commitment.
Opting out
The three cookies above are functional — they make the site work. There’s no “optional” bucket to consent away. If you want to opt out anyway, you have three real options:
- Use the site without signing in. The library and all the tools work fully without an account;
md_sessionnever gets set if you don’t use the Workshop. - Don’t use the language switcher. If you don’t click the EN/ES toggle,
md_localeis never set; the site renders in your browser’s locale on every visit. - Block cookies entirely in your browser. The site degrades gracefully — you’ll re-pick your language each visit and the Workshop won’t persist your sign-in, but every other surface still works.
Browser controls if you want them: Chrome · Safari · Firefox · Edge.
Why no banner
Cookie banners exist because some sites use cookies for purposes you have to consent to (advertising, cross-site tracking, profiling). This site doesn’t. The three cookies above are functional, the analytics is cookieless, and there’s no advertising surface. Adding a banner would be theatre that hurts trust without changing your data posture.
Changes
If a new cookie ships, this page changes and the change appears in the changelog. Material changes (new cookie, new vendor) get a paragraph; cosmetic edits just bump the date.
Contact
Questions about cookies or any of the above?
Email: don@muntin.digital
Reply within four business hours, Mon–Fri.
Sister surfaces: /privacy.html (the data policy) · /security/ (nine claims about how data is handled) · /never/ (five things this studio will not do) · /ai/ (how AI is used in the studio).