FoodiesHome›Cookie notice
LegalCookies, and why there is almost nothing to say
foodies.agency sets no tracking cookies, runs no analytics, and loads nothing from anyone else's server. This page exists to say that precisely, and to give you a control for the one piece of browser storage the site can ever use.
Last updated 6 August 2026 · Applies to foodies.agency
1. What this site does not set
This website sets no cookies at all. Not first-party analytics cookies, not third-party advertising cookies, not session cookies, not "strictly necessary" cookies. There is no cookie table below this paragraph because a table of cookies that do not exist would be a fiction.
Nothing here measures you. There is no Google Analytics, no Plausible, no Matomo, no Meta pixel, no TikTok pixel, no advertising tag, no A/B testing tool, no session recorder, no heat map, no consent-management platform, and no tag manager that could quietly introduce any of them later. The pages are static HTML with the stylesheet and the small script written directly into the file.
2. What this site does not load
Every asset on this site comes from foodies.agency itself: the CSS is inline, the typefaces are the ones already on your device (no Google Fonts, no Typekit, no font CDN), the icons are inline SVG or same-origin image files, and the screenshots are served from our own domain. No script, stylesheet, font, image, frame or beacon is fetched from a third party, so no third party learns your IP address, your browser or the page you were reading merely because you visited us.
The only outbound links are ordinary links you have to click, to the App Store, to Apple's standard licence agreement, and to the CNIL. Following one of those takes you to somebody else's site, with somebody else's privacy practices.
3. The one thing we may store
Browser storage other than cookies still counts under the ePrivacy rules, so here it
is in full. Foodies uses at most one entry in your browser's localStorage:
| Name | Type | Purpose | Lifetime |
|---|---|---|---|
foodies-consent |
localStorage (not a cookie) | Remembers the answer you gave to a consent prompt, so the site does not ask
again on every page. It holds a short value such as essential-only.
It contains no identifier, is never sent to our server, and nothing about you is
inferred from it. |
Until you clear it, or clear site data in your browser |
As of the date at the top of this page, no prompt is shown and this entry is not created. There is nothing on the site that requires consent, so asking for it would be theatre. We are documenting the key in advance, and giving you the control below, so that the day anything does need consent there is already a published, honest place to manage it, rather than a banner appearing with no explanation.
4. Withdrawing consent, or clearing it now
Consent can be withdrawn as easily as it was given. The button below removes the
foodies-consent entry from this browser immediately and tells you whether
there was anything to remove. It works without a page reload and sends nothing anywhere.
You can also do it yourself, and you should not have to trust our button: in Safari, Settings → Privacy → Manage Website Data; in Chrome, Settings → Privacy and security → Third-party cookies → See all site data and permissions; in Firefox, Settings → Privacy & Security → Cookies and Site Data → Manage Data. Blocking storage for this site entirely breaks nothing here.
5. The contact form
The contact page is the only page that sends anything anywhere, and only when you press the button. It posts what you typed, your name, your email address, your subject and your message, plus the page you arrived from, to our own API at api.foodies.agency, after you have ticked a consent box explaining where it goes. It sets no cookie, stores nothing in your browser, and there is no tracking pixel in the confirmation. If the request fails you are told it failed; the form never claims to have sent something it did not.
6. The app is separate
Cookies are a web concept, and the iOS app does not use them. What the app collects, why, and how to export or delete all of it in one tap is set out in the privacy policy. The short version: no advertising SDK, no analytics broker, no data sale, and direct messages that reach our server already encrypted.
7. Why we bothered
A cookie notice is usually the place where a site quietly admits to thirty trackers. Ours is the place where we can prove there are none, and that is worth a page of its own.
It is also a commitment. If we ever add something that stores data in your browser for a purpose beyond delivering the page, it will be listed in the table above, it will ask first, and the answer will be revocable from this page.
The same principle, in the app
No ads in your feed, no analytics broker, and messages that are end-to-end encrypted, we relay ciphertext and hold no key that opens it.
Related: privacy policy · terms of use · contact · recipe guides