Privacy Policy
Last updated: October 7, 2026This Privacy Policy explains what personal data Table QR LLC (“TableQR”, “we”, “us”) collects when you use TableQR, why we collect it, who we share it with, how long we keep it and what rights you have. It covers visitors to our website, people who use the dashboard as members of an organization, and guests who open a venue’s menu page. The rules for using the Service are in our Terms of Service.
In short: we collect what we need to run the Service, we host it in the European Union wherever we can, we do not sell personal data and we do not use it for our own advertising.
1. Who is responsible
Table QR LLC operates TableQR and is responsible (the “controller”) for the personal data of our account holders and website visitors.
Venues use TableQR to run their own menu pages. For data about their guests — orders, emailed receipts and visit statistics — the venue decides what is collected and why, and is the controller; we process that data on the venue’s behalf, as its service provider. Questions about how a venue uses guest data should go to the venue, and we will help it answer.
2. Data about account holders and team members
When you create an account, join an organization or use the dashboard, we process:
- Account details — your name, email address and password (stored only as a secure hash by our authentication provider), your language and theme preferences, and a profile photo if you upload one.
- Organizations and team — the organizations and locations you belong to and your roles there, and invitations you send or receive (the invitee’s email address, the organization’s name and the inviter’s name).
- Content you add — menus, products, prices, images and settings. This is mostly business information, but it can include personal data, such as a venue’s contact email or phone number.
- Sign-in sessions — the IP address and browser or device (user agent) of your active sessions, which you can see in your account settings, and your multi-factor authentication settings if you use them.
- Billing — your billing email address, your customer reference at Paddle, your subscription and payment history, and links to invoices and receipts. Card details are entered in Paddle’s checkout and never reach our servers.
- Messages — what you tell us when you contact support.
3. Signing in with Google or Apple
If you choose to sign in with Google, we ask Google only for the basic sign-in scopes: openid, email and profile. From your Google account we receive your name, your email address, a link to your profile picture and your Google account identifier. We use this data only to create your TableQR account and sign you in, to confirm your email address, and to show your name and picture in the dashboard.
- We do not access your Gmail, contacts, calendar, Drive or any other Google data.
- We do not sell Google user data or use it for advertising, and we share it only with the service providers that host our authentication and database, solely to run the Service.
- TableQR’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
You can remove TableQR’s access at any time in your Google Account settings. Deleting your TableQR account deletes the data we received from Google.
Sign in with Apple works the same way: we receive your name and your email address — or the private relay address Apple creates for you — and use them only for your account.
4. Technical and usage data
- Server logs — when your browser talks to our servers, we log the time, the address requested, the result, your IP address and your user agent. We use these logs to keep the Service secure, prevent abuse and fix problems.
- Traffic and performance measurement — our website, dashboard and menu pages use Vercel Web Analytics and Speed Insights to count page views and measure loading speed. They do not use cookies and give us aggregated figures, not profiles of individuals.
- Error reports — when something breaks, an error report with technical details (the page, the browser, what failed) may be sent to our error-monitoring provider.
Our website and dashboard do not use advertising cookies or advertising pixels.
5. Guests of venue menu pages
When you open a venue’s menu page — usually by scanning its QR code — we process the following on the venue’s behalf:
- Orders and requests — the name you enter (needed for pickup orders), your notes, your table, the menu language and what you ordered or asked for, so the venue can serve you. They stay in the venue’s order history while the venue’s organization exists on TableQR.
- Emailed receipts — if you ask for a receipt by email, we use your email address to send it and delete the address 30 days after the request.
- Data on your device — your cart, references to your recent orders and your language choice are kept in your browser so the page works when you come back, including offline.
- Visit statistics and venue marketing tools — see the next two sections.
You do not need an account to read a menu or to order.
7. Venue marketing integrations
A venue on an eligible plan can connect advertising and analytics tools to its menu pages: Meta Pixel, Google Analytics, Google Ads, TikTok Pixel, Snap Pixel, Pinterest Tag and Yandex Metrica. The venue chooses and controls these tools, and their providers receive data under their own privacy policies. The tools are told about page views, items viewed, cart and order events (including order value and currency), and that a search happened — never the search text.
- For venues in the EU, the EEA, the UK and Switzerland, and for any venue that chooses to ask everywhere, these tools load only after you agree in the consent banner on the menu page. Your choice is stored in your browser for about six months, separately for each venue, and you can change it at any time from the menu page.
- Elsewhere they may load without a banner, but if your browser sends a Global Privacy Control signal, advertising tools stay off.
9. Why we use personal data
Where data protection law such as the GDPR applies, we rely on these legal bases:
- Performing our contract with you — creating and securing accounts, hosting menus, passing orders to venues, billing through Paddle, and sending service emails such as sign-in links, invitations and receipts.
- Legitimate interests — keeping the Service secure and preventing abuse (logs, rate limiting, audit records), fixing errors, measuring and improving the Service in aggregate, and giving venues statistics about their menu pages. You can object to processing based on legitimate interests.
- Consent — venue marketing tools where a consent banner is shown. You can withdraw consent at any time.
- Legal obligations — keeping billing and accounting records and responding to lawful requests.
We do not sell personal data and do not use it for our own advertising. We do not make decisions about you based solely on automated processing that have legal or similarly significant effects.
11. International transfers
We host the Service mainly in the European Union. Some providers — such as Paddle, Google, Apple, Sentry and Vercel’s delivery network — may process data in other countries, including the United Kingdom and the United States. Where data protection law requires it, these transfers rely on adequacy decisions or on the Standard Contractual Clauses our providers offer.
12. How long we keep data
- Account data — while your account exists. When you delete your account, we delete your profile, your sign-in identities (including data received from Google or Apple), your profile photo, your memberships and invitations, and the organizations where you were the only member, together with their content.
- Organization content and orders — while the organization exists.
- Receipt email addresses — 30 days after the receipt was requested.
- Visit statistics — as described in “Visit statistics on menu pages”.
- Audit records — a log of who changed what in an organization, which refers to people by an internal identifier rather than by name or email. We keep it after an account is deleted, for security, fraud prevention and the defence of legal claims.
- Trial records — a note that a free trial was used, kept to prevent repeated trials.
- Billing records — invoices, payments, the billing email address and payment notifications from Paddle, for as long as tax and accounting law requires, including after an account is deleted.
- Server logs — for a limited period set by our hosting providers, after which they are deleted automatically.
- Backups — deleted data may remain in backups for a limited period until they are overwritten.
13. How we protect data
Data is encrypted in transit, and our hosting providers encrypt it at rest. Access inside the Service is limited by roles, and that limit is enforced by the database itself. Our staff access personal data only when they need to for support, security or running the Service: staff accounts require multi-factor authentication, revealing a customer’s contact details is logged, and acting inside a customer’s account requires a recorded support session.
No system is perfectly secure. If a personal data breach happens, we will notify you and the authorities where the law requires.
14. Your rights
Depending on where you live, you may have the right to access your personal data, correct it, delete it, restrict or object to its processing, receive it in a portable format, and withdraw any consent you gave. You can update your profile and delete your account yourself in your account settings. For anything else, write to support@table-qr.com. We will reply within one month and may first need to confirm your identity.
If your request concerns data a venue collected through its menu page, such as an order, we will forward it to the venue or help the venue respond, because the venue decides how that data is used. You also have the right to lodge a complaint with the data protection authority where you live.
15. Children
The Service is not directed at children, and we do not knowingly collect personal data from children under 16 for our own purposes. A venue’s menu page can be opened by anyone; if you believe a child has given us personal data, contact us and we will delete it.
16. Changes to this policy
We will update this policy as the Service changes. If a change is material, we will tell account holders by email or in the dashboard before it takes effect. The date at the top shows when the policy last changed.
17. Contact
Table QR LLC is responsible for the processing described in this policy, except where a venue is. For questions or requests about your personal data, write to support@table-qr.com.
This policy may be translated; if the versions differ, the English version prevails.