Install & operate
FAQ
Short answers.
Do you store my users' personal data?
No. Vitrus is built so that it never has it. The user id your app passes to
vitrus.identify() is hashed in the browser before it is sent and hashed again with a
server secret before it is stored; email, phone, name, address, password, token, IP and similar properties are dropped
in the browser and again at ingest, and the removal is counted. What is stored is a hash per site, so one person in two
of your apps cannot be joined. The Users page shows each person under a made-up name.
Details: User identity and Privacy.
Can I see each user without storing who they are?
Yes. Each signed-in user is a row — status, actions, active days, visits, joined, last active, and opened, their actions by day and recent visits — under a stable made-up name like “Amber Falcon · 3f9a2c”. If you need to know who it is, your own database already does; Vitrus deliberately does not.
Can I ask an AI about all my apps?
Yes, over MCP: get_portfolio covers every site you can read, get_lifecycle
one site. Counts only, each with its query. See MCP.
Can I really drop the consent banner?
For most sites, yes: we set no cookies, mint no persistent identifier and store no personal data. The final call belongs to your counsel; we document the technical facts.
Does my data go to an LLM provider?
Not unless you enable one. No model is on by default. If you turn one on you have two options: Ollama on your own server (nothing leaves the box) or your own API key. In both cases what reaches the model is an aggregated evidence bundle, not raw visitor data.
Can it replace GA4?
For most sites, yes. Not for ad-platform attribution (Google/Meta Ads ROAS) — we deliberately do not build that.
Is there session replay?
Yes, since September 2026 — and it is off by default. For a long time we said we would never build it: recording a visitor's screen means recording the ID number they typed into your form, and if masking misses one field you created your customer's compliance problem. So it ships the other way round from most tools: every text node and every input value is masked unless you unmask an element on purpose, password and card fields are never captured at all, Do Not Track is always honoured, and a site has to opt in twice. The aggregate signals — field-level form abandonment, rage clicks, scroll depth — still answer most of the same questions without recording anyone. See session replay.
What happens when I hit the quota?
You are not cut off immediately: data keeps flowing inside a 20% grace band with a dashboard warning. Once that is exhausted new events are rejected — and the rejected count is shown, so you can see what you lost.
Can I export my data?
Self-hosted, the database file is yours — query it directly. In the cloud,
/api/stats returns the evidence bundle as JSON and the MCP server exposes
the same data to an agent. Bulk CSV export does not exist yet.
Can an AI agent query my analytics?
Yes, over MCP. It is read-only, and every answer includes the query that produced it so the agent can cite evidence rather than assert a number.