Privacy Policy

DineMio, formerly TableLite, is a restaurant reservation platform based in the Netherlands. We provide restaurant dashboards, embeddable booking widgets, reservation emails, guest CRM tools, setup flows, checkout, and related support and sales communications.

This policy applies to DineMio websites, apps, booking widgets, emails, and related services. If you have questions or want to make a privacy request, contact us at [email protected].

For personal data about restaurant account users, buyers, referral partners, website visitors, support contacts, and sales contacts, the business operating DineMio is the controller. For guest and reservation data entered by or collected for a restaurant, the restaurant is usually the controller and DineMio acts as its service provider or processor.

The data we collect depends on how you use DineMio.

• Account data: name, email address, preferred language, password authentication data, Google sign-in identifiers when you use Google login, role, invitation status, account status, and session information.
• Restaurant data: restaurant name, address, city, country, timezone, phone, email, website, social links, logo, cover images, opening hours, tables, seating areas, floor-plan layouts, widget settings, plans, and team membership information.
• Guest and reservation data: guest name, salutation, email, phone number, party size, reservation date and time, status, cancellation reason, special requests, notes, tags, visit counts, no-show counts, guest events, and reservation activity history.
• Payment and checkout data: purchaser name, email, restaurant name, selected plan, quoted amount, currency, checkout status, Stripe customer, checkout, and payment identifiers. DineMio does not store full card numbers.
• Communications data: messages you send us, restaurant invitations, password reset and magic-link emails, reservation emails, sales emails, replies, unsubscribe or suppression records, and email delivery, bounce, or complaint events.
• Business outreach and historical campaign data: public business contact details, website, location, booking software signals, outreach notes and status, and opt-out records. Historical campaigns also recorded link clicks, referrer, user agent, and hashed IP address. Contact and suppression records may be maintained in a private prospect spreadsheet to prevent unwanted follow-up.
• Technical and security data: IP address, user agent, device and browser data, request metadata, timestamps, authentication events, rate-limit records, diagnostic logs, error reports, and sampled performance diagnostics. Sentry session replay is not enabled.

Special requests and restaurant notes can contain sensitive details, such as allergies, dietary needs, accessibility needs, or other health-related information. Please only provide or enter sensitive information that is needed to manage the reservation or restaurant service. Where this reveals health or other specially protected data, the restaurant must have both a lawful basis and an applicable condition for processing that sensitive data, such as valid explicit consent where appropriate. Accepting our terms or analytics is not consent to process health information.

We receive data from you, the restaurant and its authorized team, guests using the booking tools, and providers such as Google and Stripe when you use their services. Business leads may come from publicly available business websites or directories. Account contact details and the fields marked as required in a booking or checkout flow are needed to complete that service; optional profile information and analytics consent are not required.

For referral partners, we store application details, country, accepted program terms, referral assignments, commission calculations, payee details and payout references. Your chosen partner name is displayed on your public referral link. Referred restaurants can see who introduced them; partners see their referred restaurant names and related subscription earnings, but never restaurant guest or reservation data. We use these records to administer the program, prevent abuse, resolve disputes and meet accounting obligations. A referral can be attached when you continue through a partner invitation and create or use an eligible restaurant account, or when we correct a missed introduction at your request. We do not set an affiliate tracking cookie. Optional analytics still follows your consent choice. PayPal or an agreed bank processes manual payouts, and Cal.com processes call bookings when you choose to book a call with us.

• Provide, secure, maintain, and improve DineMio.
• Create and manage accounts, sessions, teams, roles, and invitations.
• Let restaurants configure availability, tables, widgets, and booking flows.
• Create, update, confirm, remind, cancel, and manage reservations.
• Send transactional emails, support replies, product notices, and sales communications.
• Process purchases, refunds, invoices, plan access, and payment records.
• Detect abuse, enforce limits, prevent fraud, investigate incidents, and debug errors.
• Retain historical campaign records for reference and honor recorded opt-outs.
• Comply with legal, tax, accounting, security, and regulatory obligations.

For processing where DineMio acts as the controller, our purposes and legal bases under the GDPR are:

