Privacy Policy

NvisionData is operated by Nvision Data Solutions SRL, a company registered in Romania (registration ID nvision-data-solutions-srl-zy). For any privacy-related question you can reach us at privacy@nvisiondata.com.

This policy applies to nvisiondata.com, analytics.nvisiondata.com, and any subdomain we operate. It does not apply to websites that happen to use NvisionData as their analytics provider — those sites have their own privacy policies and are responsible for them.

Privacy law (GDPR, the UK GDPR, similar regimes) distinguishes between the controller of personal data — the party that decides what to collect and why — and the processor that handles it on the controller's behalf. NvisionData operates in both roles depending on the data:

• Processor for the analytics events your customers send through us. The customer running the website or app is the controller. They decide what to track, what consent to ask for, and what retention to apply. We process those events on their instructions.
• Controller for the data we collect about our own customers — your name, email, billing details, support conversations, and the analytics we run on our marketing site (nvisiondata.com) using our own product.

The rest of this policy covers our role as a controller. For the processor side — how we handle events on a customer's behalf — see our Data Processing Agreement.

We collect three categories of data, and only what we actually use.

1. Account data. When you create a NvisionData account we store your email address, your display name (if you provide one), and the workspace and property identifiers tied to your account. We use OAuth (Google) or passwordless magic links — we do not store passwords.

2. Billing data. Paid customers go through Stripe. Stripe holds the card number, expiry, and billing address; we receive a Stripe customer ID, the last four digits of the card, the billing email, and invoice metadata. Card numbers never touch our servers.

3. Product-usage events. When you use the console (analytics.nvisiondata.com) we record minimal telemetry — page views, property switches, errors, response timing — using NvisionData itself, with the same consent-aware pipeline our customers use. We do not record session replays, mouse movements, scroll heatmaps, or anything similar.

4. Support conversations. Email threads with our support team are stored in our email provider for as long as we need to keep the conversation useful.

Each category above maps to a narrow purpose:

• Account data — to authenticate you, scope your access to the right workspaces, and send you operational email (security alerts, billing receipts, occasional product updates).
• Billing data — to process subscriptions, calculate event-volume overage, send invoices, and meet our tax-reporting obligations.
• Product-usage events — to understand which parts of the console get used, debug errors, and prioritize what we build next. We do not use this data for advertising or sell it to third parties.
• Support conversations — to answer your question and to learn from recurring issues so we can fix them at the root.

For users in the European Economic Area, the United Kingdom, and Switzerland, we rely on two legal bases under the GDPR:

• Performance of a contract — to provide the service you signed up for. This covers account data and billing data.
• Legitimate interest — for product telemetry, security monitoring, fraud prevention, and to improve the service. We've weighed this against your privacy expectations and limited what we collect accordingly.

Where we ask for consent (for example, to send you marketing email), we record the consent and you can withdraw it at any time without affecting your access to the service.

The marketing site (nvisiondata.com) uses no third-party tracking scripts and no advertising cookies. The console (analytics.nvisiondata.com) uses a single first-party authentication cookie required for you to stay signed in, and a short-lived CSRF token. Neither is shared with third parties.

We do not use cross-site tracking, browser fingerprinting, or device-graph services. If a future feature would change this, we'll update this section and notify customers before it ships.

Retention windows depend on the dataset. The defaults below match our pricing tiers; on paid tiers customers can extend raw-event retention indefinitely (they pay the storage cost).

• Free tier raw events — 14 days. Aggregated counts kept indefinitely.
• Pro and Scale tier raw events — 36 months by default; extendable.
• Self-host — operator's choice. We don't hold the data.
• Identity vault — 13 months rolling unless consent extends, then up to 36 months.
• Account and billing records — kept for the life of your account, plus up to 7 years afterwards where required for tax and accounting law.
• Backups — encrypted, rotated on a 30-day cycle.

If you're an EEA, UK, or Swiss resident — and in many other jurisdictions with equivalent rights — you can ask us to:

• Access the data we hold about you.
• Correct anything inaccurate.
• Delete your account and the data tied to it.
• Export your data in a machine-readable format.
• Restrict or object to specific processing.
• Withdraw consent for anything you previously opted into.

The fastest path is the in-product DSAR flow at /settings/dsar. If you can't reach the console for any reason, email privacy@nvisiondata.com and we'll handle it manually within 30 days.

If you're a visitor of a site that uses NvisionData (rather than a NvisionData customer), please contact that site's operator first — they are the controller of their analytics data and we can only act on their instructions.

We use a small number of vendors to operate the service. The current list — names, role, region — lives at /legal/sub-processors and is updated whenever a vendor is added or removed.

NvisionData Cloud runs in the European Union by default — Hetzner Frankfurt for collectors and workers, ClickHouse Cloud EU for the event store, Vercel EU for the console. Personal data of EU residents stays in the EU.

Three vendors we depend on (Stripe, Sentry, Cloudflare) are headquartered in the United States and may process limited operational data — billing records, error reports, edge traffic metadata — outside the EU. For those flows we rely on the European Commission Standard Contractual Clauses and the additional safeguards each vendor publishes.

We're currently working through SOC 2 Type I — Security, Availability, and Confidentiality. Auditor engagement is planned for Q3 2026; we'll publish the report here once it's complete. We do not claim SOC 2, ISO 27001, or HIPAA today.

What is in place:

• TLS 1.3 in transit; AES-256 encryption at rest for all customer data.
• Passwordless authentication (Google OAuth and magic links) — no password store.
• Per-tenant access controls and row-level isolation in our metadata database.
• Identifiers used for ad-platform activation are stored as salted hashes in an identity vault separate from the event store, so a single read in one system cannot reconstruct the full subject profile.
• Secrets stored in Doppler. Time-bound, scoped credentials for every production system.
• Regular dependency updates and an internal security review before each release.

If you find a security issue, please email security@nvisiondata.com. We respond within two business days.

NvisionData is not designed for children. We do not knowingly collect data from people under 16. If you believe a child has provided us data, contact privacy@nvisiondata.com and we'll delete it.

When we change this policy we update the “Last updated” date at the top. For changes that meaningfully affect what we collect or how we use it, we'll also email customers and post a note on /changelog at least 14 days before the change takes effect.

For privacy questions: privacy@nvisiondata.com.

For everything else legal: legal@nvisiondata.com.

Postal: Nvision Data Solutions SRL, Romania. Registration ID nvision-data-solutions-srl-zy.