TableGo Privacy Policy

Scope

MGM Studio provides TableGo for restaurant management, cashier operations and QR ordering. This policy covers the TableGo app and web interfaces.

Accounts and trial mode

Restaurant owners and staff register with email and password or sign in with Google. TableGo processes account identifiers, full name, email, phone number if provided, profiles, memberships, roles and sign-in sessions. Supabase Auth handles passwords and authentication. Google processes sign-in information when you choose Google sign-in. QR ordering customers do not need an account. Trial mode creates an anonymous authentication account and separate sample restaurant data on the server for 72 hours. Do not enter personal information or real business data in the sample restaurant.

Restaurant and order data

TableGo stores restaurant details (name, address, contact phone, logo, language and currency), staff and invitation codes, categories and menu items (names, descriptions, prices, images and availability), tables, QR codes, table sessions, orders, quantities, notes, service status and action timestamps. Cashier data includes invoices, discounts, adjustments, refunds, external payment status, revenue reports and audit logs. Recording payments does not require card numbers or bank login credentials.

Public information and sharing

Restaurant details and menus appear on QR ordering pages. Anyone with a table link can view the session information the page provides, including ordered items and notes. Restaurant owners and authorized members access data according to their roles. When you print or share invoices, reports or QR codes, data is passed to the printer, app or recipient you select. Avoid sensitive information in notes and sharing table links beyond their service purpose.

Photos and notifications

You choose photos from your library to upload restaurant logos or menu images to Supabase Storage. Restaurant and menu images may be public; only upload content you are entitled to use. When notifications are enabled, Firebase Cloud Messaging (FCM) processes notification tokens; TableGo stores the token, installation identifier, platform and account association to send operational notifications. You may deny or disable notifications in device or browser settings.

Device storage

The app stores sign-in sessions, language, the selected restaurant and an installation identifier on your device or browser. The ordering page stores carts and request state for each table link to restore actions and reduce duplicate submissions. Sign out and clear browser data when needed on shared devices. Clearing local data or uninstalling the app does not delete server data.

Usage analytics

TableGo uses Google Analytics for Firebase in the merchant app and web interfaces to measure usage, understand registration, trial, restaurant setup and ordering journeys, identify incomplete flows and improve the product. Analytics may automatically record information such as users and sessions, session duration, app opens or updates, operating system, device model, browser, approximate geography and an identifier for a particular app installation; cookies or similar technologies may be used on the web.

Custom TableGo events cover milestones such as sign-in, registration, starting a trial, creating a restaurant, menu item or QR code, inviting staff, opening a menu, viewing an item, adding or removing cart items, beginning an order submission, successful or failed order submission and order completion. Accompanying parameters are limited to operational context such as the app surface, language, action source, quantity and value. TableGo does not intentionally send email addresses, phone numbers, customer names, item notes, QR tokens, table-session identifiers or passwords to Analytics. Google processes Analytics data under Google's policies. You may use device or browser privacy controls and Analytics-blocking tools where available.

Purposes

Data supports authentication, access control, menu and order synchronization, service coordination, cashier operations, reporting, notifications, usage measurement, product improvement, support and system protection. We do not sell personal data.

Providers and data processing

Supabase provides authentication, database, image storage, real-time synchronization and server request processing. Google/Firebase provides Google sign-in when selected, Google Analytics for Firebase, FCM notifications and hosting for web interfaces deployed on Firebase Hosting. Infrastructure providers may process IP addresses, device or browser information and technical logs to operate, deliver and secure services. Data may be processed outside your country depending on infrastructure locations.

Retention and deletion requests

Account and restaurant data remains on the server to provide services and maintain operational history. Some archive or deactivate actions only change record status. Trials expire after 72 hours; sample restaurant data and the associated anonymous account enter automatic cleanup after expiry and may not be deleted at the exact expiry time. To request access, correction or deletion of your account and data, use the email below. We may need to verify your identity and restaurant authority; the scope is reviewed in light of other people's data, security needs and applicable retention obligations and will be discussed when handling your request.

Security and choices

TableGo uses authentication, restaurant and role access controls, and server-side data and file access policies. No system is completely secure. Protect passwords, invitation codes and QR links, and assign appropriate staff permissions. You can edit permitted information in the app, decline photo or notification access, clear local data and contact us about your data.

Children

TableGo supports restaurant operations and ordering and is not designed specifically for children. If you believe a child has provided personal information inappropriately, contact us so we can review and address it.

Updates and contact

We update this policy when features or data practices change and publish the update date here. Responsible entity: MGM Studio. For orders, contact the restaurant serving you. Privacy questions and data requests: support.mgm.studio@gmail.com .