Privacy policy
What we store, why, and what we will never do with it. Last updated September 3, 2026.
What we store
About you: your name, email address, and restaurant name — that's what sign-up asks for, and that's all it asks for.
About your restaurant: your menu (dishes, prices, artwork), its Spanish translation, your published page's design — and, if you use the scheduler, your staff's first names, roles, availability and shifts, because that is what a schedule is made of.
About your guests: almost nothing. Menus count how often they are opened, which language was used, and which dishes get tapped — as daily totals. We do not identify diners, we set no advertising trackers, and a guest can read your menu without an account, a cookie banner, or an app.
What we do with it
Run the service. Your menu is stored so it can be served; your schedule is stored so you can edit it; the tap counts exist so your dashboard can tell you what's working. Menu text and schedule text are processed by an AI service (Anthropic's Claude) to produce translations and schedule drafts — that processing is not used to train anyone's models.
What we will never do
We don't sell data. We don't rent lists. We don't run ads. Your staff's names are not marketing material and your guests are not a product.
Where it lives
Data is stored with Supabase (our database) and served through Cloudflare (our host). Both are established providers with their own security practices; access on our side is restricted to the founder.
Public means public
Your menu page is a public web page — that is the point of a QR menu. Everything else (your schedule, your dashboard, your account) is private to your login.
Deleting your data
Text us and it's gone: account, menu, schedule, counts — deleted, not archived. 713-677-1009.
See also: the terms of service.