Skip to main content

Legal (beta)

Data Processing Addendum.

Last updated: November 8, 2026

  1. What this is

    This Data Processing Addendum is an annex to the Vero Terms and part of them. It applies whenever a customer uses Vero to measure its own sites. The customer is the controller of its visitors’ data and Vero is its processor under Article 28 of the GDPR (Regulation 2016/679). Vero is run by the operator named in the legal notice.

    TermsLegal notice

  2. Subject matter and duration

    Vero processes visitor data to run the analytics, revenue attribution, alerts and, unless the customer turns AI off, the AI features the customer uses. Processing lasts as long as the customer has an account, and ends with the deletion set out below.

  3. Data and data subjects

    Data subjects are the visitors to the customer’s sites and, when the customer connects revenue, its buyers. Vero processes the page path, referrer, UTM parameters, screen-width bucket, browser language, timezone, country, browser and operating-system names, the data of the optional modules the customer turns on, the custom events the customer sends with their properties, and the payment metadata the customer’s provider sends (amount, currency, provider event id, an opaque customer id and the session). Nothing stored identifies a person. The IP is used only in memory, to derive the country and to compute a hash with a daily salt, and is never stored. The customer must not send special-category data, names or email addresses in custom events.

    Every field the tracker sends

  4. Instructions

    Vero processes the data only on the customer’s documented instructions: the Terms, this addendum and the settings the customer chooses in the dashboard. If EU or Member State law requires other processing, Vero tells the customer first, unless that law forbids it. If Vero believes an instruction breaks data protection law, it tells the customer.

  5. Confidentiality

    Everyone at Vero who can access the data is bound to confidentiality. For support, staff can open a customer’s dashboard in a read-only session that expires after 30 minutes and is recorded in an audit log. To run the service, an internal console shows staff account-level totals, never pages, sources or countries.

  6. Security

    Vero keeps the measures described on the security page, among them: the IP is never stored, storage is a single database in the EU, passwords and API keys are stored only as hashes, webhook payloads are signature-verified, outbound requests are guarded against SSRF, and every request is checked against the customer’s organization before it is answered.

    Security

  7. Subprocessors

    The customer authorizes the subprocessors listed on the subprocessors page. Vero binds each one to data protection obligations no weaker than these and stays responsible for them. Before adding or replacing one, Vero updates that page and emails account owners, so the customer can object. If an objection cannot be resolved, the customer can close its account.

    Subprocessors

  8. International transfers

    All data is stored in a single database in Ireland (EU). Processing is global: the tracker endpoint and the API run at the Cloudflare edge location nearest to each request, and stats responses are cached there. While AI is on for the customer’s workspace, aggregated figures are sent to Google’s Gemini API, which may process them outside the EU; no single visit and no IP is sent. Transfers outside the EEA rely on Standard Contractual Clauses or an equivalent safeguard.

  9. Assistance

    Vero helps the customer answer requests from data subjects and meet its duties on security, impact assessments and prior consultation, as far as the nature of the processing allows. The customer can export and delete its data from the dashboard; for anything else it can email hello@getvero.dev. Because nothing stored identifies a person, a request about one visitor usually cannot be matched to any record.

  10. Personal data breaches

    Vero tells the customer without undue delay after becoming aware of a breach that affects its data, by email to the account owners. The notice says what happened, which data and roughly how many records are involved, the likely consequences and what Vero has done about it. Vero adds what it learns as it learns it.

  11. Deletion at the end

    Until it deletes its data, the customer can export its events and revenue as CSV, up to 50,000 rows per export. When the customer deletes a site, Vero deletes that site’s events, revenue, settings and lifetime totals. Deleting the account deletes the data it holds. Events older than the plan’s retention are deleted automatically. Copies of deleted data remain in the nightly backups until those backups expire, at most 30 days later, and are not restored except to recover from an incident.

  12. Audits and information

    Vero makes available the information needed to show it meets Article 28: this addendum, the security, subprocessors and transparency pages, and written answers to the customer’s questions at hello@getvero.dev. Vero allows audits by the customer or an auditor it mandates, on reasonable notice and without access to other customers’ data.

  13. Precedence

    If this addendum and the Terms disagree on the processing of personal data, this addendum applies. Spanish law governs both.