• Accounts, subscriptions and partner rewards: we use account, billing and referral information to enter into and perform a contract with you, including steps you request before joining. When you act for a business that is our customer, we use your professional contact details in our legitimate interest in administering that business relationship.
• Security and support: we use technical records and communications in our legitimate interests in preventing fraud and abuse, diagnosing errors, answering requests and maintaining a reliable service. We balance those interests against your rights. Approximate country lookup from your IP address runs on our server to help choose a language or pricing currency; it does not obtain your precise location.
• Optional product analytics: consent, covering the limited website and product events described in section 6. You can refuse or withdraw without losing access.
• Marketing and opt-outs: consent where required, or legitimate interests where applicable law permits relevant business communications without prior consent. We keep limited suppression records to respect objections and avoid contacting people who opted out. A legitimate interest does not override consent requirements for electronic marketing.
• Accounting and legal matters: legal obligations for required tax and accounting records and binding legal requests; legitimate interests for establishing, exercising or defending legal claims.

For guest and reservation data processed on a restaurant's behalf, the restaurant determines the purpose and lawful basis. We process that data to provide its booking and management services under its instructions, rather than treating our contract with the restaurant as the guest's consent.

We share personal data only as needed to operate DineMio, comply with law, or protect rights and security. Current categories include:

• Hosting, database, infrastructure, backup, and deployment providers.
• Cloudflare R2 for uploaded logos, cover images, floor-plan images, and offsite database backups.
• Stripe for checkout, payment processing, refunds, payment records, and fraud controls.
• Email providers, including SMTP and Amazon SES, for transactional email and delivery events, and Mailforge for the separately managed business-outreach mailbox.
• Sentry for error reports and sampled performance diagnostics, with personal-data filtering. Session replay is disabled.
• PostHog Cloud EU for optional, consent-based product analytics as described in section 6.
• Google services for Google sign-in and maps links, and Google Sheets for private business-prospect and opt-out records.
• OpenAI for optional AI floor-plan image analysis when a restaurant user chooses to use that feature.
• Telegram for internal signup, referral and billing alerts. These can include the restaurant name and account email, and the referring partner's name and email where applicable. They are not public posts.
• PayPal or an agreed bank for partner payouts, and Cal.com if you choose to book a call.
• Internal operations and notification tools, professional advisers, auditors, authorities, or parties involved in a business transaction where needed.

Restaurants and their authorized team members can access guest and reservation data for their own restaurant. Guests should contact the restaurant directly for restaurant-specific booking, hospitality, or data questions; we can help route requests where appropriate.

DineMio uses cookies and similar technologies for authentication, security, language preferences, and interface preferences. For example, we use session cookies to keep users signed in, a locale cookie to remember language choice, and a sidebar preference cookie in the dashboard. The retired outbound campaign no longer creates or reads attribution cookies.

We do not currently use third-party advertising cookies on DineMio. With your consent, we use PostHog Cloud EU to measure visits to DineMio’s own website, selected dashboard actions, setup progress, trial starts and subscription payments. We use a random identifier linked to your account after sign-in, not your name or email. We do not send guest names, reservation details, feedback messages, or full URLs with query parameters to analytics. IP-based analytics enrichment is disabled. Like any direct network connection, your browser's connection to PostHog exposes its IP address to the receiving service; our analytics configuration is set to discard client IP addresses rather than use them in analytics. Session recording and automatic click capture are disabled.

Analytics stays off until you choose “Allow analytics”. Choosing “Essential only” does not affect the service. Use the “Privacy choices” control on our website or dashboard to change or withdraw your choice. We remember it for 180 days using a preference cookie and, when signed in, an account preference. Withdrawal stops future collection; contact us if you also want previously collected data deleted.

Our embedded restaurant booking widget and guest reservation management pages do not load PostHog or show this analytics banner. Restaurant booking and operational statistics are calculated from reservation records needed to provide the service.

We do not use advertising trackers to follow you across other websites. Our optional analytics follows your explicit Privacy choices selection; the app does not separately interpret the legacy browser “Do Not Track” signal. If you follow an external link to a payment, social, map or appointment service, that service's own privacy and cookie practices apply.

