Draft — under legal review This text is a draft. A lawyer still reviews it; until then the terms in your quote or agreement apply.

Reporting vulnerabilities (responsible disclosure)

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. This English text is a translation; if the two differ, the Dutch text prevails.

The security of cloud.novarint.com and of our customers' data matters to us. Have you found a weak spot? Let us know, and we will fix it together.

How to report

E-mail hi@novarint.com with "Security" in the subject. Describe:

What is in scope

Not in scope: our suppliers' systems (such as TransIP, Mollie and Mistral AI; report to that party directly), and servers on which a customer runs novarint itself (report to the customer, or to us if it concerns the software).

What we ask of you

What you can expect from us

We have no reward programme (bug bounty) and promise no payment. We may thank you for a good report in a way of our own choosing.

Reports that are usually not a weak spot: a missing header without demonstrable impact, version numbers, SPF/DMARC remarks without abuse, clickjacking on pages without actions, or self-XSS.

security.txt

This is the text for https://cloud.novarint.com/.well-known/security.txt (per RFC 9116). It must be renewed every year, before the date in Expires.

`` Contact: mailto:hi@novarint.com Expires: 2027-11-18T00:00:00.000Z Preferred-Languages: nl, en Canonical: https://cloud.novarint.com/.well-known/security.txt Policy: https://cloud.novarint.com/legal/responsible-disclosure ``

Policy points to the page with this policy; change the address if the page ends up elsewhere.