We read tables, not people.
TableWave needs to know whether a table is taken, waiting or dirty. It doesn’t need to know who is sitting there, so it never tries to.
What TableWave does
- Detects people as anonymous shapes, only to know if a table is taken.
- Blurs faces on screen: every person it detects is blurred before an image is shown or saved.
- Keeps table events, like “seated 20:14” or “reset in 3 min”, for 30 days by default.
- Runs on a computer inside your restaurant. Video is not uploaded or stored by TableWave.
- Gives you the door notice, staff notice and data agreement in your language.
What it never does
- No facial recognition, face matching or face templates.
- No names, no identities, no tracking across visits.
- No continuous recording. Short clips are off by default; if the owner turns them on, they are face-blurred and deleted automatically after 30 days.
- No per-employee scores.
- We never sell data, and never show ads to your guests.
Where your data goes
Nowhere, mostly. Video is analysed on the computer in your restaurant and thrown away, unless you switch clips on. What’s kept is a list of table events. TableWave never uploads or stores your video.
Your cameras
Stream on your local network
Computer in the building
Detects, blurs, discards frames
Table events
“T7 seated 20:14”, kept 30 days
Alerts, licence, optional remote view
What leaves: short text alerts, a licence ping and, only if you turn on remote access, live blurred views to your own browser
If a box were ever compromised, the most an attacker could get is table states, 30 days of blurred event clips if you turned clips on, and camera stream addresses. No card data and no face templates; guest names only if your team typed them into the waitlist.
How the computer is protected
No inbound internet ports
The computer only makes outgoing connections: alerts, the licence check and, if you switch on remote access, an encrypted tunnel to your PIN-protected console. Nothing is opened on your router.
Encrypted on your network
Tablets and staff devices connect to the console over HTTPS.
PIN-protected settings
Setup, health and clips sit behind an admin PIN, stored as a salted hash.
Signed and tamper-checked
Licences are signed and bound to the machine, and the app checks its own files for tampering. A copied install stops working on any other computer.
Locked-down box
Our box ships with a firmware password and no admin account for staff. Full-disk encryption is planned, not yet in place.
Cameras kept apart
At install we put cameras on their own network segment and change default camera passwords.
What we set up with you
You own the data; we process it for you. Every install includes:
Camera analytics.No facial recognition.
“This venue uses camera analytics to manage tables. No facial recognition. The analytics store no video.”
A notice for your entrance, in your language. Plus a written notice for your staff and a data processing agreement. In Mexico we also supply the aviso de privacidad.
Draft, under legal review Terms of serviceThe agreement for using TableWave.
Draft, under legal review Data processing agreementAsk us for the current version.
On request
Privacy law differs by country and state. We’re having our approach reviewed by counsel in each market we sell in, and we’ll publish what they confirm. Nothing on this page is legal advice.