Your information at Table Voice

Who we are

TableVoice.live is a unit of Eisberg. Eisberg operates this website and service. GSTIN: 29AACFE9184D1Z9.

For support and privacy requests, email info@eisberg.in.

What we collect and why

Our public pages have no advertising trackers, analytics scripts, contact forms or embedded media. Our hosting service processes technical request information, such as IP address and browser details, to deliver and secure the website.

For invited workspace users, Google sign-in supplies identity information such as an account identifier, email, name and profile details. We use it to sign you in and connect you with your assigned access. We do not receive your Google password.

The workspace stores your assigned restaurant, role, access status and relevant administrative activity. When notifications are enabled, it stores the browser push subscription and notification delivery, receipt and confirmation records. These support access controls, service testing and complaint handling.

If you contact us by email, we use the information you send to respond and manage your request.

Text message alerts

If a restaurant adds your phone number for Table Voice alerts, we use it only to send you guest alerts for that restaurant. We never sell or share phone numbers or text-message consent with third parties for marketing. Message frequency varies; message and data rates may apply. Reply STOP to opt out or HELP for help. See SMS alerts and terms.

Guest feedback and testing

Guest feedback is available only at restaurants enabled by the service provider. With recording permission, an assigned staff member can collect up to two and a half minutes of audio, a guest rating, and the restaurant, table or area, staff reference and collection time. Audio is processed by our AI service providers to prepare an English transcript and, when the guest speaks another language, a written copy of their words in that language. The transcript is analysed to categorise feedback and identify complaints. AI output can be inaccurate; authorised restaurant users should review it before taking action. The separate early pilot is not the service described on this website.

Restaurant operators are responsible for explaining their guest-facing use of Table Voice and obtaining any required recording permissions before collecting guest feedback.

Services and access

We use Google Cloud and Firebase to host the application and public pages, Google for sign-in, and Supabase for authentication and workspace data. Enabled notifications pass through the push service used by your browser or device. Private recordings are stored in Google Cloud Storage. Our AI service providers process the audio or transcript needed to prepare transcripts and reports; this processing may occur outside the application hosting region. We record usage and cost information to administer the service. Google Workspace sends configured owner report and support notification emails. These services process information needed to perform their functions.

Authorised restaurant users receive information according to their assigned access. Dashboard playback is restricted to the restaurant's approved listener list, with a maximum of three current users; knowing a recording identifier does not grant access. Feedback, reports and complaint history have separate role-based access. In-app support stores the messages and replies you submit; avoid including unnecessary sensitive information. Service-provider administration is separate from restaurant access. Information may also be disclosed when required by applicable law or to investigate abuse and protect the service.

The current application and database are hosted in European regions. Public website delivery, Google sign-in and browser notification services may process information in other countries.

Keeping and deleting information

Recording playback expires after 60 days. Storage deletion is scheduled from the recording time and is processed asynchronously; deleted recordings may remain in restricted recovery storage for a further seven days. Transcripts, reports, historical scores, usage and audit records can remain beyond the audio retention period to support reporting, security and service administration. Account, access and operational records are kept to support the workspace, security and troubleshooting. Current testing does not provide automatic expiry or a self-service deletion tool for every record. To request access, correction or deletion, contact info@eisberg.in. We will verify the request and explain what can be removed and any records that must be retained for security or legal reasons.

Deletion from active systems may not immediately remove copies in service logs or backups. Where a restaurant controls the information in your request, we may direct you to that restaurant or work with it to address the request.

Your choices

You can sign out of the workspace, turn off notifications in browser or device settings, and ask your organisation to update or revoke your access. The workspace uses local browser storage to keep your sign-in session and device connection across tabs. Use Sign out when leaving a shared device. Revoking notification permission stops future delivery to that browser but does not itself delete historical delivery records.

Changes to this notice

We will update this page when the service or its information practices change. The effective date above identifies the current version. Questions can be sent to info@eisberg.in.