If a restaurant user uploads a floor-plan image for AI analysis, the image is sent to OpenAI to detect table positions and layout data. Use of this feature is optional. Do not upload floor plans or images containing information you are not permitted to process or share for this purpose.

DineMio is operated from the Netherlands, but some providers may process data in other countries, including outside the European Economic Area. An EU hosting region does not by itself rule out access from another country. Transfers subject to the GDPR require an applicable adequacy decision or other lawful safeguards, such as the European Commission's standard contractual clauses and any necessary supplementary measures. Contact us for details of the destinations and safeguards applicable to your data, or to request a copy of the relevant safeguards.

We keep personal data for as long as needed for the purposes described in this policy, including to provide DineMio, comply with legal and accounting obligations, resolve disputes, enforce agreements, secure the service, and maintain backups.

• Account and restaurant data is generally kept while the account or restaurant workspace remains active. Cancelling billing or reaching the end of a trial does not itself delete the workspace. Contact us to request account closure, export or deletion; separate legal retention duties may still apply.
• Guest and reservation data is kept for the restaurant workspace unless deleted, exported, or otherwise handled under the restaurant's instructions or legal obligations.
• Payment records, invoices, and related checkout records are kept as needed for accounting, tax, chargeback, and fraud purposes.
• Sales lead, outreach, suppression, unsubscribe, and attribution data is kept while relevant for sales operations, compliance, opt-out handling, and suppression hygiene.
• Our routine cleanup removes expired login sessions and verification records after expiry, stale rate-limit records after 7 days, and expired invitations after 30 days. Cleanup runs periodically rather than at the exact expiry time.
• Routine maintenance-job history is retained for 30 days for successful runs and 365 days for failed runs. These periods do not describe every infrastructure or provider log.
• For processed email-delivery events created from September 11, 2026, detailed provider payloads are reduced after 14 days and processed event records are removed after 180 days. Earlier campaign archives and unprocessed events are outside that routine cleanup and require separate review.
• Backup rotation normally keeps local hourly recovery points for 24 hours and offsite recovery points for up to 56 days. Protected recovery snapshots and interrupted backup verification can extend this; deleting a live record does not instantly remove every backup copy.

When a fixed period does not apply, retention depends on whether the workspace or support request is still open, the restaurant's instructions, an unresolved payment or legal claim, and applicable accounting duties. The 180-day analytics preference expiry is not an automatic deletion deadline for earlier analytics events. You can ask us for the retention information relevant to your records or request deletion using the contact details below.

Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or receive a copy of your personal data. You may also have the right to withdraw consent and to complain to a data protection authority.

We do not sell personal information. We also do not share personal information for cross-context behavioral advertising as those concepts are commonly used in US state privacy laws. If that changes, we will update this policy and provide required choices.

To make a request, contact [email protected]. If your request concerns a reservation or guest profile held for a restaurant, we may need to forward the request to that restaurant or ask you to contact it directly.

For requests under the GDPR, we normally respond within one month. If complexity or the number of requests requires an extension of up to two further months, we explain it within the first month. We may request proportionate information to verify your identity. You may object to direct marketing at any time; withdrawal of consent does not affect processing that was lawful before withdrawal.

You can complain to the Dutch Autoriteit Persoonsgegevens or your competent local supervisory authority. You do not need to contact us first. Optional floor-plan analysis detects layout objects; it is not a decision about an individual's legal rights or eligibility for a service.

US privacy rights depend on the applicable state law and our role in processing your information. Contact us to request access, correction or deletion, or to raise an objection. We assess and respond under the law that applies; the GDPR response period above does not replace a different mandatory local deadline.

We use technical and organizational measures designed to protect personal data, including authentication, role-based access, rate limiting, secure transport, provider controls, monitoring, and access restrictions. No system is perfectly secure, so you should use strong passwords, limit team access, and keep account credentials private.

DineMio is not directed to children. Restaurant guests may include children in party sizes or child-seat requests, but children should not create DineMio accounts.

We may update this policy as DineMio changes. The updated version will be posted at /privacy. If changes are material, we will take reasonable steps to notify affected users.