Privacy notice

Damz operates Tablio. We store business account details, team membership, menus, table visits, orders, service requests, payment references and optional loyalty records to provide restaurant operations.

Guest information

Guests can order without creating an account. Table visits can include a guest’s name and requests to staff. Optional loyalty uses a mobile number, visits, paid-order history, points or stamp balances, reward activity, prepaid pass uses and accepted offer versions. With the guest’s permission, staff may record a birthday (month and day only) and a referrer’s mobile number to verify those specific offers. Birthday and referral details are optional. Reward and manager adjustment history is recorded for accountability. Website loyalty signup also stores a verified email, name, selected restaurant programs, the terms accepted, joining dates and notification preferences. Your private loyalty inbox stores up to 50 recent updates. New-offer notifications from your restaurant are optional and require a separate opt-in; they never enroll you in a new program automatically. Private visit and order links provide access to their associated records; keep them private.

Restaurant discovery and location

Restaurant discovery works without device location permission. If you choose a city or neighbourhood, we remember that preference in a cookie for up to 30 days. If you tap Use my location and grant browser permission, your coordinates are rounded to roughly 100 metres before being sent to Tablio. This approximate location is kept in an essential, browser-inaccessible cookie for one hour to calculate straight-line distances to restaurant map pins. It is not saved in the application database or added to search URLs. You can clear it from the area selector. We do not continuously track your location or send it to a geocoding provider.

Guest discoveries and shared ideas

Saving a dish, following a guest or sharing an idea creates a browser profile without an email or signup. A protected cookie provides access for up to one year. We store your optional public name, taste preferences, saved dish references, follows, group votes and recommendation feedback. Language choice stays in local browser storage. Clearing the cookie removes access to this browser profile. Lists, questions, answers, food trails, pairings and their chosen names and messages are public; anyone with a shared link can read them. Personal notes included in a shared dish link are visible to anyone with that link. Avoid including private information. Community suggestions and browser votes are not proof of a visit or identity. Reports and moderation reasons are private to platform administrators. We use a protected network-address digest for abuse limits. Community records are included in application backups. You can remove your own shared ideas from My ideas or contact us for other access or deletion requests. Optional voice search uses the browser speech service after you activate it; Tablio receives the search text, not an audio recording. Voice availability and processing depend on your browser and device.

Public restaurant reviews

If you submit a review, your chosen display name, review text, selected dish names and reorder choices, visit recommendations, visit date and publication date are public. Earlier reviews may also include star ratings. Private food passport cards and visit stamps are stored only in this browser for this site and are not uploaded unless you choose to publish a table note. Clearing browser data removes those private cards; removing a local card does not remove a published review. Your private visit credentials, contact information and payment details are not published. We retain the visit reference privately to verify eligibility and prevent duplicate reviews. Verified visit describes a completed, paid order recorded in Tablio; it does not verify the display name or guarantee the opinion. Review reports require email verification and store a report reason and a protected account identifier for platform moderation. Review and moderation records can remain in application backups. Contact us for correction or deletion requests.

Platform usage and email preferences

We record daily workspace attendance and the last activity time for signed-in owners and team members to understand platform use. Visible workspaces report attendance while recently attended; hidden or idle tabs stop reporting. Platform administrators can view account, usage and subscription reports. Optional Tablio product news and offers require a separate business-owner opt-in, which can be changed in Account & billing. We store the preference, current email and change date, and exclude opt-outs and unrecorded preferences from marketing exports. Account and billing messages are separate.

Team accounts

We store a member’s email, optional name, role, invitation and joining dates, and access status. Join links expire after seven days. Owner changes to team access are recorded for accountability. Removed memberships remain blocked until the owner creates a new invitation.

Service providers and storage

Supabase handles authentication and database storage. Vercel hosts the application. Razorpay handles platform subscriptions and optional payments to connected restaurant accounts. We store payment references and statuses, not full card details. Essential authentication cookies and browser session storage support sign-in, checkout recovery and private visit tracking. The application does not include advertising trackers.

Optional notifications and AI artwork

If you enable order-ready or loyalty browser notifications, we store the browser’s push endpoint and encryption keys and send messages through its push service. You can turn permission off in your browser and change loyalty alert preferences in My rewards. When a restaurant generates optional AI QR artwork, Replicate receives its prompt and public table link. Guest details, loyalty records and order history are not sent for artwork generation.

Access and retention

Authorized staff access records according to their roles. Business operational records and team access history are retained while providing the service and until an approved deletion or archival request is carried out; ordinary order history is not automatically deleted. The scheduled maintenance worker removes expired rate-limit counters after one day, delivered notification jobs after seven days and exhausted notification jobs after thirty days. Invalid push endpoints are removed when the push provider reports them.

Backups follow the deployment’s configured retention and can retain earlier copies until they expire. Payment providers apply their own retention rules. A subscription cancellation stops renewal and does not itself delete business records.

Requests and contact

For guest orders, loyalty or service records, contact the restaurant first. Business owners can export available reports in the workspace and contact theindieedeveloper@gmail.com for account access, broader export, corrections or deletion. We verify authority before disclosing or deleting records and may retain records needed to resolve payment disputes or meet applicable obligations.

Operator: Damz. Updated 2 November 2026.