TrademarkTrademark

Privacy Policy

Last updated: 2026-10-31
This 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 Aveiro: 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

Who we are

Dopler is the brand under which Tóth Lóránt e.v. builds and runs Once UI, Stack, Chirio, Aveiro, Tavilio, Frametic and related services. Tóth Lóránt e.v. is a sole proprietorship (egyéni vállalkozó) registered in Hungary, and it is the data controller for the personal data described here, except where this policy says a customer is the controller instead.
  • 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

Your account. When you sign up for a Dopler service, buy a plan or write to us, we decide what is collected and why. For that data we are the controller. Data you collect through our services. Some services let you collect data about other people: visitors to a site you publish, subscribers to your newsletter, guests who book a table at your venue. For that data you are the controller and we are your processor. We store and move it on your instructions, only to provide the service, and never for our own purposes. You are responsible for telling those people what you do with their data, in your own privacy notice. Our terms of use set out the processing terms that apply between us.

What we never do

  • 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.

Providers we use

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, public feedback boards and, on the services whose Part 2 says so, cookieless page analytics. 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. Some services also use Chirio's own analytics; Part 2 says which. It counts page views and a few product events, such as a finished sign-up, without cookies and without storing anything on your device. Chirio never stores your IP address: it becomes a visitor code that changes every day and differs from site to site, so we cannot identify you or follow you from one day to the next. Only the page's path and the domain of the page that sent you are kept. Raw events are deleted after 30 days; only daily totals are kept. If your browser sends Global Privacy Control, Chirio counts nothing. 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

Some Dopler services let you connect an AI assistant, such as ChatGPT or Claude, through sign-in from the assistant or with an API key or token you create. The assistant then calls the service's tools on your behalf, limited to what you allowed.
  • 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.

Cookies

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.

International transfers

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.

How long we keep data

  • 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.

Your rights

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.

Children

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.

Security

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.

Changes

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.

Part 2: Aveiro

Aveiro is a platform for building websites, growing an audience, sending email campaigns, publishing to social media and viewing analytics, at aveiro.app.

Two roles worth knowing

When you have an Aveiro account, we decide why and how your account data is used, so we are the controller for it. When someone visits a site you built on Aveiro, or subscribes to your newsletter through an Aveiro form, you decide why their data is collected: you are the controller for that visitor or subscriber data and we are your processor. You must give your visitors and subscribers your own privacy notice.

What we collect

Account and profile: email address and password (or sign-in with Google or GitHub); display name, username, bio and profile photo; organization name, membership and role; invite codes used during the closed beta; notification preferences. If you join the waitlist, we collect your email (and optional name) through the same signup forms we offer on published sites, tagged for the waitlist segment. Billing: if you subscribe, Stripe processes payment; we store your Stripe customer ID and subscription status, never your full card number. Your content and product use: sites, pages, media and settings you create; email subscribers, segments, campaigns and delivery statistics you manage; sender domains and DNS records you connect; your own email provider credentials (BYOK) if your plan includes it, stored encrypted; version history and organization activity. AI features: when you use AI in the editor or campaign tools, we send your prompts and the context you include (such as page content or attachments) to AI model providers through the Vercel AI Gateway so the model can respond. AI use is metered against your plan credits. Technical logs and security: server logs, request metadata and rate-limiting data, including IP addresses.

AI apps and MCP connections

You can connect an AI app such as ChatGPT or Claude to Aveiro, either by signing in through the app (OAuth) or with an API token you create. The app then calls Aveiro's tools on your behalf, limited to the organization, sites and permissions (scopes) you grant. What we receive from the AI app: the instructions and content it sends to a tool, such as page text, captions, image prompts, URLs to capture and campaign drafts, plus the sign-in or API token that proves the connection is yours. We use them only to carry out that tool call. Failed sign-ins are logged with an error code, never with the token. What the tools return to the AI app, and therefore to its provider, only for the organization and sites the connection can reach:
  • Connection: the connection's name, its permission scopes and the IDs of the sites it can access.
  • Sites: site names, IDs, subdomains and URLs, layout and navigation settings, interface text, languages, and publish and coming-soon status.
  • Pages and collections: IDs, paths, titles, the page content and metadata you wrote, language and translation links, draft and published status, last-edited times, and links to open the page in the editor.
  • Media: file names, URLs (including short-lived signed preview links), sizes, dimensions and upload dates; for screenshots and website videos, the page URL captured, status, any capture warnings and credits used.
  • Social posts: captions, per-platform text and titles, first comments, target account IDs, media attached, proposed and scheduled times, approval time and status, the review timeline (comments, and whether each came from a person, an AI agent or the system, but not which person), published post links and platform post IDs, publish errors, and engagement numbers per post (such as views, likes and comments).
  • Connected social accounts: the account's Aveiro ID, platform, public handle (username), connection status and date.
  • Newsletters: campaign names, subjects, preview text, status, scheduled and sent times, sender name, sender email address, reply-to address, the sender postal contact and footer you set, and the email content; campaign analytics only as totals and rates (sends, opens, clicks, top clicked links, unsubscribe counts and reasons).
  • Credits: the credit cost or balance of actions that spend credits.
