Data processing agreement (DPA)
Version 0.1.0, November 18, 2026.
Data processing agreement (DPA)
Appendix 1 to the terms of sale. Entered into under Article 28 of Regulation (EU) 2016/679 (GDPR).
1. Parties
- The controller: the AttackScout customer that has accepted the terms of sale ("the customer").
- The processor: Simon Raynaud, sole trader (autónomo), trading under the trade name Elerine, who operates AttackScout, C/ Almazara n° 232, 30153 Corvera (Murcia), Spain, NIF (NIE) Y7168667H ("AttackScout").
The customer accepts this agreement by accepting the terms of sale. It is concluded electronically, as permitted by the GDPR (Art. 28.9).
2. Purpose and scope
2.1. This agreement applies to the personal data that AttackScout processes on behalf of the customer when it audits the customer's domains, in particular during the in-depth check after proof of ownership, and when it receives the aggregate DMARC reports the customer has sent to it. For this data, the customer is the controller; AttackScout uses it only to perform the service, on the customer's documented instructions.
2.2. It does not apply to processing for which AttackScout is itself the controller (account, billing, authorization log, security, public audit), described in the privacy policy.
3. Description of the processing
| Item | Description |
|---|---|
| Nature | Automated reading, from the internet, of public data and the pages of the customer's website; analysis; storage of findings; report generation; receipt and totaling of aggregate DMARC reports |
| Purpose | Providing the customer with the security check of its domains and the alerts provided for in the terms of sale |
| Duration | That of the subscription, then the export period (section 11) |
| Data subjects | Employees, managers, providers and contacts of the customer, and anyone whose data appears on the pages or in the public records of the domain |
| Data | Email addresses and names found in the DNS, certificates, subdomains or crawled pages; IP addresses of sending servers (DMARC reports, if the customer has them sent to AttackScout); secret key type and 4 characters (never the full key); addresses of sensitive files found (never their content) |
| Sensitive data | None is sought. If a page contains any, it is not kept beyond the finding |
| Location | European Union (Google Cloud, europe-west1, Belgium), except safeguarded transfers (section 7) |
4. AttackScout's obligations
AttackScout: a) processes the data only on the customer's documented instructions. The terms of sale, the terms of use, the account settings and this agreement constitute these instructions. If an instruction appears to infringe the GDPR, AttackScout informs the customer (GDPR, Art. 28.3.a and last subparagraph); b) ensures that anyone authorized to process the data is bound by confidentiality (Art. 28.3.b); c) takes the security measures in Appendix A (Art. 28.3.c and 32); d) complies with the rules in section 6 on sub-processors (Art. 28.3.d); e) assists the customer, through appropriate technical and organizational measures, in responding to requests to exercise rights (Art. 28.3.e); f) assists the customer in meeting its obligations regarding security, breach notification and impact assessment (Art. 28.3.f); g) at the end of the service, deletes or returns the data at the customer's choice (section 11) (Art. 28.3.g); h) makes available to the customer the information needed to demonstrate compliance with this agreement and allows audits (section 9) (Art. 28.3.h).
5. Customer's obligations
The customer: a) has a legal basis for having its domains audited and is entitled to have them audited (terms of use, Art. 4); b) informs, where necessary, the data subjects in its organization; c) does not ask AttackScout to process data beyond what the service provides.
6. Sub-processors
6.1. The customer gives a general authorization for the use of the sub-processors listed on the "Sub-processors" page (GDPR, Art. 28.2).
6.2. AttackScout informs the customer by email at least 30 days before adding or replacing a sub-processor. The customer may object on reasonable grounds related to data protection. Failing agreement, it may cancel the domains concerned and be refunded the unused portion.
6.3. AttackScout imposes equivalent obligations on each sub-processor and remains liable to the customer for their compliance (GDPR, Art. 28.4).
7. Transfers outside the European Economic Area
A transfer only takes place to a country recognized as adequate (GDPR, Art. 45), including companies certified under the EU-U.S. Data Privacy Framework, or with appropriate safeguards, such as the Commission's standard contractual clauses (Art. 46.2.c). The "Sub-processors" page states the mechanism for each one.
8. Data breach
8.1. AttackScout informs the customer without undue delay, and at the latest 48 hours after becoming aware of it, of any data breach affecting the data processed on its behalf, by email to the account holder.
8.2. The information includes what Article 33.3 GDPR provides for, insofar as AttackScout knows it: nature of the breach, categories and approximate number of data subjects and records, likely consequences, measures taken or proposed, contact. What is not yet known is sent as soon as possible.
8.3. The customer remains responsible for notifying the supervisory authority (within 72 hours, Art. 33.1) and, where necessary, the data subjects (Art. 34). AttackScout helps it do so.
9. Audits
9.1. AttackScout answers the customer's written questions on compliance with this agreement within 30 days, and provides the relevant documentation (description of measures, list of sub-processors, its providers' certifications).
9.2. If this information is not sufficient, the customer may have an audit carried out, at its own expense, at most once a year, with 30 days' notice, by an auditor bound by confidentiality and not a competitor. The audit must not compromise the security or data of other customers.
10. Requests from data subjects and authorities
If a person contacts AttackScout about data processed for the customer, AttackScout forwards the request to the customer without answering it, unless instructed otherwise. AttackScout informs the customer of any request from an authority concerning this data, unless legally prohibited.
11. End of the service
11.1. At the end of the subscription, the customer may export its data for at least 30 days (terms of sale, Art. 15).
11.2. Then, AttackScout deletes the data processed for the customer, including copies, within 30 days; database backups, replaced on a rolling basis, no longer contain it 7 days later. This deletion applies unless there is a legal obligation to retain (GDPR, Art. 28.3.g).
11.3. The proof-of-ownership log is not affected: AttackScout keeps it on its own behalf, as controller (privacy policy, §3.4).
12. Liability
Each party's liability is governed by Article 82 GDPR and by the terms of sale, within the limits permitted by law.
13. Term, governing law and jurisdiction
This agreement lasts as long as AttackScout processes data for the customer. It is subject to Spanish law and to the jurisdiction rules of the terms of sale (Art. 20).
For an instruction, an audit request or a deletion request: [email protected].
14. Languages
This agreement exists in French, English, Spanish, German, Italian and Portuguese. French is the language in which it was drafted: in the event of a discrepancy, the French version prevails.
---
Appendix A — Security measures
- Hosting in the European Union (Google Cloud, europe-west1, Belgium); encryption of data in transit (TLS) and at rest; database with no public address.
- Administration console protected by Cloudflare Access and two-factor authentication with a passkey; named list of administrators; least privilege.
- Secrets (API keys, webhook addresses) stored encrypted, never in the code.
- Logical separation of each account's data, verified by automated tests.
- Minimization: never the content of a sensitive file, never a full key, never a password; only findings. Domain, host names, IP addresses and emails replaced with tokens before anything is sent to the AI model that writes the monthly report.
- Protection against requests to internal addresses (SSRF); probe limited to the verified domain.
- Logging of access and administrative actions, with truncated IP addresses; security alerts.
- Daily database backups, kept for 7 days, with point-in-time recovery over 7 days (transaction logs kept for 7 days); daily database exports, encrypted, hosted in the European Union and kept for 7 days at most; database protected against deletion.
- Every change goes through continuous integration (tests, secret scanning, dependency analysis) and a progressive rollout with automatic rollback.
- Handling of data breaches under section 8.
Appendix B — Sub-processors
See the "Sub-processors" page, which forms part of this agreement.
Appendix C — A partner's "Test your website" widget
Data processing agreement made under article 28 of the GDPR, whose clauses are set out below.
C.1. Parties and scope. This appendix applies when a partner (agency or integrator) turns the widget on (terms of sale, art. 21.4). The partner is the controller; AttackScout (identified in section 1) is its processor. It covers only the contacts described below. The partner accepts it by accepting the terms of sale; it is concluded electronically (GDPR, art. 28.9). In sections 6 to 12 cited below, "the customer" means the partner.
C.2. Subject matter and term. AttackScout collects, passes to the partner and keeps for it the contacts of visitors to its site who asked to be contacted. The agreement lasts as long as the partner's contract; each contact is kept for 12 months at most.
C.3. Nature and purpose. Nature: displaying the widget, testing the domain entered (level A public audit), recording the contact, sending an email to the partner, listing it in its console. Sole purpose: to let the partner contact the visitor who asked for it, after the consent box is ticked.
C.4. People and data. People: visitors to the partner's site who tick the box. Data: email address, domain tested, grade, language, date of the agreement, version of the text shown, truncated IP address (never the full address). No sensitive data.
C.5. Documented instructions. AttackScout processes the data only on the partner's documented instructions: the contract, this appendix and the widget settings (activation, allowed sites, company name, privacy link). AttackScout never uses these contacts for its own marketing or for any other purpose. If an instruction seems to it to breach the GDPR, it tells the partner (art. 28.3.a).
C.6. Partner's obligations. The partner has the legal basis for its own processing of the contacts and informs visitors: the widget shows, under the box, its company name and the link to its privacy policy, which it must keep accurate and up to date, and which must describe this processing. It uses the contacts only to answer the visitor's request, answers data-subject requests and does not ask AttackScout for other processing.
C.7. Confidentiality. Everyone authorized to process this data is bound by confidentiality (art. 28.3.b).
C.8. Security. The measures in appendix A apply (art. 32), plus: a widget frame with no cookie, a strict content policy, display limited to the sites the partner declares, anti-bot checks, quotas, truncated IP, nothing sent unless the box is ticked.
C.9. Sub-processors. The partner gives general authorization to the sub-processors on the "Sub-processors" page that act here: Google Cloud (hosting), Brevo (sending the email to the partner) and Cloudflare (network, anti-bot). Section 6 applies, including the 30 days' notice.
C.10. Data-subject rights. AttackScout passes to the partner, within 72 hours, any request a person sends it ([email protected]) and does not answer in its place, unless instructed otherwise. It helps the partner answer and erases a contact on the partner's written request (art. 28.3.e).
C.11. Breaches. Section 8 applies: the partner is told without undue delay and at the latest 48 hours after AttackScout becomes aware, and AttackScout helps with the notifications (art. 28.3.f).
C.12. End and fate of the data. When the partner's contract ends, AttackScout erases the contacts or returns them to the partner, at its choice, stated in writing within 30 days; with no choice in that time, it erases them. The widget stops working when the contract ends. Backups are replaced by rotation within 7 days (art. 28.3.g). If the contract does not end, each contact is erased 12 months after the visitor's agreement.
C.13. Audits. Section 9 applies (art. 28.3.h).
C.14. Transfers. The data is hosted in the European Union; section 7 applies.
C.15. Liability. Section 12 applies.