Privacy notice for website enquiries

This is a short notice for the website forms. It is consistent with, and part of, our full Privacy Policy, which also covers customer account users, billing contacts and the DataNivra service. If the two ever differ, the Privacy Policy applies.

What we collect

• The details you type: name, work email, company, optional job title, topic, optional preferred demo date and optional message.
• For a feature request: the area, a short title, the problem it would solve, optional urgency and team size, the page you sent it from and, only if you want a reply, your email. In the console we also record your organization, your user account and your plan, so we can follow up in context.
• Your consent to be contacted, and the version of this notice you agreed to.
• A pseudonymous key derived from your network address with a secret keyed hash. We use it to limit repeated submissions and to detect abuse. We do not store your network address itself.

Please do not put customer, patient, financial, personal or production data in these forms. Feature requests are checked automatically: a request whose text looks like real data (for example email addresses, card or account numbers, connection strings, secrets or pasted records) is refused before anything is stored or sent, and we ask you to describe the need without real data.

Why we use it

Only to answer your enquiry — for example to arrange a demo, discuss pricing or reply to your question — to review feature requests when we decide what to build next, and to protect the forms from spam. We do not sell it and we do not add you to marketing lists from these forms. A feature request is product feedback: sending one is not a promise that we will build it.

Who receives it

The DataNivra team responsible for responding to enquiries. When you submit a form, an internal email notification with your details is sent to that team. Notification destinations are part of our secured configuration. Feature requests are sent to our general mailbox (hello@datanivra.com); if you left an email, you receive one acknowledgement and replies come from that mailbox.

How long we keep it

Enquiry records are deleted automatically 365 days after submission; feature requests are deleted automatically 24 months after submission. If the conversation leads to a business relationship, the contact details it needs are kept in our customer records under the Privacy Policy, not in the enquiry record. We keep a tamper-evident log of events about each enquiry (for example “submitted”, “notification sent”, “deleted”); those log entries contain no name, email, company or message. Refused submissions (for example spam or missing consent) are not stored — only a log entry with a reason code is kept. The technical details of how enquiries are validated, stored and deleted are in the developer documentation on website lead data.

Your choices

You can ask us to access, correct or delete your enquiry or feature request at any time through the contact form or the email address shown there. Deletion removes the record and any pending notification.

Cookies and browser storage

The website uses three kinds of browser technology, described below: browser storage for features you use, optional analytics cookies that are set only after you allow analytics, and the technical requests any website needs. The website’s own code sets no cookies other than the optional analytics cookies. Its Content Security Policy lets the browser run scripts only from DataNivra’s own site and, when analytics is switched on for the website, from Google’s analytics loader, which our code requests only after you allow analytics.

Like any website, every page request reaches our hosting provider, which processes technical request data such as your IP address to deliver the site (see section 3.4 of the Privacy Policy). The narrated walkthroughs can use your browser’s built-in speech synthesis; depending on your browser, the browser vendor may process the narration text (website content, not your personal data) under its own terms.

Optional website analytics

DataNivra uses Google Analytics 4 (GA4) to understand how visitors interact with our public website and improve its content, documentation, and features.

Google Analytics is optional. We do not load the GA4 tracking script, set GA4 analytics cookies, or send GA4 measurement events unless you have provided the required consent.

If you allow analytics, we collect limited information about pages visited and selected website interactions, such as navigation, tutorial completion, feature exploration, and demo requests.

Google may also receive technical information associated with analytics requests, including browser and device characteristics, approximate geographic location, timestamps, and cookie identifiers.

We configure our implementation to minimize the information sent. We do not intentionally transmit form contents, email addresses, credentials, customer datasets, SQL queries, account identifiers, or other sensitive application information.

We do not use GA4 for advertising. Advertising-related consent remains denied, and Google signals and advertising personalization features are disabled.

Google Analytics may set first-party cookies, including _ga and _ga_*, after consent. These cookies help distinguish browser interactions and returning visits.

Our intended GA4 event-data retention setting is two months. Analytics cookies are configured to expire within approximately 13 months, subject to their actual configuration and browser behavior. Some aggregated reporting may remain available beyond the event-data retention period.

You can withdraw analytics consent at any time using the privacy preferences control on this page. Withdrawal stops subsequent optional analytics tracking and triggers deletion of applicable GA4 cookies that our website can access. Withdrawal does not automatically erase information already processed by Google.

Google receives technical request information when analytics is enabled. Google states that GA4 does not log or store IP addresses.

Where consent is required, we rely on your consent for this optional analytics processing.

Browser privacy signals

Global Privacy Control and Do Not Track are two different browser signals, and we treat them separately:

• Global Privacy Control. We treat a Global Privacy Control signal from your browser as a refusal of optional analytics.
• Do Not Track. Do Not Track is an older signal with no agreed meaning. We voluntarily honour it by keeping optional analytics off.

While your browser sends either signal, we do not show the analytics banner, we do not load GA4, a choice you stored earlier does not switch analytics back on, and GA4 cookies left from an earlier choice are deleted where our website can access them.

Privacy preferences

You can open this control at any time from the “Privacy preferences” link at the bottom of every page.

More information

The Privacy Policy explains who we are, the legal bases we rely on, our service providers, international transfers and all of your rights.