Security
Last updated: 22 October 2026 · version 2026-10
Nudge processes our customers' leads. That calls for security you can verify. Below is what we do, organised by the measures the NIS2 Directive lists (in the Netherlands the Cyberbeveiligingswet). As a small company Nudge is not itself in scope of that law, but customers that are must assess their suppliers. This page helps with that.
Honest about certification: Nudge does not yet hold an ISO 27001 or SOC 2 certificate. We work according to those standards, and our hosting and storage suppliers are certified.
Access and identity
- Two-factor authentication with an authenticator app, with one-time recovery codes stored only as hashes.
- Roles per user: owner, admin and member. Partners only see their own clients.
- Bot protection at sign-in and sign-up, and limits on login attempts.
- Nudge's own administrative access is limited to the founder, with two-factor authentication. Viewing a customer account for support only happens with a temporary token and is logged.
Data
- All connections over TLS 1.2 or higher, with HSTS.
- Storage encrypted at rest by the database provider, in Frankfurt (EU).
- Row Level Security in the database: every query only sees the data of its own organisation.
- Passwords only as hashes, IP addresses only hashed with a secret salt.
- Lead contact details never go to AI models.
- Proof of consent per lead, so customers can demonstrate that a visitor agreed.
Application
- A strict Content Security Policy with per-request nonces and a violation report endpoint.
- Protection against clickjacking, MIME sniffing and referrer leakage.
- Schema-based input validation on all public endpoints, request rate limits, a honeypot and timing checks against bots.
- Outbound connections to addresses supplied by customers are checked against SSRF, including after redirects.
- Unsubscribe links, report links and click tracking are signed; webhooks to customers are signed with a key per organisation.
- Secrets only live in the hosting environment settings, never in code.
Development and suppliers
- Every change goes through a pull request with automated type checks, lint and tests, first to a test environment and only then to production.
- Dependencies are checked weekly for known vulnerabilities.
- Periodic security audits of the code; the latest in October 2026.
- Suppliers only with a data processing agreement; the list is on sub-processors.
Continuity and incidents
- Automatic database backups.
- A daily health check that alerts on failures, error tracking and an incident runbook.
- A fixed data breach procedure: customers are informed without undue delay and no later than 48 hours after discovery.
Reporting a vulnerability
If you find a security issue, report it to info@nudgedigital.nl with "Security report" in the subject. Describe what you found and how we can reproduce it.
- We confirm your report within two working days and keep you informed.
- Only test with your own account and your own data. Don't view, change or delete other people's data, and don't disrupt the service.
- Only disclose an issue publicly once it is fixed, or after 90 days in consultation.
- If you follow these rules, we will not take legal action, and we are happy to credit you by name if you wish.
Our policy is also available in machine-readable form at /.well-known/security.txt.
Questionnaires
Need to assess Nudge as a supplier, for example for NIS2 or your own ISO certification? Email your questionnaire to info@nudgedigital.nl. We fill it in and sign the data processing agreement on request.
The Dutch version of our legal documents is legally binding.