Privacy policy
Last updated 2026-10-31This policy explains how Dopler handles personal data across its services. It has two parts. Part 1 applies to every Dopler service. Part 2, below it on the same page, sets out what is specific to Tavilio: what it collects, the providers it uses, its cookies and how long it keeps things. Where Part 2 says something more specific than Part 1, Part 2 applies.
Part 1: All Dopler services
- Registered address: 1134 Budapest, Kassák Lajos utca 67/B, Hungary
- Registration number: 52097030
- Tax number: 68682398-1-41 (EU VAT HU68682398)
- Contact for anything in this policy: support@dopler.app
We have not appointed a data protection officer, because the law does not require one for a business of our size and kind. Write to the address above and the person who runs the service will answer.
Two roles: ours and yours
- We do not sell personal data, rent it out or trade it.
- We do not use behavioural advertising, advertising pixels or cross-site tracking.
- We do not use your content, or data you collect through our services, to train AI models.
- We do not knowingly collect special-category data (health, beliefs, biometrics and the like). Do not put it in free-text fields.
Where the GDPR applies, we rely on these legal bases (Article 6(1) GDPR):
- Contract (b): to create your account, provide the service you signed up for, take payment and support you.
- Legal obligation (c): to keep invoices and accounting records, and to answer lawful requests from authorities.
- Legitimate interest (f): to keep the services secure and available (logs, rate limits, abuse prevention, error reports), to count page views in aggregate, and to improve the product. We balance these interests against your rights, and you can object to them (see "Your rights").
- Consent (a): for newsletters and other optional email you sign up for, and for anything else where we ask first. You can withdraw consent at any time, for example with the unsubscribe link in every newsletter; withdrawal does not affect what happened before it.
We use a small number of providers, each for a specific job. They process personal data only on our instructions, under a data processing agreement. Part 2 lists which of them a given service uses and names any provider used by that service alone.
- Vercel: hosting, content delivery, request logs and cookieless page-view analytics.
- Supabase: database, sign-in and file storage.
- Stripe: payments, subscriptions, invoices and tax.
- Resend: sending account and transactional email.
- Sentry: error reports, so we can find and fix bugs.
- Aveiro (a Dopler service): sending the newsletters you subscribe to.
- Chirio (a Dopler service): the feedback widget and public feedback boards. When you post feedback from inside a service, the service passes your user ID, name, email address and plan to Chirio, so we can answer you.
Stripe is an independent controller for the card and payment data it holds. Card numbers are entered on Stripe's own forms and never reach our servers; we keep only Stripe's customer and subscription identifiers, your plan and your invoices. If you never buy anything, nothing is sent to Stripe.
Analytics. Vercel Web Analytics counts page views without cookies and without identifying you or following you across sites. We do not use Google Analytics or any analytics that profiles individual people.
Error reports. When something breaks, Sentry receives the error, the page or request it happened on and technical details of the browser or server. Reports are scrubbed of passwords and tokens and kept for up to 90 days.
Sign-in providers. If you choose to sign in with Google or GitHub, that provider tells us your email address, name and account ID. It acts under its own privacy policy.
We may also disclose data when the law requires it, or to protect someone's rights or safety, and we will tell you when we are allowed to.
AI assistants you connect
- What we receive from the assistant: the instructions and content it sends to a tool, and the sign-in or key that proves the connection is yours. We use them only to carry out that call.
- What the tools return is listed in Part 2 for each service. Tools never return passwords, keys or tokens, and they leave out other people's contact details unless Part 2 says otherwise.
- The assistant's provider (for example OpenAI for ChatGPT, Anthropic for Claude) receives what a tool returns because you chose to connect it. It handles that data as an independent controller under its own terms and privacy policy, not as our processor.
You can disconnect an assistant, or revoke its key, at any time in the service's settings.
We set only cookies that a service needs to work: keeping you signed in, remembering your language or theme, and protecting forms against abuse. These are strictly necessary, so they do not need consent. We set no advertising or analytics cookies. Part 2 lists any other cookie a service sets.
Some providers process data outside the European Economic Area, mostly in the United States. Where they do, the transfer relies on the EU-US Data Privacy Framework for providers certified under it, or on the European Commission's standard contractual clauses.
- Account data: while your account is open. When you delete your account, we delete or anonymise its data within 30 days, unless Part 2 says otherwise.
- Content you create: until you delete it or your account. Part 2 lists exceptions.
- Invoices and payment records: eight years, as the Hungarian Accounting Act requires (Act C of 2000, section 169).
- Request logs and error reports: up to 90 days.
- Backups: a rolling window of up to 30 days, after which deleted data is gone from them too.
- Newsletter subscriptions: until you unsubscribe; we keep a record of the unsubscribe so we do not email you again.
Under the GDPR you can ask us to:
- give you a copy of the personal data we hold about you (access),
- correct it (rectification),
- delete it (erasure),
- limit what we do with it (restriction),
- give it to you, or to another provider, in a portable format (portability),
- stop processing it on the basis of our legitimate interest (objection),
- and you can withdraw consent at any time.
Write to support@dopler.app from the email address on your account. We answer within one month, and tell you if we need longer (up to two more months for complex requests). Many services also let you export or delete your data yourself; Part 2 says where.
If your data was collected by one of our customers, such as a site owner or a venue, that customer is the controller. Ask them first; if you write to us, we will pass the request on and help them answer.
Complaints. If you think we have handled your data wrongly, please tell us first so we can put it right. You also have the right to complain to a supervisory authority, either where you live or work, or in Hungary to the Nemzeti Adatvédelmi és Információszabadság Hatóság (NAIH): 1055 Budapest, Falk Miksa utca 9-11; postal address 1363 Budapest, Pf. 9.; ugyfelszolgalat@naih.hu; naih.hu. You can also go to court.
Dopler services are not meant for children under 16, and we do not knowingly collect their data. If you think a child has given us personal data, write to us and we will delete it.
Data is encrypted in transit and at rest with our providers. Access is limited to the people who run the service, keys and tokens are stored hashed or encrypted, and we keep the software up to date. No system is perfectly secure; if a breach puts your data at risk, we will tell you and the NAIH as the GDPR requires.
When we change this policy in a way that matters, we update the date at the top and, for significant changes, tell account holders by email or in the product before the change takes effect.
Tavilio is reservation software for restaurants and cafés: bookings, a floor plan, a menu and a small website for each venue.
Your venue's account is ours to look after: for it we are the controller.
Your guests' reservations belong to the venue. The venue decides that it takes bookings, what it asks for and how long it keeps the answers, so the venue is the controller and we are its processor. We do not use guests' data for our own purposes, and we do not use it to advertise or to train anything.
About you and your team: your name, email address and the role you were given in a venue. Sign-in is handled by our authentication provider; we hold the email address and, if you set one, a password hash — never the password itself.
About your venue: its name, address, phone number, public email, opening hours, links, the images and logos you upload, your floor plan, your menu with its photos, prices and allergens, and the pages of your website.
About a booking: the guest's name, email address, phone number, party size, the date and time, the tables assigned, and any note the guest wrote. A note is free text, so it is worth telling guests not to put anything sensitive in it.
About your subscription: which plan you are on, when it renews, and the identifiers our payment provider gives us. We never see or store card numbers — those go straight to Stripe and stay there.
Technical records: the ordinary request logs our hosting provider keeps, which include IP addresses, and the records of transactional emails we sent.
AI assistants connected to your venue
- Your venue: its name, address, phone number, public email, links, languages, plan and its limits, opening hours, closed days and booking rules
- Bookings and event signups: the guest's name, party size, date and time, status, the guest's note, your team's internal note, answers to your signup or booking form, a decline reason, and whether the guest or your team cancelled
- One booking, when the assistant asks for it by id: also the guest's email address and phone number, and which emails were sent about it, when, and whether they were delivered
- Feedback surveys: how many were sent, and each response with the guest's name, rating and answers
- Events, the menu, your website's pages and style, and availability
- Your team's profiles: name, role, bio, photo, specialties, website and Instagram, and whether each is shown on your site
- Statistics: booking, cover and signup counts
- Agent activity: each change an assistant made or tried, as logged above
What the tools never return: your or your team's user IDs, sign-in email addresses or passwords; card or payment details and payment provider identifiers; the addresses an email was sent to; our internal identifiers; IP addresses; and technical details of errors on our side. A list of bookings or signups does not include guests' email addresses or phone numbers.
Once a tool answers, the assistant's provider (for example OpenAI for ChatGPT, Anthropic for Claude) holds that answer under its own terms and privacy policy, as an independent controller, not as our processor. Guests' data shared with an assistant is shared on the venue's instruction, so a venue that connects one should say so in its own privacy notice to guests.
Vercel, Supabase, Stripe and Resend, as described in Part 1. Resend sends booking confirmations and other transactional email; for a guest that is on the venue's instruction. Chirio runs the feedback button in the admin; with your post it also receives your profile photo, if you have set one.
Only the cookies in Part 1: sign-in and your chosen language. Venue sites count page views with cookieless Vercel Web Analytics, with the address cleaned before it leaves the page.
Reservations stay while they are useful to the venue and are removed when the venue removes them or closes its account. Venue content (the menu, the floor plan, the website) stays until you delete it. When a venue is deleted, its data goes with it: its content, uploaded files and bookings are removed, not hidden.
The venue you booked with is the controller of your booking. Ask the venue first; if you ask us, we pass the request on and help it answer.
Write to us with anything about this document, or to exercise any of the rights above.
Tóth Lóránt e.v.
1134 Budapest, Kassák Lajos utca 67/B, Hungary
Registration number: 52097030
Tax number: 68682398-1-41 (EU VAT HU68682398)
Email: support@dopler.app
Governing law: Hungary 
