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

WhomWhich dataFor whatLegal basis (GDPR art. 6(1))How long
Visitors of the website and the DemoIP address, time, page requested, browser details (in server logs)Running and securing the website and Demo, countering abuse and attacksLegitimate interest (f)[TO DECIDE: for example 30 days]
People using a DemoWhat you enter in the Demo (without an account)Running the DemoLegitimate interest (f)Until the end of the Demo's lifetime, then deleted. If you register, it becomes your organisation
People who register or sign inName, 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 sessionsContract (b); for colleagues a customer invites: legitimate interest (f) of the customer and of us in a secure serviceAs long as the account exists, then deleted with the organisation (see §9)
Users of the serviceAudit log: who did something with sign-ins, rights, keys, backups and connections, when, from which address and deviceSecurity, accountability, detecting fraud and abuseLegitimate interest (f); for the customer, part of the serviceAs long as the organisation exists [TO DECIDE: a fixed retention period]
Customers' contact personsName, e-mail address, phone number, job title, company detailsPerforming 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, accountingContract (b) and legal obligation (c)7 years (Dutch tax retention obligation)
People asking for supportYour message, e-mail address, organisation, and what you attach (such as a screenshot via the feedback button)Helping you, improving the serviceContract (b) and legitimate interest (f)2 years after handling [TO DECIDE]
People reporting a vulnerabilityName (if you give it), e-mail address, your reportHandling the reportLegitimate interest (f)2 years after handling
People who turn on push notificationsAn address of your browser's push service and that device's keysShowing notifications on that deviceConsent (a): you turn it on and off yourselfUntil 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.

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:

  1. 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.
  2. 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:

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 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