This document is a draft prepared for review. It describes how Palatis intends to work and is not legal advice.
This page lists every cookie and similar technology Palatis sets, what each one is for and how long it lives. There is no advertising network on this site, no cross-site tracking pixel, and nothing that follows you once you leave palatis.app.
The short version
Nine cookies. Three are strictly necessary and cannot be switched off, because without them you cannot sign in or submit a form safely. Three are functional and remember choices you made. Two are first-party analytics. One records which partner or article sent you, so we can pay a referral fairly. The last six only appear after you say yes.
How consent works
On your first visit you get a banner with two equally weighted buttons, Accept and Reject, and a link to choose categories one by one. Rejecting is one click and sets nothing beyond the record of your choice. We do not use a scroll, a timer or a close button as consent, and we do not treat continued browsing as agreement.
Your choice is stored for twelve months, after which we ask again. You can change or withdraw it at any time from the Cookie settings link in the footer, and withdrawal takes effect immediately: the relevant cookies are deleted on the spot rather than at their expiry date.
What we set
| Name | Category | Purpose | Duration |
|---|---|---|---|
| pal_session | Strictly necessary | Keeps you signed in between page loads | Session |
| pal_csrf | Strictly necessary | Single-use token that stops a third-party site submitting a form as you | Session |
| pal_consent | Strictly necessary | Records which cookie categories you allowed | 12 months |
| pal_locale | Functional | Remembers whether you read the site in English, French, Spanish or Dutch | 12 months |
| pal_units | Functional | Remembers metric or imperial measures and your temperature unit | 12 months |
| pal_pantry_draft | Functional | Holds an unfinished pantry edit so a dropped connection does not lose it | 7 days |
| _pal_stats_id | Analytics | A rotating first-party identifier used to count unique visits | 13 months |
| _pal_stats_ses | Analytics | Groups page views into one visit | 30 minutes |
| pal_ref | Attribution | Records which partner, journal article or newsletter referred you, so a referral fee goes to the right place | 30 days |
What we deliberately do not use
- No advertising or retargeting tags, and no conversion pixels from social networks.
- No data brokers, no audience segments, no lookalike lists.
- No cross-device fingerprinting, and no attempt to identify you from your fonts, canvas or hardware.
- No session recording or heatmap tool that would replay what you typed into a pantry field.
- No third-party analytics that combines your visit here with your behaviour elsewhere.
Our analytics runs on aggregated first-party counts. It cannot follow you to another website, and the numbers it produces are page views, referrers and feature usage — not people.
Third-party technologies
Two categories of third-party technology reach your browser. Our content delivery network sets no cookie but does read your IP address to route the request and block abuse. Embedded partner checkout, used only when you complete a grocery hand-off on a partner site, is governed by that partner's own cookie policy from the moment you land there — we cannot set or read cookies on their domain, and they cannot set any on ours.
We also load two typefaces from Google Fonts. That request exposes your IP address to Google and sets no cookie. If you prefer to avoid it entirely, blocking the font domain leaves the site fully readable in your system serif and sans-serif.
Local storage and the app
The web app keeps a small amount of data in browser local storage rather than in cookies: your unsent build queue, the last flavor map you viewed so the screen paints instantly, and an offline copy of your pantry list. None of it is transmitted for analytics, and clearing site data removes all of it. The mobile apps use the equivalent operating-system store and no advertising identifier.
Browser controls and signals
Every browser lets you block or delete cookies, and most let you do it per site. Blocking strictly necessary cookies will break sign-in; blocking the rest costs you only the conveniences described above. We honour Global Privacy Control and Do Not Track signals by treating them as a rejection of the analytics and attribution categories, so you do not need to interact with the banner at all if your browser sends one.
Changes
Adding a cookie means updating this table before the cookie ships, and asking for consent again if the new one is not strictly necessary. Withdrawn or renamed cookies are removed from the table in the same release. Questions go to [email protected].