What the tools never return: your or your teammates' user IDs, email addresses, passwords or profile data; who created a token or approved a post; your subscribers' or recipients' email addresses or any per-subscriber data; social platform user IDs; IP addresses or device data; internal organization or vendor IDs; and debugging details such as error traces. When something fails on our side, the app gets an error code and a generic message. Personal data can still appear inside content you or your team wrote, for example a name in a page or a caption. That content is returned as written, because the tool needs it to do what you asked. Once a tool returns data to an AI app, the app's provider (for example OpenAI for ChatGPT, Anthropic for Claude) handles it as an independent controller under its own terms and privacy policy, not as our processor. You can disconnect an app at any time in Account settings → Security → Connected AI apps, or by revoking its API token.

Analytics on published sites

Sites you publish can include Aveiro's cookieless analytics. The script stores nothing on and reads nothing from the visitor's device: no cookies, no localStorage or sessionStorage, no fingerprinting. For visitors to those sites we may collect the page path, referrer domain and event type; browser, operating system and device type (from the user agent); a hashed visitor identifier made from IP address, user agent and date, which rotates daily (raw IP addresses are not stored in analytics records); an optional country derived from the IP at the time of the event; and a random session identifier that exists only in page memory. This rests on legitimate interest (Article 6(1)(f) GDPR): aggregate usage statistics for the site owner. Visitors whose browser sends a Global Privacy Control signal are excluded entirely, and anyone can object by contacting us or the site owner. We filter common bots.

Email sending and tracking

When you send campaigns through Aveiro, we process recipient email addresses and message content to deliver mail. Open tracking may use a small pixel and click tracking may rewrite links; you control both when sending. The IP address of the opening or clicking device is used only to record the event and is stored hashed (salted SHA-256), never raw. Delivery, bounce and complaint events from our email provider are recorded; a hard bounce or spam complaint suppresses that recipient from future campaigns. From these events we may compute per-subscriber engagement (open rate, click rate and a status such as engaged, active, dormant or cold). This is profiling that helps you segment your audience; it is not used for automated decisions with legal or similarly significant effects. If location insights are on, we derive an approximate city and country from the opening or clicking device's IP and store only the last-seen city and country, never the raw IP. Recipients can unsubscribe through our unsubscribe page and may object to engagement profiling. Because you are the controller for your subscribers, your own privacy notice must cover this tracking, profiling and approximate-location processing, name a legal basis for it, and honour your subscribers' right to object.

Social publishing

If you connect a social account, the posts you approve are published to Instagram, Threads, X or LinkedIn through Chirio, which receives the post content, media URLs and first comment you approve, plus the connected-account identifiers needed to publish them. The platforms receive your content as independent controllers under their own terms. Access tokens are held by Chirio, not by Aveiro; disconnecting an account in Aveiro revokes them. Content already published stays on the platform until you delete it there.

Providers

Vercel (hosting, custom domains and the AI Gateway), Supabase, Stripe, Resend and Chirio, as described in Part 1, plus:
  • Upstash: rate limiting.
  • Google and GitHub: sign-in, only if you choose it.
  • AI model providers, through the Vercel AI Gateway: responses for AI features you use.
  • Your own email provider (BYOK): if you connect one, it receives what is needed to send your campaigns.

Cookies

  • Supabase sign-in cookies: keep you signed in, for the session or as Supabase sets.
  • invite_code (httpOnly): attributes an invite at signup, up to 60 days.
  • aff (httpOnly): attributes an affiliate referral, up to 60 days. Not used for advertising.
  • Cookie choices: remembers what you picked in Cookie settings.
Sign-in buttons for Google and GitHub may set cookies on their own domains only after you click them.

Your data

  • Export: Settings → Security → Export personal data (a JSON file of your account, profile, memberships, invites and affiliate data).
  • Delete: Settings → Security → Delete account.
When you delete your account, we soft-delete its records at once and then remove or anonymise them on our deletion schedule, except what we must keep for legal or security reasons. Exports cover your personal data, not organization-owned content such as sites, subscriber lists and campaigns; organization admins manage those. Analytics and email logs may be kept for the reporting periods set in the product.

Contact

support@dopler.app · Tóth Lóránt e.v., 1134 Budapest, Kassák Lajos utca 67/B, Hungary
TrademarkTrademark
Crea tu presencia en línea con Aveiro sin pelearte con el diseño ni el código.
Built onOnce UI
© Aveiro. Todos los derechos reservados.
TrademarkTrademarkUn producto de Dopler