transparency
Exactly what we collect.
No dark patterns, no fine print. Here is every field the tracker sends, and everything it never touches.
- 12fields the tracker can send, all of them in the table below.
- 0cookies, and nothing written to the visitor’s device.
- 0IP addresses stored. They are used in memory and dropped.
- 1dayis how long a visitor hash lasts: its salt rotates daily, and visits are not linked across days.
What we collect
| Field | When it is sent |
|---|---|
| FieldPage URL and path | When it is sentAlways |
| FieldReferrer (where the visit came from) | When it is sentAlways |
| FieldUTM campaign parameters | When it is sentAlways |
| FieldCountry (derived at the edge, never from a stored IP) | When it is sentAlways |
| FieldScreen width, and the device bucket derived from it | When it is sentAlways |
| FieldBrowser language and time zone | When it is sentAlways |
| FieldBrowser and OS names, and the app when the page opens inside one (derived from the user agent, which is not stored) | When it is sentAlways |
| FieldScroll depth and active time on page | When it is sentWith its modulescroll + engagement |
| FieldThe outbound link URL or downloaded file name | When it is sentWith its moduleoutbound + downloads |
| FieldCustom events you send with vero.track(), and the A/B variant a session saw | When it is sentWhen you send itexperiments |
| FieldCore Web Vitals (LCP, INP, CLS, FCP, TTFB) | When it is sentWith its modulevitals |
| FieldThe session id of the visit, added to Stripe and Lemon Squeezy checkout links, so your payment provider’s webhook brings the sale back with its source | When it is sentWith its modulecheckout |
What we never touch
- Cookies or localStorage
- Your IP address (never stored)
- Your visitors’ names or email addresses
- The full user agent (never stored)
- Identifiers that link sites or outlast the day
- Precise location
Check it in your browser.
Open DevTools on any site that runs Vero. The requests to /api/collect carry only the fields above, and nothing is stored on the device.
What about the cookie banner?
Most analytics tools show a banner because they keep data in cookies on the visitor’s device. Vero’s tracker writes nothing to the device. It counts visitors with a SHA-256 hash of the IP, the user agent, the date and the site, salted with a server secret and computed at the edge. The hash is stored with each event; the IP never is. Because the date is part of the input, the hash changes every day and visits are not linked across days. Because the site is part of it too, the same person on two websites that use Vero gets two unrelated hashes. What that means for your site is your legal team’s call, and this page is the list they need to make it.