Data Processing Agreement
Last updated: 22 October 2026 · version 2026-10
This data processing agreement is part of Nudge's terms of service. By creating an account the Customer enters into it with Nudge. It meets Article 28(3) of the General Data Protection Regulation (GDPR). The Dutch version is legally binding; this English version is a faithful translation. For a signed copy for your records, email info@nudgedigital.nl.
1. Parties and roles
1.1 Controller: the Customer, the organisation that uses the Platform to build Nudges and collect leads.
1.2 Processor: Nudge Digital, trade name of Consulting with Tom, Chamber of Commerce 93401639, Wolgalaan 32, 1448 KT Purmerend, the Netherlands.
1.3 Terms have the meaning given in the GDPR and in the terms of service.
2. Subject matter, duration, nature and purpose
2.1 Subject matter: processing personal data of Visitors who complete a Customer's Nudge, and of the colleagues the Customer gives access.
2.2 Duration: for as long as the Customer uses the Platform, and afterwards until the data has been deleted under article 10.
2.3 Nature: storing, organising, structuring, calculating (score and result), displaying, exporting, forwarding to integrations chosen by the Customer, sending messages in the Customer's name, and deleting.
2.4 Purpose: providing the Platform as described in the terms of service: showing Nudges, storing submissions, showing leads in the Lead Vault, follow-up by email, text message or WhatsApp, and connecting the Customer's systems.
3. Data subjects and data
3.1 Data subjects: visitors to the Customer's websites or links who complete a Nudge; recipients of follow-up messages; users of the Customer's account.
3.2 Data, depending on the Customer's settings:
- answers to the Nudge's questions, the score and the result;
- contact details such as name, email address, phone number, company name, job title, company size, LinkedIn profile and company website;
- origin data: page, referring page, browser type and hashed IP address;
- proof of consent: whether the checkbox was ticked, when, and which links were shown;
- follow-up data: messages sent, link clicks, replies to emails, unsubscribes and meetings;
- notes, status and deal value the Customer adds to a lead.
3.3 The Customer does not ask for special categories of personal data, criminal records or national identification numbers through a Nudge, unless the law allows it. If the Customer does so anyway, the Customer is responsible for the legal basis and any data protection impact assessment (DPIA).
4. Instructions
4.1 Nudge processes the data only on the Customer's documented instructions. The settings the Customer chooses in the Platform, and this agreement, are those instructions.
4.2 Nudge does not process the data for its own purposes, does not use it for advertising and does not allow it to be used to train AI models.
4.3 If Nudge considers an instruction unlawful, it informs the Customer immediately.
4.4 If the law requires Nudge to disclose data to an authority, Nudge informs the Customer in advance, unless the law prohibits this.
5. Confidentiality
Everyone at Nudge with access to the data is bound by confidentiality. Access is limited to those who need it for support or administration, and is logged.
6. Security
6.1 Nudge takes appropriate technical and organisational measures, taking into account the state of the art, the costs and the risks to data subjects (Article 32 GDPR). The measures are listed in annex 1 and on the security page.
6.2 Nudge may adjust measures, provided the level of security does not decrease.
7. Sub-processors
7.1 The Customer gives Nudge general authorisation to engage sub-processors. The current list is on the sub-processors page.
7.2 Nudge notifies a new or replacement sub-processor at least 30 days in advance by email to the account owner. The Customer may object with reasons within that period. If we cannot resolve it, the Customer may terminate before the change takes effect, without cost for the remaining period.
7.3 Nudge imposes the same obligations as in this agreement on every sub-processor and remains liable to the Customer for their performance.
7.4 Integrations the Customer turns on, such as a CRM, Slack, Microsoft Teams, Cal.com or its own webhook, are not Nudge's sub-processors. The Customer chooses them and makes its own arrangements with them.
8. Transfers outside the EEA
Nudge transfers data outside the European Economic Area only with a valid basis under Chapter V GDPR: an adequacy decision, including the EU-US Data Privacy Framework, or the European Commission's standard contractual clauses with supplementary measures. The basis per sub-processor is on the sub-processors page.
9. Assistance
9.1 Nudge helps the Customer respond to data subject requests. The Customer can do much of this in the Platform: view, edit, export and permanently delete leads. If Nudge receives a request directly, it forwards it within five working days and does not answer it itself.
9.2 Nudge provides the Customer with the information reasonably needed for a DPIA or a prior consultation with the supervisory authority.
10. End: return and deletion
10.1 During the agreement the Customer can export all leads as CSV at any time.
10.2 If the Customer deletes its account, Nudge permanently deletes all personal data after a 30-day restore period. Copies in backups and in sub-processors' delivery logs disappear within their rotation periods.
10.3 Nudge keeps data longer only where the law requires it, and then only for that purpose.
11. Personal data breaches
11.1 If Nudge discovers a personal data breach affecting the Customer, it notifies the account owner without undue delay and no later than 48 hours after discovery.
11.2 The notification includes, as far as known: what happened, which data and how many data subjects are affected, the likely consequences, the measures taken and proposed, and a contact person. Information not yet known follows as soon as Nudge has it.
11.3 The Customer decides whether the breach is reported to the supervisory authority and to data subjects. Nudge does not report on the Customer's behalf, unless the Customer asks or the law requires it.
12. Audit
12.1 On request Nudge gives the Customer all information needed to demonstrate compliance with this agreement.
12.2 The Customer may have an audit carried out once a year, or after a data breach, by an independent expert bound by confidentiality, with at least 30 days' notice. The Customer bears the costs, unless the audit reveals a material shortcoming by Nudge.
13. Liability
Liability under this agreement is subject to the limitations in the terms of service, unless the GDPR excludes this. A fine imposed on a party by a supervisory authority is borne by the party to whom the infringement is attributable.
14. Precedence and law
In case of conflict with the terms of service, this agreement prevails as far as personal data is concerned. Dutch law applies; the District Court of North Holland has jurisdiction.
Annex 1. Security measures
- Encryption: all connections over TLS 1.2 or higher with HSTS; storage encrypted at rest by the database provider.
- Separation: Row Level Security in the database, so an organisation can only read its own data; partner accounts only see their own clients.
- Access: two-factor authentication (TOTP) with recovery codes; roles per user; administrative access limited and logged; support access to a customer account only with a temporary, logged token.
- Passwords and keys: passwords only as hashes; IP addresses only hashed with a secret salt; secrets only in the hosting environment settings, never in code.
- Application: strict Content Security Policy, clickjacking protection, input validation on all public endpoints, request rate limits, bot protection, SSRF checks on outbound connections, signed unsubscribe and report links, signed webhooks.
- Logging and monitoring: an activity log for accounts, error tracking and a daily health check with alerts on failures.
- Continuity: automatic database backups; a recovery procedure and incident runbook.
- Development: every change through a pull request with automated type checks, lint and tests; separate test and production environments; periodic security audits; dependencies monitored with automated security alerts.
- Suppliers: only suppliers with a data processing agreement and appropriate certification or safeguards.
- Incidents: a fixed data breach procedure and a vulnerability reporting point.
The Dutch version of our legal documents is legally binding.