Legal

Privacy policy

What we collect, what we don't, and where the data lives.

This is not legal advice. It describes what the product actually does and can be used as a starting point, but assessing your obligations is your counsel's job. The technical claims are documented in detail in the privacy documentation.

The short answer

Vitrus sets no cookies, mints no persistent identifier and stores no personal data about your visitors. The visitor id is a one-way hash that changes every day.

Visitor data (people who visit your site)

What we collect

Page path, page title, referrer and UTM parameters
Browser, operating system, device type, screen size, language
Country — only from your proxy's header (Cloudflare and similar)
Core Web Vitals (LCP, INP, CLS, FCP, TTFB) from real visits
JavaScript error messages, file and line — never stack traces
Custom events you define, and their properties
Derived visitor and session digests

What we never collect

Cookies and localStorage — not used at all
IP addresses — never stored; only an input to a one-way hash
Values typed into forms — only the field name is sent
Password and hidden fields — never observed
Session recordings and heatmaps — the product does not do this
Person or company identification — out of scope

How the visitor id is built

hash(secret_salt + day + site + ip_prefix + browser)

The salt rotates daily, so the same visitor hashes to a different value tomorrow. Retroactive identity stitching is not possible. IPv6 addresses are reduced to their /64 prefix — that identifies a network, not a device.

Strict privacy mode

Each site can be switched to strict mode, which drops country, screen size, referrer query strings and cross-day identity entirely, and refuses any Do Not Track override. It is enforced on the server, so the browser script cannot bypass it.

Do Not Track

If the browser sends DNT, nothing is collected by default. A site owner can disable that with data-do-not-track="false", in which case the responsibility is theirs — except in strict mode, where the override is refused.

Account data (Vitrus users)

Email address and, if you gave one, your name
Your provider user id, if you signed in with Google or GitHub
Session records (login time, browser)
Billing status — card details never reach us, they stay with the payment provider

Where the data lives

In the cloud version, data is held on our servers in Germany/Finland (Hetzner). If you run it yourself, the data is yours and nothing is sent to us.

Third parties

Who	For what	What they see
Cloudflare	CDN and TLS	Request metadata
Paddle	Payments and invoicing	Payment details (never stored by us)
Resend	Digest email	Recipient address and summary content
LLM provider	Only if you enable one	An aggregated evidence bundle — never raw visitor data

Your rights and retention

To delete your account and data, write to us; we action requests within 30 days. Retention length depends on your plan (pricing).