Privacy

Last updated: September 6, 2026. This page describes what this site actually stores — no “we may collect” hedging.

What gets stored

Your name — visible to others in the same round
Budget, diet, things you won’t eat — shown only as aggregate counts (“2 vegetarian · 1 gluten-free”), never with names. Dietary restrictions often touch health or religion, so this is deliberately built so it can’t be traced back to a person.
That line is only shown to people who joined the round: someone who just opens the link doesn’t see it, and it is not on the preview card that chat apps generate when you share the link — links get forwarded, and this kind of information shouldn’t travel with them.
Your votes — the leaderboard shows totals only, never who voted for what
The starting point the host picks (a coordinate) — used to search for nearby restaurants. If you tap “use my current location,” that’s where you were at that moment

One cookie (dm_pid) — it holds a random ID and a signature, and nothing else: not your name, not your food preferences. It exists so you don’t have to retype things next time and so your votes are recognized as yours. Expires after 90 days. Clear your browser data and it’s gone — you become a brand new person
One more cookie (dm_lang) — which language you picked in the top-right corner. Nothing else

Your email (the “leave an email” box) — used only to tell you about that one thing. It is stored unlinked from your name and food preferences
Your feedback text, plus the technical context sent with it: current page, device type, window size, the last few errors. Not included: your name or food preferences. The token in an invite link is stripped before sending

Restaurant information comes from Google Maps. Two things worth knowing:

The nearby-restaurant search is sent to Google by our server, carrying the starting point the host chose and nothing about anyone’s name or preferences
The map on the page is Google’s embedded map — it loads directly from Google, so Google can see your IP address. That is true of any site with an embedded Google map

Rounds, restaurant options, votes: nothing is auto-deleted yet. Once people are actually using this, scheduled deletion gets added
Restaurant info pulled from Google: cached at most 7 days, then re-fetched
Cookies: 90 days

There are no accounts, so there’s no “delete my account” button. To get rid of things:

Clear your browser data — that severs this device from anything already recorded. After that you’re a new person
To actually delete stored content, use the feedback link in the footer and say so, with the link to that round. We’ll delete it by hand. Honestly: that process is crude, but it’s real — better than a self-service button that doesn’t exist

Every time a feature that stores data gets added, this page gets updated. The history lives in the code repository (real link coming after launch).