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 you found and where (address, page or endpoint);
- how we can reproduce it (steps, and if possible a screenshot or request);
- what someone could do with it;
- how we can reach you. Anonymous reports are welcome too.
What is in scope
cloud.novarint.com- the apps on
*.cloud.novarint.com - the installable app (PWA) and novarint's MCP server
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
- Only test in your own Demo or your own trial organisation, never in others' data.
- Do no more than needed to demonstrate the weak spot. If you still see others' data by accident, stop, do not copy or keep them, and tell us.
- Do not change or delete data and do not leave a backdoor or other program behind.
- No attacks that take down or slow down the service (denial of service), no spam, no social engineering (such as phishing or calling our people) and no physical attacks.
- Do not use automated scanners that generate a lot of traffic, and do not guess passwords (brute force).
- Report it to us as soon as possible and share the weak spot with no one else until we have fixed it. We agree together when you may publish about it; without another agreement, that is after the fix, or at the latest 90 days after your report.
What you can expect from us
- Within 3 working days a confirmation that we received your report.
- Within 10 working days our assessment and, where possible, when we expect to fix it.
- We keep you informed and tell you when it is fixed.
- If you follow this policy, we will not report you to the police or take you to court for your research. (The Dutch Public Prosecution Service decides on prosecution itself; we can only speak for ourselves.)
- We treat your report confidentially and do not give your details to others without your consent, unless the law requires it.
- If you wish, we name you as the finder when we tell about the fix.
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.