Privacy policy

• Restaurant owners and staff, who have Tableside accounts.
• Diners, who use a restaurant's menu by scanning the code on their table. Diners don't create an account.

When you order at a restaurant, that restaurant sees your order and the details you send it, and uses them to serve you. We handle diners' information to provide the service to the restaurant.

From restaurant owners and staff

• Your account: your email address and password. The password is stored only as a secure hash, and we can't see it.
• Your restaurant: what you enter, such as its name, address, phone number, opening hours, menus, dish photos and videos, prices, ingredients, allergen and nutrition information, tables and settings.
• Your team: the email addresses you invite and each person's role.
• Order alerts: if you turn on notifications on a device, that device's push subscription (an address issued by your browser's push service, or in the iPhone and iPad app a device token issued by Apple) and a description of the browser and device, so we can alert you to new orders and table requests.
• Payments and billing: if your restaurant accepts cards or subscribes to a paid plan, Stripe collects the business and bank details it needs to pay you and bill you. We keep Stripe's account and payment references and the status and amounts of payments, refunds and subscriptions, never card or bank numbers.
• Email: the address that receives your daily summary and other emails about your restaurant.

From diners

• Your visit: scanning a table's code starts an anonymous session for that table. We don't ask for your name, email or phone number to browse the menu or order.
• Orders: what you add to your order, any notes, how you pay (card, cash, tip, splitting the bill) and the order's status.
• Table requests, such as asking for a server or the bill.
• Feedback you choose to leave about your visit or a dish. Only the restaurant sees it.
• Reservation requests: if you ask for a table, the name and phone number you give, plus any email address and notes. These go to the restaurant.
• Card payments: your card details go straight to Stripe, the payment processor, and never reach Tableside. We receive the payment's status and amount.
• AI waiter conversations: what you ask the AI waiter and its replies, kept with your visit so the conversation survives a page reload. See “The AI waiter” below.
• Voice input: if you use the microphone button, your browser's own speech service turns speech into text (Google's in Chrome, Apple's in Safari) under its own privacy terms. Tableside never receives audio, only the text, and only when you send it.
• Dish statistics: opening, adding or ordering a dish is counted in daily totals per dish, which contain no session, account, table or time of day. A short-lived note that your visit was already counted, so that opening a dish twice counts once, is deleted after 2 days.

From everyone

• Error reports: when something breaks, technical details are recorded (through Sentry) so we can fix it. They are set up to leave out IP addresses and personal details, and table links are removed before a report leaves your browser.
• Server logs: our hosting provider records requests to the service, which can include your IP address, for security and troubleshooting. Our AI waiter logs record timing and counts, not what anyone wrote.
• Visit statistics: we count which pages are visited, through Vercel Web Analytics, to see how people find and use Tableside. It uses no cookies and keeps no personal information, and links that contain table, invitation, order or payment codes have those codes removed before anything is recorded.
• Cookies: only the ones needed to keep you signed in and to keep your visit to a table working. No advertising or analytics cookies, and no tracking across other sites.

• To run Tableside: show menus, take orders and send them to the kitchen, process payments, show order status, and send alerts and emails.
• To answer diners' questions with the AI waiter.
• To give restaurants reports, such as sales and how often each dish is ordered.
• To keep the service secure and reliable, prevent abuse (for example, limits on how many messages the AI waiter takes) and fix problems.
• To contact restaurant owners about their account.

We don't sell personal information, use it for advertising, or share it with data brokers.

When a diner asks the AI waiter something, we send the message, the recent conversation and the relevant parts of the restaurant's menu to an AI model provider, which writes the answer. That provider is Anthropic, or OpenRouter, which passes the request to the company running the model. Providers handle messages under their own terms, and some, especially those offering free models, may keep them or use them to improve their models. Please don't share sensitive personal information with the AI waiter.

Answers are based on the restaurant's menu, but AI can make mistakes. If you have an allergy or a dietary requirement, always confirm with the restaurant's staff.

• The restaurant you order from or work for.
• Service providers that run parts of Tableside for us: Supabase (database and sign-in), Vercel (hosting and visit statistics), Stripe (payments), Anthropic and OpenRouter (the AI waiter), Sentry (error reports), Resend (email), and your browser's push service, such as Google, Apple or Mozilla, or Apple's push notification service in the iPhone and iPad app (notifications).
• When the law requires it, or to protect the rights, safety or property of diners, restaurants, Tableside or others.
• If Tableside is sold or reorganized, to the new owner, who must keep honoring this policy.

• Accounts and restaurant information: for as long as the account is open.
• Orders and payment records: these are the restaurant's business records. We keep them while the restaurant uses Tableside, and as long as needed for accounting, tax and payment disputes.
• Diner visits and AI waiter conversations: kept with the restaurant's records. We don't delete them automatically yet, and you can ask us to delete yours at any time.
• The note that a visit was already counted for a dish: 2 days.

• See, correct, delete or get a copy of your information: email privacy@tableside.menu. Restaurant owners and staff, please write from the address on your account. Diners, tell us the restaurant, the table and roughly when you visited. We'll reply within 30 days, and we honor these requests wherever you live.
• Delete your account: sign in and open Account (at the top of the dashboard, or in the app), then “Delete your account”. It's deleted straight away, along with your place in every restaurant team and your devices' order alerts. The restaurants keep their own records, such as orders and payments, without your name on them. A restaurant's only owner first makes someone else an owner, or asks us to close the restaurant. You can also email privacy@tableside.menu from your account's address and we'll delete it for you. Owners can remove a staff member from their team on the Staff page.
• Order alerts: turn them off with the “Turn off” button on the kitchen board, or in your browser or phone settings.

Information travels over encrypted connections (HTTPS). Each restaurant's data is kept separate at the database level, so one restaurant can't see another's, and staff see only what their role allows. Card details are held only by Stripe. No system is perfectly secure, so we can't guarantee absolute security, but we work to protect your information.

Tableside isn't directed at children under 13, and we don't knowingly collect their personal information. If you think a child has given us personal information, contact us and we'll delete it.

We're based in the United States. Our service providers may process information in the United States and other countries.

When we change this policy, we'll update the date at the top. If a change is significant, we'll also tell restaurant owners by email or in Tableside.

Beacon Digital Consulting LLC, Jersey City, New Jersey, USA.
Privacy questions and requests: privacy@tableside.menu