Legal
Our processing roles and the technical measures behind them.
| Scenario | Controller | Processor |
|---|---|---|
| Cloud version | You (the site owner) | Vitrus |
| Self-hosted | You | None — the data never reaches us |
| Your Vitrus account | Vitrus | — |
Consent obligations usually turn on access to terminal equipment (writing cookies or localStorage) and on processing personal data. Vitrus:
What that means in your specific context is a question for your counsel. We only document what the product does.
If you switch session replay on, you record individual visits. Even with every text node and
input value masked and sensitive fields never captured, a recording of one person's visit is more
than aggregate analytics, and your counsel may well conclude that it needs consent or at least a
line in your privacy notice. That is why replay is off by default, why a page has to opt in with
data-replay, and why Do Not Track and Global Privacy Control always stop
it. Retention is yours to set (1–90 days) and every recording can be deleted individually.
If your counsel wants the smallest possible footprint, strict mode drops country, screen size, referrer query strings and cross-day identity, and makes Do Not Track non-overridable. It is enforced server-side, so it holds even if the browser script is modified.
identify) are hashed one-way; the raw value
never touches diskFor your visitors: because there is no persistent identifier and no stored IP, locating a single visitor retroactively is technically impossible — which means less that we cannot honour a deletion request, and more that the data was never linkable to a person. For your own account data, write to us.