Data Processing Agreement
This Data Processing Agreement ("DPA") forms an integral part of the Terms and Conditions of Cruxa and applies to every Scan performed by Cruxa on behalf of Client.
1. Parties and roles
- Data Controller: Client (the party requesting and confirming the Scan).
- Data Processor: Cruxa, a sole proprietorship operating under the name Cruxa, registered in the Netherlands and listed in the Dutch Commercial Register (Chamber of Commerce) under number 42044115.
- Cruxa processes personal data exclusively on behalf of and for the benefit of Client, in accordance with this DPA and Client's written instructions.
- If, in Cruxa's opinion, an instruction from Client infringes the GDPR or other applicable data protection legislation, Cruxa will inform Client thereof without delay.
2. Purpose and legal basis
- Processing takes place for the execution of the automated security scan as described in the Terms and Conditions.
- The legal basis is the performance of the agreement between Cruxa and Client (Article 6(1)(b) GDPR) and Client's legitimate interest in securing their systems (Article 6(1)(f) GDPR).
3. Categories of personal data
The processing concerns the following categories of data subjects: (i) the contact person(s) of Client, and (ii) data subjects whose personal data is inadvertently encountered in Client's tested systems, such as end users, customers, or employees of Client.
3.1 Client contact data
Processed for the execution of the agreement:
| Data | Purpose | Retention |
|---|---|---|
| Contact name | Communication and reporting | 12 months after Scan |
| Company name and role | Identification and authorization verification | 12 months after Scan |
| Business email address | Verification, communication, report delivery | 12 months after Scan |
| IP address at request/confirmation | Fraud prevention, consent documentation | 12 months after Scan |
3.2 Data encountered during the Scan
During a security scan, Cruxa may inadvertently encounter personal data in Client's systems, such as:
| Category | Examples | Processing |
|---|---|---|
| User data | Email addresses, names, phone numbers in API responses or databases | Recorded only as evidence of a vulnerability (e.g., IDOR, data leak). Minimized in Report. |
| Authentication data | Session tokens, API keys, password hashes | Recorded only as evidence. Never stored in plain text after reporting. |
| Special category data | National ID numbers, medical data, financial data | If encountered: immediately reported to Client. Minimized in Report (category mention only, not content). |
4. Sub-processors
Cruxa uses the following sub-processors:
| Sub-processor | Service | Location | Data |
|---|---|---|---|
| Google Ireland Limited | Google Apps Script / Google Sheets | EU (Ireland) | Request data, consent registration |
| Resend Inc. | Transactional email | US (EU Standard Contractual Clauses) | Email address, name (in email body) |
| Anthropic PBC | AI model (Claude) for scan analysis | US (EU Standard Contractual Clauses) | Technical scan data. No personal data unless encountered during scan. |
| Hosting provider | Server (Docker containers) | EU (Netherlands) | Scan results, findings, reports |
- By accepting this DPA, Client consents to the use of the above sub-processors.
- Cruxa will inform Client of changes to the sub-processor list. Client has the right to object within 14 days of notification.
- Cruxa ensures each sub-processor is bound by an agreement containing at minimum the same obligations as this DPA.
5. Security measures
Cruxa implements the following technical and organizational measures to protect personal data:
5.1 Technical
- Encrypted connections (TLS 1.2+) for all communication
- Encrypted storage of sensitive data (at-rest encryption)
- Separation of client data per Scan (no shared storage between engagements)
- Automatic deletion of scan data after the retention period
- Secured access to systems via SSH keys and two-factor authentication
- Regular updates of all software and dependencies
- Technical PII redaction on scan data sent to external processors (including AI models): personal data in scan results is automatically replaced with typed placeholders before leaving the processing environment. This reduces exposure but does not guarantee complete elimination of all personal data
5.2 Organizational
- Access to client data is limited to Cruxa staff who require it for execution
- All staff are bound by confidentiality obligations
- No use of client data for training AI models — contractually agreed with all sub-processors, supplemented by technical PII redaction (see 5.1)
- Annual review of security measures
6. Retention periods
| Data | Retention period | After expiry |
|---|---|---|
| Client contact data | 12 months after Scan | Automatically deleted |
| Report | 12 months after delivery | Automatically deleted |
| Raw scan data (logs, findings) | 3 months after Report delivery | Automatically deleted |
| Consent registration (consent receipt) | 5 years after Scan | Retained for legal documentation |
| Invoicing data | 7 years (statutory requirement) | Retained per fiscal legislation |
7. Data subject rights
- Client, as data controller, is the primary point of contact for data subjects wishing to exercise their rights (access, rectification, erasure, restriction, portability, objection).
- Cruxa will assist with data subject requests forwarded by Client, within 10 business days.
- If a data subject contacts Cruxa directly, Cruxa will refer them to Client and inform Client accordingly.
8. Data breach notification
- Cruxa will report any data breach involving personal data of Client or their data subjects within 24 hours of discovery, via email to the address provided during onboarding.
- The notification will include at minimum:
- the nature of the breach;
- the (estimated) categories and numbers of personal data records affected;
- the likely consequences;
- the measures taken or proposed by Cruxa to mitigate the breach.
- Notification to the supervisory authority and/or data subjects is the responsibility of Client as data controller.
9. Audits
- Client has the right, upon written notice with a reasonable period of at least 14 days, to audit compliance with this DPA.
- Cruxa will cooperate with such an audit and provide all relevant information.
- Audit costs are borne by Client, unless the audit reveals a material breach by Cruxa.
10. International transfers
- Personal data is preferably processed within the European Economic Area (EEA).
- For sub-processors outside the EEA (Resend, Anthropic), EU Standard Contractual Clauses (SCCs) apply in accordance with Commission Implementing Decision (EU) 2021/914.
- Cruxa conducts a Transfer Impact Assessment for each non-EEA sub-processor and applies supplementary technical measures where necessary (encryption, pseudonymization).
11. Termination
- Upon termination of the agreement, Cruxa will delete all personal data in accordance with the retention periods in article 6, unless statutory retention obligations apply.
- Client may request a copy of their data at any time (subject to the retention period) via [email protected].
- Cruxa will confirm deletion in writing upon Client's request.
12. Final provisions
- In case of conflict between this DPA and the Terms and Conditions, this DPA prevails with regard to the processing of personal data.
- This DPA is governed by Dutch law.
- Amendments to this DPA are communicated in the same manner as amendments to the Terms and Conditions. The version in effect at the time of Client's confirmation remains applicable to that specific agreement.
- The current version is always available at cruxa.io/dpa.
Questions about this data processing agreement? Contact us at [email protected].