Privacy Policy
Last updated: 19 November 2026.
1. Who is responsible for your data?
Ingstad Media AS (Norwegian organisation number 932 155 125), referred to as “TableBooking”, is the data controller for information about customers, account users, billing, security and the operation of tablebooking.io.
When a restaurant uses TableBooking to manage guests, reservations and employees, the restaurant is normally the data controller and TableBooking acts as its data processor. This processing is governed by our data processing agreement (Norwegian).
Contact us at post@ingstadmedia.no.
2. Data we process
Customers, account users and employees
- Name, work email, phone number and authentication status
- Restaurant, role, permissions, invitations and account activity
- Restaurant profile, opening hours, table setup and settings
- Technical security data, such as timestamps, session status, IP/device data held by the authentication provider and controlled error logs
- Invoice and payment references for paid subscriptions
Google Business Profile (optional connection)
A restaurant can connect TableBooking to its own Google Business Profile in Settings. The connection uses Google sign-in (OAuth) with the “business.manage” permission. We use it only for actions the restaurant starts in the dashboard:
- reading which business accounts and locations the signed-in Google user manages, so the restaurant can choose the right location
- reading the name, address, phone number, opening hours and Place ID of the chosen location and showing them as suggestions. Nothing is overwritten until the restaurant confirms each field
- adding the restaurant’s TableBooking booking link to the profile as a reservation link, and removing that link again on disconnect if the restaurant chooses to
We store an encrypted refresh token, the chosen location and a reference to the link we created. Access tokens are not stored. Details the restaurant chooses to import are stored as ordinary restaurant settings. We do not change other parts of the profile, do not read reviews or messages, and do not use data from Google for advertising, profiling, sale or training AI models. The data is not shared with anyone other than the providers that operate the service.
The restaurant can disconnect at any time in Settings. We then revoke access at Google and delete the stored token. Access can also be removed at myaccount.google.com/permissions. TableBooking’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Guests making a reservation
- Name, phone number and email
- Date, time, party size and reservation status
- Comments that guests choose to provide. Restaurants must not request unnecessary health information or other special categories of personal data.
- Reservation history at the relevant restaurant
Allergies for one booking
Allergy information may be health data. The separate allergy field is optional and requires distinct, explicit consent for the restaurant and TableBooking to process the information for this visit. You can book without using the field and contact the restaurant directly instead. The restaurant is the controller; TableBooking processes the information on its instructions.
We record the consent version and time. Allergy details are stored separately from booking lists and guest profiles and are shown only to authorised staff on the relevant booking. They are not copied to future visits, email, ordinary booking CSV lists, analytics tools or AI. Do not put health information in other free-text fields.
Use your private booking link to change or remove the details. Removal withdraws consent and deletes the details from the active database without cancelling your table. Cancellation or a recorded no-show also deletes them. Otherwise, they are hidden 24 hours after the scheduled end and deleted by hourly cleanup. Rescheduling moves the expiry to the new visit. Encrypted backups may retain older copies until rotation; those copies are not used in normal operations.
Web analytics and restaurant-account statistics
With consent, we use PostHog’s EU endpoint for anonymous web analytics with a random tab ID: page paths, article slugs, coarse traffic sources, calls to action, registration starts, email account creation and booking-code copies. We send no query strings, full URLs, raw referrers or form contents. Consent can be withdrawn using the cookie settings.
Separately, the server sends pseudonymous business events for restaurant creation, bookings and the first widget booking, subscriptions and support categories. A keyed hash replaces the restaurant ID. Booking properties are limited to source and party-size bucket, subscriptions to plan, and support to category. These events use no cookies or browser storage and are independent of web analytics consent. Names, email addresses, phone numbers, reservation times, notes, allergies and support contents are not sent. Browser and restaurant IDs are not linked. Pseudonymous restaurant data is not anonymous.
3. Purposes and legal bases
| Purpose | Legal basis |
|---|---|
| Create accounts and provide the service to the customer | Contract, GDPR Article 6(1)(b) |
| Process guest data on behalf of the restaurant | The restaurant’s documented instructions and legal basis |
| Account security, abuse prevention and operational stability | Legitimate interests, GDPR Article 6(1)(f) |
| Invoicing, bookkeeping and legal requirements | Contract and legal obligations |
| Optional product analytics or newsletter | Separate consent for each purpose, GDPR Article 6(1)(a) |
| Optional allergy information for the visit | Explicit consent, GDPR Articles 6(1)(a) and 9(2)(a) |
Which messages are sent?
- Guest booking emails
- Booking receipt, restaurant confirmation, changes and cancellation are sent to the booking email address when the restaurant enables booking emails. These relate to the booking and are not newsletters. Disabling the setting stops all four types.
- Restaurant notifications
- New bookings, confirmations, changes and cancellations can be sent to the restaurant’s selected notification address. The separate allergy field is excluded.
- Review request
- At most one email after a completed visit, only if the restaurant enables the feature and the guest actively selects it. The choice is off by default. Unsubscribing in the email or on the preference page stops further review requests from that restaurant without stopping essential booking emails.
- Restaurant owner onboarding
- One setup email may be sent to the verified owner address when the restaurant is created. At most one follow-up about a day later is sent only if the restaurant still has no bookings and onboarding tips have not been disabled.
- Optional TableBooking newsletter
- Requires separate, active consent from the restaurant owner. We record the consent and its time; registering for the service is not newsletter consent. There is no automatic newsletter sequence. Consent can be withdrawn in email preferences or by unsubscribing.
- Account, security and invoices
- Email verification, password links, invitations and relevant account/security messages follow a specific action or operational need. Stripe sends payment and invoice messages for subscriptions. Optional unsubscribe choices do not stop these essential messages.
SMS is disabled. We do not sell allergy information or use it for newsletters, advertising or AI. Queuing an email does not guarantee delivery; unsubscribe choices, invalid addresses or provider suppressions may stop it.
4. Providers and recipients
This list separates core operations from providers used only when you choose a particular feature. A configured API key does not mean a provider receives all data.
Operations and essential services
- Ingstad Media AS — Application and PostgreSQL on our own infrastructure
- Accounts, bookings, contact details, settings and separately stored allergy information.
Self-hosted. Production does not use an external database provider. - Vercel — Public entry point and forwarding to the application
- Network requests, IP address and technical delivery data.
Global provider; traffic and support may involve countries outside the EEA. - Cloudflare — Secure connection, Turnstile bot protection and R2 backups
- Technical browser and network data. Backups contain encrypted database and configuration copies.
The R2 bucket is in the EU. Network and bot-protection services are global. - Resend — Email delivery
- Recipient, sender and message contents. The separate allergy field is excluded from booking emails.
Provider processing and support may take place outside the EEA. - PostHog (EU) — Pseudonymous restaurant-account statistics; web analytics only with consent
- Server events for restaurant creation, bookings (source and party-size bucket), subscriptions (plan) and support (category), with a keyed hash of the restaurant ID. Consented web analytics uses a random tab ID, paths, article slugs, coarse traffic sources and selected actions. No identifying guest data, field contents, recordings, raw referrers or full URLs are sent.
EU endpoint. Geolocation is disabled in the request. The provider may process the IP address as part of network traffic. - Sentry — Technical error monitoring
- Limited error events and technical metadata. Allergy fields, notes and private booking keys are filtered before sending.
Transfers outside the EEA may occur; see section 5.
When you choose a feature or give consent
- Google — When you choose Google sign-in
- Name, email address and profile picture. Guests do not need a Google account to book.
Global service; transfers outside the EEA may occur. - Google Business Profile — When the restaurant connects its Google Business Profile in Settings
- The connection token, chosen location and the restaurant’s booking link. We read the name, address, phone, opening hours and Place ID from the profile.
Global service; transfers outside the EEA may occur. - Stripe — When the restaurant owner orders a paid subscription
- Customer and invoice information and payment references. Card details are handled by Stripe.
Global service; transfers outside the EEA may occur. - OpenRouter and Google — When a restaurant requests AI analysis of an uploaded floor plan
- The images and instructions submitted for analysis. AI functions do not read the separate allergy table.
Processing may occur outside the EEA. API requests require zero retention by the model provider and disallow collection for training; this is a routing requirement, not a promise about all provider metadata. - Retell AI — When a user chooses to start optional voice booking
- Audio, spoken content and necessary booking details may be processed. Do not provide health information during the call; use the booking’s separate allergy field.
Processing may occur outside the EEA. The production agent is configured for basic attributes only, without recordings or transcript logs, with a seven-day retention period. Users can choose the standard booking form instead.
Not enabled
Twilio SMS is disabled. Direct Meta/Facebook/Instagram integration is not enabled. These services are not active recipients of booking data in those flows. New or replacement subprocessors are notified under the data processing agreement before planned use.
5. Transfers outside the EEA
Some providers are established in, or may provide support from, countries outside the EEA. When this happens, we use a valid transfer mechanism, normally the European Commission’s Standard Contractual Clauses (SCCs), and assess any necessary supplementary safeguards. We do not promise EU-only storage where this has not been technically and contractually confirmed.
6. Retention and deletion
- Account and customer data: for the duration of the customer relationship
- Reservation history: retained for the restaurant while the customer relationship continues or until the restaurant requests deletion. The restaurant must determine a necessary retention period and request deletion when the history is no longer needed. Ordinary bookings are not automatically deleted based on age.
- Customer data after termination: normally deleted or anonymised within 30 days, with backups expiring later according to the provider’s documented rotation
- Google Business Profile connection: the encrypted token and chosen location are deleted immediately on disconnect, and otherwise together with the restaurant account when it is deleted
- Security and audit logs: according to documented security need. Ordinary audit logs follow the restaurant account and are removed on account deletion; separate deletion records may be kept to demonstrate compliance with obligations. Some technical logs have shorter, automatic retention periods.
- Accounting and payment records: for as long as bookkeeping or other applicable law requires
Data subject to legal retention requirements is kept separately and is not used for ordinary product purposes.
How to request deletion
Restaurant owners can open Settings → Account and request deletion of the restaurant account. The dashboard explains the data affected, any retention exceptions and the 30-day cancellation period. An active subscription must be ended before deletion can be completed.
For deletion of your sign-in identity or other personal data, email post@ingstadmedia.no. Deleting a restaurant does not automatically delete a sign-in identity that may be used for other restaurants. Guests should first contact the restaurant where they made their booking.
7. Your rights
Depending on the circumstances, you can request access, rectification, deletion, restriction or portability, or object to processing. You can withdraw consent without affecting the lawfulness of earlier processing.
Guests should first contact the restaurant where they booked. We assist the restaurant under the data processing agreement. Account users can contact us directly or use the export and deletion functions available in the dashboard.
You can lodge a complaint with the Norwegian Data Protection Authority.
8. Security
We use encrypted transport, access controls for each restaurant, role-based permissions, session controls, logging, backups and ongoing technical testing. Administrative and financially sensitive functions require strong authentication and recent verification before access. No internet-connected service can be guaranteed to be risk-free.
Breaches are handled under the GDPR. When TableBooking is a data processor, we notify the relevant restaurant without undue delay. When Ingstad Media AS is the data controller, we assess notification to the Norwegian Data Protection Authority and affected individuals within the applicable deadlines.
9. Automated decisions
TableBooking does not use automated decisions that produce legal effects or similarly significantly affect individuals.
10. Changes
Material changes are notified before they take effect. The date at the top shows when this policy was last updated.