Skip to main content
Security

Secure by architecture.

The strongest privacy guarantee is not collecting the data in the first place. Here is exactly how Vero is built.

0
cookies, and nothing written to the visitor’s device.
1day
is how long a visitor hash lasts: its salt rotates daily, and visits are not linked across days.
EU
is where every event is stored: one database in Ireland (aws-eu-west-1). Compute and cache run at the edge.
30min
is the most a staff support session lasts: read-only and logged.

The dashboard and the website send HSTS with preload, getvero.dev email has DMARC set to reject, and the CSP reports its violations, stored by host and directive only.

1

Data protection

  • No cookies and no localStorage: nothing is written to the device.
  • IP addresses are never stored. Visitors are counted with a SHA-256 hash of the IP, user agent, date and site, salted with a server secret, so the hash changes every day and differs on every site.
  • No names, emails, or precise location are collected by the tracker.
  • Analytics events are retained 30 days on Hobby and 2 years on Pro, then deleted by an automated job.
  • Every event, session and revenue row is stored in a single Turso (libSQL) primary in Ireland (aws-eu-west-1), with no replicas: storage is EU-only. Compute is not: the API runs on Cloudflare Workers at the edge location nearest the visitor, and stats responses are cached there, so derived aggregates sit outside the EU for requests from outside the EU.
2

Ingestion & webhooks

  • Revenue ingestion authenticates with a per-site secret sent as a Bearer token, rotatable at any time.
  • Stripe, Lemon Squeezy and Paddle webhooks are verified by HMAC signature against a per-site secret, stored encrypted; unsigned or mismatched events are rejected. Stripe and Paddle signatures expire after 5 minutes, and Lemon Squeezy events older than 24 hours are refused, so a captured request cannot be replayed.
  • Ingestion is idempotent: duplicate events are ignored.
  • Outbound notification URLs are validated against SSRF (https-only, private ranges and metadata endpoints blocked).
3

Access control & isolation

  • Authorization runs before the handler, on every request: your access to the requested site is resolved against your organization, and a request for a site outside it is rejected. Vero staff are the exception: to run the service, an internal console shows them account-level figures for every account: 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 a support session, described under “Your account”.
  • Sites are addressed by rotatable tokens, not guessable identifiers.
  • API keys are stored hashed, gated to Pro plans, and read-only unless created with write access; the read API is Bearer-authenticated.
  • Every sensitive endpoint carries a per-minute rate limit. Authenticated and expensive routes are counted in a Durable Object, which serialises the count so the limit is exact wherever your requests land. High-volume public routes (the tracker script and event ingest) are counted by Cloudflare at the edge location that received the request, which adds no round trip and counts per location rather than globally. When the limit is keyed by address, the address is salted and hashed first and is never stored in the clear.
4

Your account

  • Two-step sign-in is optional and on every plan: a 6-digit code from your authenticator app and 10 backup codes that each work once. Turning it on or off asks for your password.
  • You can see your open sessions and close any of them from Account. Resetting your password closes all of them.
  • Sign-in and sign-up attempts are rate limited, to slow down anyone guessing passwords.
  • At sign-up, password reset and password change, Vero refuses passwords that have already appeared in a data breach. Only the first 5 characters of the password’s hash leave Vero to check, never the password. If that service does not answer, the password is accepted.
  • Vero staff need two-step sign-in to enter the internal console. Their support sessions are read-only, expire after 30 minutes and are recorded in an audit log.
  • Removing a member, their access to a site or an MCP connection takes effect within 10 seconds.
5

Your AI’s access (MCP)

  • The MCP server is read-only. Each connection reads the site you pick when you connect and, only if you tick the box, every other site you see. Each call checks, at that moment, that you still see the site and that its workspace is on Pro; lose the site you connected with and the whole connection ends.
  • Your AI client signs in with OAuth and PKCE, so there is no key to paste. The consent page lasts 10 minutes and works once; the access token lasts 1 hour and renews, and a connection unused for 90 days expires.
  • Revoke each connection from “Connect your AI”, and it stops working within 10 seconds.
6

Privacy posture

  • No cookies and nothing written to the visitor’s device. Nothing stored identifies anyone: the IP is used only in memory, to compute a hash with a daily salt, and is never stored. What that means for your site is your legal team’s call: /transparency lists every field the tracker sends.
  • Honors Do Not Track and Global Privacy Control.
  • One-click account data export (right of access) and account deletion (right to erasure).
  • A ready-to-paste privacy-policy snippet is generated for each site.
Found a vulnerability? Email security@getvero.dev.