How Voris handles data. All of it, in plain language.

The list that matters most is the empty one.

In its default configuration, Voris uses no cookies and touches no browser storage of any kind. It does not fingerprint devices. It does not track people across sites. It stores no names, no emails, no identifiers of any person. IP addresses are used for a moment to derive a country and are never written to disk, never logged, never stored. There is no visitor profile in our systems because nothing exists to build one from.

This is enforced in the code and verified by automated tests on every release, not promised in a policy and hoped for in practice.

Counts of what happened. Not records of who.

Voris records that a page was viewed, where the visit came from at the level of a source, the country it resolved to, the type of device and browser, and any custom events you define, such as a goal completing. Aggregated, this becomes your dashboard: trends, totals, breakdowns. It does not, and cannot, become a dossier on a person.

No banner needed. Here is why, and here is the receipt.

Consent banners exist to ask permission for two things: storing information on a visitor’s device and processing their personal data. Voris does neither in its default configuration, so there is nothing to ask permission for. We are commissioning a written legal opinion on exactly this posture from a leading EU privacy law firm, and we will publish the full document on this page, not a summary, not selected quotes, the document.

EU infrastructure, end to end.

Your analytics data is processed and stored in EU data centers in Germany, and the path from the script on your site to your dashboard stays in the EU. A few vetted providers we rely on, for transactional email and the AI digest, operate under EU Standard Contractual Clauses, and the data they ever see is minimal and, for analytics, typically not personal. The full list is in our privacy policy. For European organizations this removes a familiar headache; for everyone else it is a clean answer to “where is my data,” which is rarer than it should be.

The AI analyst reads statistics, not people.

The weekly digest is generated from aggregated query results about your site: totals, trends, significant changes. It never reads raw event content, and your data is never used to train AI models, ours or anyone’s. Citation tracking works on public AI answers to questions you chose, and touches your visitor data only at the aggregate join to your own traffic.

Easy to audit, easy to leave.

A DPA is available for customers who want one on file. Data exports to CSV are on every plan. Deleting a site deletes its data, on a schedule we document. We think lock-in is a confession that a product cannot retain customers on merit, so we declined to build any.