Privacy and GDPR

Without cookies (the default)

By default Nvivio sets no cookie and stores nothing on your visitor’s device. A visitor is recognised with a code that changes every day: a hash of a daily key, your site, the IP address and the browser. The daily key is deleted after 26 hours, so after midnight a visitor can no longer be linked to yesterday.

You do not need a cookie banner for Nvivio in this mode, and nobody is followed across days.

The trade-off: a visitor is only recognised within the same day, so “returning visitor” is not reliable in this mode.

This mode is on for every new site. You find it in Settings › Privacy › Without cookies, and the mode is shown next to the site name (“Privacy mode”).

With one cookie (optional)

Want to recognise visitors across days and months, for example in a web shop, a SaaS product or a site with a login? Switch to Settings › Privacy › With one cookie.

• Nvivio then uses one first-party cookie, _nvivio_sid, valid for about 13 months.
• The script only sets it after you call nvivio.consent(), for example when your cookie banner gets consent. Until then the visitor is counted as in privacy mode, so no visit is lost.
• The cookie is set on your main domain, so a visit across your subdomains stays one visit.
• With data-consent="none" on the script tag, the script sets the cookie right away (only where you do not need consent).
• You need a cookie banner for EU visitors in this mode.
• Not in the free plan; available from Starter (see Plans).

You can switch at any time: existing data stays, new visits follow the new choice. API: PATCH /v1/sites/{site} with {"mode": "cookie"}.

What Nvivio never stores

• IP addresses. The IP address is only used in memory, for the daily code and to check excluded addresses. It never reaches the queue or the database.
• The full user agent. Only the browser, the operating system and the kind of device are kept.
• Small company networks. In privacy mode, the name of the network is only kept when it is a large provider or relay, such as Proximus, Telenet or iCloud Private Relay. “Proximus” says nothing about a person; the name of a small company network would. (In cookie mode the network name is kept.)

Addresses are cleaned

Of every URL, Nvivio only keeps known parameters: utm_source, utm_medium, utm_campaign, utm_term, utm_content, ref, source, q, s, search, query, page and lang. An email address in a path becomes :email; long codes and UUIDs become :id. Other parameters are dropped, so a password-reset link or an email address in a URL never ends up in your statistics.

Where your data lives

• The database and sign-in run at Supabase in Frankfurt (eu-central-1).
• The queue and the site settings run on Cloudflare under EU jurisdiction. The dashboard runs next to the database in Frankfurt.
• Query results are not cached, and no logs are kept.
• The database cannot be reached directly through REST or GraphQL.
• The MCP server for AI assistants also runs in Frankfurt and has no database of its own. What a connected assistant asks for does go to the company behind that assistant.

Good to know: a request first arrives at the Cloudflare data centre closest to the visitor. For visitors in the EU, that is in the EU.

Icons without a third party

The icons next to sources (Google, LinkedIn) and next to your own sites are fetched by Nvivio itself and kept for a week. Your browser never asks an external favicon service or the referring site, so nobody outside Nvivio sees which sources send you visitors.

How long data is kept

Visits, events and bot details are kept according to your plan: Free 30 days, Starter 90, Pro 180, Agency 365. Older data is deleted every night. Settings › Data retention shows your period. You can also delete all data of a site, or the site itself, in the Danger zone.