Install & operate

Privacy & data

What is collected, what isn't, and how the visitor id is built.

The visitor id#

hash(secret_salt + day + site + ip_prefix + browser)
  • The id changes when the day changes. There is no persistent identifier.
  • The IP is never stored — it is only an input, and the hash is one-way.
  • IPv6 is reduced to its /64 prefix. Privacy extensions rotate the low 64 bits several times a day; hashing the full address would mint a new visitor on every rotation and inflate unique counts. A /64 also identifies a network rather than a device — less identifying.

Your users: counted, never identified#

When your app calls vitrus.identify(user.id), sensitive data stays out of our cloud by construction, not by policy:

  • The raw id never leaves the browser. The script sends sha256(site + "|" + id); without WebCrypto it sends no id at all.
  • Hashed again on arrival with a secret that never leaves the server; only that is stored, per site — one person in two of your apps cannot be joined.
  • Email, phone, name, address, password, token, IP, date of birth, card, IBAN and national-id fields are dropped, in the browser and again at ingest, along with any value shaped like an email or an international phone number. The event is kept and the removal is counted on the Lifecycle page's privacy check.
  • The Users page shows a made-up name (“Amber Falcon · 3f9a2c”) derived from the hash. There is no email or name in the database to show.

What we never collect#

  • Your users' emails, names, phone numbers or raw user ids — see above
  • Cookies and localStorage — not used at all
  • Values typed into form fields — only the field name
  • Password and hidden fields — never observed
  • Stack traces — error message, file and line only
  • Session recordings — unless a site turns session replay on, and then text and inputs are masked and password and card fields are never captured
  • Anything extra for heatmaps — they are drawn from session recordings a site already keeps
  • Visitor de-anonymisation ("which company visited my site") — out of scope

A known limitation#

A dual-stack browser may reach the same site over IPv4 on one request and IPv6 on another. Those two addresses have nothing in common and cannot be joined without a cookie — that visitor is counted twice. It is rare in practice (the OS sticks to one family for the life of a connection) but it is not zero, and we would rather write it down than pretend.

Strict mode#

For a smaller footprint still, see privacy mode.

Something wrong or missing on this page? Open an issue or ask in Discussions.