Privacy Policy

1. Who this policy applies to

TableFlo is a restaurant reservation, waitlist, guest-history, and front-of-house management service. This policy applies to restaurant owners and authorized users of TableFlo. Restaurants are responsible for telling their guests how the restaurant uses guest information and for meeting any privacy obligations that apply to their business.

TableFlo is a product operated by TATIANKA LTD, a private limited company registered in England and Wales under company number 17042311. Its registered office is 71–75 Shelton Street, Covent Garden, London, United Kingdom, WC2H 9JQ.

2. Information TableFlo processes

Depending on how a restaurant uses the service, TableFlo may process:

• Owner account information, including an email address and authentication records.
• Restaurant name, settings, operating information, tables, and workspace information.
• Guest names, phone numbers, party sizes, reservation and waitlist details, notes, assigned tables, and visit status timestamps.
• Technical records needed for security, synchronization, reliability, and troubleshooting.
• Google account email and authorization information when an owner chooses to connect Google Drive.

3. How information is used

TableFlo uses information to:

• Provide reservations, waitlists, guest history, table management, exports, and backups.
• Authenticate restaurant owners and keep each restaurant workspace separate.
• Synchronize approved changes, recover from short connection outages, and prevent duplicate records.
• Protect the service, investigate errors, and comply with applicable legal obligations.

TableFlo does not sell guest or restaurant data and does not use it for advertising.

4. Storage, isolation, and device caching

Supabase provides TableFlo's hosted authentication and database infrastructure. Restaurant-owned records are associated with a restaurant workspace and protected by database-level access controls so one restaurant cannot access another restaurant's data. TableFlo may keep a limited cache and pending-change queue on the restaurant's device to support brief internet outages. The cloud database remains the authoritative record.

5. Optional Google Drive access

Google Drive connection is optional. When a restaurant owner connects Google Drive, TableFlo requests limited access to create and manage backup files created by TableFlo in that owner's Google Drive. Google Sheets is used only as a backup/export destination and is not TableFlo's main database.

TableFlo stores Google authorization tokens in encrypted server-side storage. It never asks for or stores the owner's Google password. TableFlo does not read unrelated Drive files. Access is used only to create, update, and manage TableFlo backup files requested by the restaurant. Google user data is not sold, used for advertising, or transferred to third parties except as needed to provide the requested backup service, maintain security, comply with law, or act with the user's explicit consent.

TableFlo's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Owners can disconnect Google Drive from TableFlo at any time. Disconnecting removes the saved authorization connection from TableFlo. Existing backup files remain in the owner's Drive until the owner deletes them there.

6. Operational diagnostics

TableFlo records limited technical error information so owners and support can diagnose reliability problems. These records may include the error category, message, time, route, and connection state. TableFlo is designed not to place guest names, phone numbers, reservation notes, passwords, or Google authorization credentials in diagnostic events. Diagnostics are isolated to the restaurant workspace and visible only to its owner.

7. Service providers and disclosures

TableFlo relies on service providers such as Supabase for authentication and hosted data, Google for an owner-requested Drive backup, and hosting providers needed to operate the application. Information may also be disclosed when required by law, to protect users or the service, or during a business transaction subject to appropriate safeguards.

8. Retention and deletion

Restaurant records are retained while the workspace is active or as needed to provide the service, maintain security, meet legal obligations, and resolve disputes. Normal completed visits remain in History unless an authorized owner uses a protected administrative deletion process. Owners should export needed records before requesting workspace deletion.

9. Security

TableFlo uses authenticated access, tenant-scoped database policies, encrypted connections, server-side secrets, and restricted administrative operations. No service can guarantee absolute security, so restaurant owners should protect account credentials, sign out of shared devices, and promptly report suspected unauthorized access.

10. Your choices

Restaurant owners can review and update operational data, export records, disconnect Google Drive, and request account or workspace assistance. Requests involving guest data may need to be directed to the restaurant that collected it because the restaurant controls that data.

11. Children

TableFlo is a business service for restaurants and is not directed to children. Restaurant users should not knowingly enter information they are not legally permitted to process.

12. Changes and contact

This policy may be updated as TableFlo develops. Material changes will be identified by a revised effective date. Questions or privacy requests can be sent to tableflowmanagement@gmail.com.

Legal operator: TATIANKA LTD, company number 17042311, registered office 71–75 Shelton Street, Covent Garden, London, United Kingdom, WC2H 9JQ.