Draft — under legal review This text is a draft. A lawyer still reviews it; until then the terms in your quote or agreement apply.
cloud.novarint.com Privacy Statement
Last updated: 18 November 2026
Version 1.0 — draft, 18 November 2026
Draft, do not publish yet. This is a carefully prepared draft, not legal advice. A Dutch lawyer must review it before it is published. Points that still need a choice are marked
[TO DECIDE: …]; points still to be checked are marked[to verify: …]. This English text is a translation; if the two differ, the Dutch text prevails.
This statement explains which personal data NOVARINT B.V. processes for cloud.novarint.com, why, for how long, and what rights you have. We follow the General Data Protection Regulation (GDPR).
1. Who we are
NOVARINT B.V., Scholekster 5, 2201 XH Noordwijk, the Netherlands, Chamber of Commerce 42028869. For all privacy questions: hi@novarint.com or +31 6 25413594. We have no data protection officer; we are not required to have one. [to verify: whether a DPO is required given the nature and scale of the processing.]
2. Two roles: controller and processor
We are the controller for the data we process for ourselves: of visitors to our website and the Demo, of the people who register and sign in, of customers' contact persons, for invoices and payments, for support, and for the security of the service (such as sign-in attempts and technical logs).
We are a processor for everything a customer puts into novarint: the tables, records, files, screens, scripts, workflows and the questions to the assistant ("customer data"). The customer (the organisation using novarint) decides about those. We process them only on the customer's behalf, under the data processing agreement. Are you a person in a customer's data, or do you work in your employer's app? Then please contact that organisation first; we help it with your request.
We process the data of an account a customer creates for a colleague (name, e-mail address, role) to provide the service to the customer. For the security of the service itself (signing in, two-step verification, preventing abuse) and for the messages the service itself sends (such as a welcome link or a new password) we are responsible ourselves. [TO DECIDE: have the lawyer confirm this split.]
3. Which data, for what, on what basis and for how long
| Whom | Which data | For what | Legal basis (GDPR art. 6(1)) | How long |
|---|---|---|---|---|
| Visitors of the website and the Demo | IP address, time, page requested, browser details (in server logs) | Running and securing the website and Demo, countering abuse and attacks | Legitimate interest (f) | [TO DECIDE: for example 30 days] |
| People using a Demo | What you enter in the Demo (without an account) | Running the Demo | Legitimate interest (f) | Until the end of the Demo's lifetime, then deleted. If you register, it becomes your organisation |
| People who register or sign in | Name, e-mail address, password (only as an irreversible hash), language, two-step verification data (authenticator, passkeys, recovery codes, only encrypted or as a hash), sessions (device, IP address, time) | Providing an account, signing in securely, showing and ending sessions | Contract (b); for colleagues a customer invites: legitimate interest (f) of the customer and of us in a secure service | As long as the account exists, then deleted with the organisation (see §9) |
| Users of the service | Audit log: who did something with sign-ins, rights, keys, backups and connections, when, from which address and device | Security, accountability, detecting fraud and abuse | Legitimate interest (f); for the customer, part of the service | As long as the organisation exists [TO DECIDE: a fixed retention period] |
| Customers' contact persons | Name, e-mail address, phone number, job title, company details | Performing the agreement, sending messages about the service (such as maintenance, changes, prices) | Contract (b) and legitimate interest (f) | During the agreement and 2 years after |
| Customers (billing) | Company name, address, VAT number, contact person, plan, number of active users, number of questions to the assistant, invoices, payment status, payment mandate details (such as name and IBAN) | Invoicing, collecting payments, accounting | Contract (b) and legal obligation (c) | 7 years (Dutch tax retention obligation) |
| People asking for support | Your message, e-mail address, organisation, and what you attach (such as a screenshot via the feedback button) | Helping you, improving the service | Contract (b) and legitimate interest (f) | 2 years after handling [TO DECIDE] |
| People reporting a vulnerability | Name (if you give it), e-mail address, your report | Handling the report | Legitimate interest (f) | 2 years after handling |
| People who turn on push notifications | An address of your browser's push service and that device's keys | Showing notifications on that device | Consent (a): you turn it on and off yourself | Until you turn push off or sign out on that device |
We do not use your data for advertising, profiling or selling to others. We take no decisions about you based solely on automated processing. We send no newsletter or advertising unless you choose to receive it. We weigh a legitimate interest against your privacy; you can always object to it (§7).
4. The assistant (AI)
The built-in assistant and the support chat run on Mistral AI (France, EU). When someone asks a question, that question and the pieces of data needed for the answer go to Mistral AI. The assistant only works with the rights of the person asking: it sees nothing that person may not see. The knowledge bases (search index) are in our own database, not at Mistral AI.
We use Mistral AI's paid API, under which, according to its terms, Mistral AI does not use the data to train its models. [to verify: the current wording of Mistral AI's terms and data processing agreement, Mistral AI's retention period for abuse monitoring (known: up to 30 days) and whether "zero data retention" is enabled for our account.] We do not use customer data to train AI ourselves either. The audit log records that a question was asked, not its words.
5. Whom we give data to
We only give data to others if this is needed for the service, if the law requires it, or if you choose it.
- Our processors (they work on our behalf, under a data processing agreement): the service's e-mail (such as welcome links, new passwords and notifications).
[TO DECIDE: whether AFAS is in use.]- TransIP B.V. (the Netherlands): the servers and storage in a Kubernetes cluster in the Netherlands, and sending the service's e-mail (such as welcome links, new passwords and notifications).
- Mistral AI (France): the assistant, see §4.
- AFAS Software B.V. (the Netherlands): our own bookkeeping, if we keep it there.
[TO DECIDE: whether AFAS is in use.]
- Mollie B.V. (the Netherlands) processes payments. Mollie is a supervised payment institution and is itself responsible for part of what it does (such as fraud and anti-money-laundering checks).
[to verify: Mollie's role, controller or processor, under Mollie's current terms.]If you pay on a Mollie page, Mollie's privacy statement also applies there. - Your browser's push service: if you turn on push notifications, a notification goes through the push service of your browser's maker (for example Google, Mozilla, Apple or Microsoft). That notification is encrypted and contains only a number; what it is about you only see in novarint. These services may operate outside the EU; you choose them with your browser.
- Parties the customer connects itself: a customer can connect novarint to its own AI service (through MCP) or to other systems (web services, webhooks, its own mail, API keys). Data then go to that party, under the arrangements between the customer and that party (see §6).
- Authorities: only if the law obliges us, for example by court order. We check whether such a request is legally valid and give no more than needed.
The full list is on the sub-processors page.
6. Data outside the EU
We store all data in the European Union (in the Netherlands) and do not ourselves transfer data to countries outside the European Economic Area (EEA).
There are two exceptions, and the customer or user chooses them:
- Your own AI service through MCP. If a maker connects novarint to, for example, Claude (Anthropic, US), Cursor (Anysphere, US) or GitHub Copilot (GitHub/Microsoft, US), that AI service fetches data from novarint with that maker's rights. Those data then go to that party, possibly outside the EEA, under the agreement between the customer (or the maker) and that party. That party is not our processor; the customer decides about it and is responsible for it, including an appropriate basis for the transfer (such as the EU-US Data Privacy Framework or standard contractual clauses). Mistral Vibe (Mistral AI) operates in the EU. The connection is only on after the maker's explicit choice and can be revoked at any time.
- Push notifications, see §5: encrypted, only a number, through the browser's push service.
The same applies to web services and webhooks a customer sets up itself: the customer chooses where the data go.
7. Your rights
You have the right to:
- ask which data we hold about you (access) and get a copy;
- have incorrect data corrected;
- have data erased;
- have processing restricted;
- object to processing based on legitimate interest;
- receive your data in a common file format or have them sent on (portability);
- withdraw consent you gave (such as push notifications: turn them off on the device).
E-mail hi@novarint.com for this. We respond within one month. We may ask you to show that the request comes from you. If it concerns data a customer put into novarint, we forward your request to that customer and help it handle it.
Do you disagree with how we handle your data? Let us know. You can also lodge a complaint with the Dutch Data Protection Authority, the Autoriteit Persoonsgegevens (autoriteitpersoonsgegevens.nl).
8. How we secure your data
We take appropriate technical and organisational measures. The main ones:
- the service runs in our own Kubernetes cluster at TransIP in the Netherlands; all traffic is encrypted (https);
- every organisation is separated: every database has its own schema with its own database role, and PostgreSQL row-level security keeps organisations apart; tests prove that a request never reaches another organisation's data;
- we store passwords only as an irreversible hash (Argon2id), sessions and keys only as a hash; connection secrets encrypted;
- two-step verification (authenticator app, passkeys), which an owner can require for everyone; sensitive actions ask for the second step again;
- an audit log per organisation that cannot be changed unnoticed;
- limits on the number of requests and sign-in attempts;
- encrypted backups every night (7 daily, 4 weekly, 12 monthly), and every week a test that a backup can really be restored;
- hardened, scanned software images without unnecessary parts, and every change tested before it goes live;
- our staff only look into customer data when the customer asks or when a failure or incident requires it.
The full list is in annex 2 of the data processing agreement. If you find a vulnerability, please report it under our vulnerability disclosure policy.
9. Retention and deletion
The periods are in §3. After the end of a trial or plan, the organisation remains read-only for 30 days so the customer can export everything; then we delete the organisation, with its accounts and customer data. They remain in our encrypted backups until those are replaced under the retention schedule, at the latest 12 months; we use those backups only to restore the whole service after a failure.
10. Cookies
We only use cookies needed to sign in and work securely, and no cookies to track you or for advertising. Our website loads no fonts or scripts from others. See the cookie statement.
11. Changes
We may update this statement, for example when the service changes. The date at the top shows which version applies. For an important change we tell customers in advance.
12. Contact
NOVARINT B.V. · Scholekster 5, 2201 XH Noordwijk, the Netherlands · hi@novarint.com · +31 6 25413594