Skip to main content

Legal (beta)

Privacy Policy.

Last updated: November 8, 2026

  1. Scope

    Vero is in a private beta before its public launch. This policy covers the waitlist, beta accounts (those of the people we invite and of the teammates they invite) the visitor analytics the tracker collects on beta customers’ sites and the analytics of getvero.dev’s own visitors. It will be expanded before Vero launches.

  2. Data controller

    Vicente Manuel Torres Aragón, an individual in Spain. Contact: hello@getvero.dev. I am the data controller under the EU GDPR (Regulation 2016/679) and Spain’s LOPDGDD 3/2018 for the waitlist, for account data and for the analytics of getvero.dev’s own visitors. For the visitor analytics collected on a customer’s website, the customer is the controller and Vero is the processor, under the Data Processing Addendum.

    Data Processing Addendum

  3. Waitlist

    Your email address, the language you read the site in, a "source" tag with the page you submitted from and, if you fill them in, your site’s address and a note on what you want to measure. We do not ask for your name and never store your IP address. We use this to pick beta accounts by hand, to invite you if we pick yours and to send you a small number of launch-related emails. Legal basis: your consent (Art. 6.1.a GDPR), given by submitting the form. You can withdraw it at any time by replying with "unsubscribe" or emailing hello@getvero.dev. We keep it until you unsubscribe, or up to 12 months after launch if you never engage. When you use the form, Cloudflare Turnstile checks that you are not a bot: it receives your IP address and browser signals to do that, and we keep none of it. Cloudflare handles that data under its Turnstile Privacy Addendum (https://www.cloudflare.com/turnstile-privacy-policy/).

  4. Beta accounts: what we collect

    If you create an account, we process your email address; a display name, taken from your email address until you change it; a hashed password (never the plaintext) or, if you sign in with Google or GitHub (both optional: email and password still work), the name, the email address the provider has verified, the profile picture link and the provider’s account id, which recognises you next time. Vero asks Google only for openid, email and profile, and GitHub only for read:user and user:email: no repositories, contacts or calendar. The tokens the provider issues are used once to complete the sign-in and are not kept. The provider learns that you signed in to Vero, as with any sign-in through it, and receives none of your analytics data; your organization’s name, its members and the email addresses you invite to your team; the sites you add and their settings; which setup steps you have completed, such as verifying your email or installing the tracker; your email preferences; and anything you send through the in-app feedback form, with the page, browser, screen size and recent errors it attaches. No payment data is collected: nothing is charged during the beta.

  5. Beta accounts: cookies and sessions

    The dashboard sets a session cookie that keeps you signed in and is removed when you sign out, and vero_lang, which remembers your language for a year. Connecting Search Console also sets a single-use security cookie that expires after 10 minutes. None is used for tracking or advertising. Display preferences (theme, density and language) are also kept in your browser’s local storage. A signed-in session stores neither your IP address nor your browser details. If you turn on “Exclude visits from this network” for a site, Vero stores a keyed hash of the IP address you are using, never the address, so that site stops recording your visits; turning it off deletes the hash.

  6. Beta accounts: why we process it

    To create and secure your account, run your workspace, give you support, and send the email the service depends on: verification, password resets, team invitations, a welcome message, setup reminders, usage notices, anomaly alerts, and the weekly digest, which you can switch off. Legal basis: performing our agreement with you (Art. 6.1.b GDPR). Vero sends account holders no marketing email.

  7. Visitor analytics (cookie-free)

    A beta account can install the Vero tracker on its own website, and Vero measures getvero.dev the same way. The tracker records page path, referrer, UTM parameters, screen-width bucket (mapped to Mobile/Tablet/Desktop), browser language, timezone, country, and the names of the browser, the operating system and, when the page opens inside an app such as Instagram, that app (derived from the user agent, which is not stored). With the optional modules a site turns on, it also records time on page, scroll depth, the URLs of outbound links and downloaded files, Core Web Vitals and the A/B variant a session saw, and it records the custom events a site sends, with their properties. Country is derived from the IP at the edge; the raw IP is never stored. There are no cookies, no cross-site identifiers, and no device fingerprinting. To count unique visitors we compute a salted SHA-256 hash of (IP + user-agent + day) that rotates every 24 hours and cannot be reversed to a person. On getvero.dev, where Vero is the controller, the legal basis is our legitimate interest in knowing how the site is used (Art. 6.1.f GDPR); the data identifies no one.

  8. Revenue data

    When a beta customer connects revenue, we process the payment metadata their provider sends us (amount, currency, provider event id, an opaque customer id, and the associated session) to attribute revenue to a traffic source. We do not receive or store card numbers, names, or billing addresses.

  9. AI features

    AI is part of the beta: AI insights, Ask Vero, watches written in plain language, the likely cause of a revenue drop and the commentary in the weekly digest. To answer, Vero sends Google’s Gemini API the site’s domain and aggregated figures (totals, top pages, sources, campaigns, revenue by source and the deploys you recorded), plus the text of your question or watch. It sends no single visit, no IP address and no visitor hash. Vero uses Gemini on a paid Google Cloud account; on that paid tier, Google does not use prompts or responses to improve its products. The account owner or an admin can turn all AI off on the Team page, and while it is off no model is called and nothing goes to Google. Legal basis: performing our agreement with you (Art. 6.1.b GDPR).

  10. How long we keep it

    Analytics events are kept 2 years on a beta account, then deleted by an automated job. When the beta ends, an account that does not choose a paid plan moves to Hobby, which keeps 30 days, and older events are deleted. Account data is kept while the account exists and deleted when you delete the account. You can export it, or delete the account, from Settings at any time.

  11. Site totals kept past retention

    For the achievements screen, each site keeps a running record that retention does not delete: its total pageviews, the countries it has had visitors from, and its net and highest revenue per currency. These are totals about the site, nothing about any visitor. They are not part of the CSV or account export, and they are deleted when the site is deleted.

  12. Staff access

    To give support, such as looking into a problem you reported, Vero staff can open a customer’s dashboard in a read-only session that cannot change anything in the account, expires after 30 minutes and is recorded in an audit log. Separately, to run the service, staff see account-level figures for every account in an internal console: account and member emails and names, site domains, the plan, and daily event, visitor and revenue totals. Detailed analytics (pages, sources, countries) are visible only in the support session.

  13. Where data is stored

    Everything above is stored in a single Turso (SQLite) primary database in Ireland (aws-eu-west-1), with no replicas: storage is EU-only. Processing is not. The site, the tracker endpoint and the API run on Cloudflare Workers at the edge location nearest to each visitor, and stats responses are cached at the edge location that served them, so derived aggregates sit outside the EU when the request comes from outside the EU. Waitlist emails are never cached. Transfers outside the EEA rely on Standard Contractual Clauses or an equivalent safeguard.

  14. Subprocessors

    During the beta: Cloudflare (edge hosting, transactional email, the waitlist bot check and the database backup), Turso (database), GitHub (runs the nightly backup job) and Google (the Gemini API, for the AI features, unless the workspace turns AI off). Nothing is charged, so Vero uses no payment provider of its own. The full list, with what each processes, is on the subprocessors page. We do not share, sell, or rent your data.

    SubprocessorsData Processing Addendum

  15. Demo page

    The /demo page renders the dashboard with mock data. It does not collect, store, or transmit any visitor data. No cookies, no fingerprinting, no analytics calls.

  16. Your rights

    You can access, correct, export, or delete your data at any time, and object to or restrict its processing. Manage your account data yourself from Settings; for anything else, email hello@getvero.dev (we respond within 30 days). You may also lodge a complaint with the Spanish AEPD (aepd.es).

  17. Changes

    We will update this policy before Vero launches. Material changes will be communicated by email to waitlist subscribers and account holders.