Privacy

Tablepass is used by café and restaurant owners and their staff. Diners ordering at a table never create an account and are never asked for a name, email, or phone number.

• Your account: the email address you sign in with, sent once as a one-time sign-in link. There is no password.
• Your menu: the restaurant name, menu text, prices, and the themes you publish.
• Table orders: the table label, the items and prices at the time of ordering, an optional free-text note from the diner, the status, and timestamps.
• Extraction usage: how many pages and tokens each AI extraction used, so we can see the cost and apply the free allowance. This row records no image and no menu content.
• Abuse protection: a truncated one-way hash of the caller's address for rate limiting. The address itself is never stored, and the hash cannot be reversed into an address.
• Page views: a plain counter per published menu. No cookie, no fingerprint, no per-visitor record.

• Menu photos. Images are read in memory to extract the menu and are discarded; they are not written to disk or to object storage.
• Diner identities. No name, no email, no phone, no account, no device identifier.
• Payment data. Nothing is charged during the launch promotion, so we never see a card number.
• Advertising profiles. There are no ad networks, no tracking pixels, and no analytics cookies.

The only cookie is a session cookie, set when you sign in so the app knows which account you are. Signing out clears it. If you use the app without signing in, menus stay in your browser's IndexedDB and never reach us, and a few small preferences (theme, checklist tick) stay in your browser's local storage.

Hosting and request logs: Vercel. Database: Neon. Sign-in email delivery: Resend. Menu extraction: Google's Gemini API, which receives the menu image and prompt for that request. We do not sell data or share it for advertising.

Menu content and table orders stay with your account until you delete them, so you can look back at past service. You can export everything as JSON at any time, and deleting the account removes it all. Nothing in this app deletes your orders automatically today; if that changes, the window will be stated on this page first. Extraction usage rows contain no diner data and are kept so cost accounting stays correct. Server request logs are kept by the hosting provider under its retention window and contain no request bodies.

You can export your menus, published pages, and orders as JSON, and delete your account and its data, from the launch page. Deleting the account also deletes its menus, published revisions, and orders. If you need help with either, contact us.

A support address has not been configured on this deployment yet. It will be published here before the promotion is advertised more widely.