Draft. Not yet reviewed; published early so what the platform collects is visible before anyone is asked to trust it.

Privacy

Last edited 22 August 2026.

What we hold

• Your account: an email address and a password (stored hashed, by our authentication provider — never readable by us).
• Your venue and menus: everything you type in — names, descriptions, prices, marks, views — and every published revision.
• Operational state: which items are off the web menu and since when; which printer settings a menu uses.
• Who did what: which account published a revision or was added to a venue, and when.

What we do not hold

• No analytics or tracking on your web menus or on this site. No advertising identifiers. No third-party scripts on diners' pages.
• No card details: when pricing exists, payment will be handled by a payment provider and the platform will not see card numbers.
• Nothing about your diners. The web menu is a page; it sets no cookies.

Cookies

One: your sign-in session, on the management pages only. The public menu pages and the embed set none.

Where it lives

Data is stored with our database and authentication provider (Supabase) and served from our hosting provider, in the region stated on your account. [Fill in regions and sub-processors before launch.]

Your rights

You can export your menus at any time, correct anything yourself, and close your account; closure deletes your content within 30 days. For anything else — access, erasure, a question — write to the address on your account page. [Address to be set with the name.]

Who can see a menu

Published menus are public: that is the point. Drafts, past revisions and the management pages are visible only to the people you add to your venue. Each venue's data is isolated from every other venue's at the database level.