Privacy

1. Staff accounts

Each staff member has an account made by the restaurant's admin. Tablewise keeps their name, email address, role, the screens they may open, and whether the account is switched on.

Passwords are handled by our sign in provider, Supabase Auth, and are never stored by Tablewise in readable form.

2. Orders, bills and payments

For each table visit Tablewise keeps the table, the number of guests, the dishes ordered with their choices and notes, the bill, and how it was paid: cash or QR transfer, the amount, and an optional reference and note.

Guests are not asked for their names, phone numbers or email addresses. Tablewise does not take card payments and never sees bank or card details. A QR transfer happens in the guest's own banking app.

3. Expenses and reports

Expenses the restaurant records are kept with their type, amount, date, who was paid and a note. Reports are worked out from these and from the bills.

4. Audit log

Changes such as payments, price changes, staff changes, cancelled orders and settings are recorded with the staff member who made them and the time, so the restaurant can see who changed what.

5. Where data is kept

The app's database and sign in run on Supabase. The app and this website are hosted on Vercel. Each restaurant's data is used only to run that restaurant's screens and reports.

6. Cookies and website measurement

Staff screens use a sign in cookie so a person stays signed in. It is needed for the app to work.

The public pages of this website may use Microsoft Clarity and Google Analytics to understand how visitors use the site, such as which pages are viewed. These are not loaded on staff screens.

7. Changes

If what Tablewise stores changes, this page will be updated and the date at the top will change.