Cookies & Storage

Last updated 14 September 2026

In short

PantryDo sets three cookies, all of them needed to sign you in and keep you signed in. There are no advertising cookies and nothing that follows you to other sites. The one thing that is genuinely optional — counting page views — is off until you say otherwise, and you can change that here, now, without leaving this page.

Your choice

Checking what you chose…

Your answer is remembered on this device and holds good for thirteen months, after which the question comes round again rather than a years-old click being treated as a standing answer. Nothing on this page is conditional on it: refusing changes nothing about how PantryDo works for you.

The cookies

All three are first-party — set by PantryDo itself, readable by nobody else — and all three are strictly necessary, in the sense the ePrivacy Directive uses: without them you cannot sign in, and a service you asked to sign into cannot work.

Name	What it does	How long
`pantrydo.session-token`	Keeps you signed in. It holds a signed token identifying your account, and is `httpOnly`, so no script — on this site or any other — can read it.	Until it expires or you sign out
`pantrydo.csrf-token`	Protects the sign-in forms from cross-site request forgery: it lets the server tell a form you submitted from a form another site submitted on your behalf.	The browsing session
`pantrydo.callback-url`	Remembers where you were heading when you were asked to sign in, so an invite link still takes you to the invitation afterwards instead of dropping you somewhere else.	The browsing session

Choosing Continue with Google sends you to Google, which sets its own cookies on its own domain as part of signing you in. Those are Google’s, governed by Google’s privacy policy, and PantryDo neither sets nor reads them. Signing in with an emailed link or a password avoids Google entirely.

Analytics, and why it is the only thing you are asked about

Page views are counted with Vercel Analytics, and only if you allow it. It stores nothing on your device, sets no identifier, and cannot follow you between sites: it produces counts of how often pages were opened, not a record of who opened them. That is the whole of the measurement on this site. There is no Google Analytics, no advertising pixel and no third-party tracker of any kind.

Strictly it is the sort of measurement that could rest on legitimate interests rather than consent — it sets nothing on your device and identifies nobody. It is put to you as a question anyway, because the honest version of “we have a legitimate interest” is usually just “we would rather not ask”. The script is not loaded at all until you answer, so refusing is not a matter of a flag being set after the fact: there is nothing to switch off.

The sign-in cookies are not offered as a choice, because they cannot honestly be one — they are what signing in consists of, and the ePrivacy rules exempt exactly that. Nothing else is hiding behind that exemption: the table above is the complete list.

If your browser sends a Global Privacy Control signal, that is taken as the answer and you are never shown the banner at all.

What is kept in your browser

Two things are stored on your device rather than sent anywhere. Both stay in your browser, on that device, and neither is readable by PantryDo’s server:

pantrydo_cookie_consent in local storage — your answer to the question above, and the date you gave it, so that you are asked once rather than on every visit. Clearing it means being asked again, which is the safe way round.
pantrydo_split_ratio in local storage — where you dragged the divider in the split view, so the panes come back the width you left them. A convenience for you on that device, nothing more.
The pantrydo-v2 cache, filled by the service worker that makes PantryDo installable. It holds the app’s own build files, icons, logo and offline page. Pages and data are deliberately never cached: every page behind the sign-in goes to the network, so nobody is ever shown a stale pantry or a page belonging to another session.

Clearing them

Signing out drops the session cookie. Beyond that, every browser lets you clear cookies and site data for a single site, and you can do that for PantryDo at any time — it signs you out, forgets your divider position and forgets your answer above, and nothing else is lost, because everything that matters lives on the server rather than in your browser.

Blocking cookies for this site altogether is your right, but sign-in will not work: the session cookie is how the server knows the next request is still you.

Uninstalling the installed app, or clearing site data, also removes the service worker cache.

What happens to data once it reaches the server is in the Privacy Policy. Anything unclear here, ask: vitor.margis@gmail.com.