Privacy policy
Version 0.1.0, November 18, 2026.
Privacy policy
Basic information (first layer)
This summary is shown below every form that collects data (Organic Law 3/2018, LOPDGDD, Art. 11.1 and 11.2).
| Controller | Simon Raynaud (Elerine, AttackScout brand), C/ Almazara n° 232, 30153 Corvera (Murcia), Spain · [email protected] |
| Purposes | Running requested audits, managing accounts and billing, proving audit authorizations, sending alerts and, if you agree, commercial emails and the weekly roundup newsletter |
| Observatory | Producing aggregated, anonymous statistics published in the observatory (at least 30 domains per figure, never a domain name), see §3.1 |
| Customer reviews | Asking for your review 30 days after you subscribe and, only if you agree, publishing it on our website, see §3.18 |
| Grade sharing | Allowing the holder of a verified, monitored domain to share its grade with a third party of its choice, see §3.19 |
| Integrator pilots | Preparing the pilot requested and writing to you about it, see §3.20 |
| Integrator prospecting | Offering our service to integrator companies by email, at their generic business address, see §3.21 |
| Automated assistant | Answering your questions about the service with an automated AI answer, which may be wrong, see §3.23 |
| Portfolio review | Carrying out, at an agency's request, a free review of its clients' domains (level A public audit), see §3.24 |
| Your other domains | Suggesting to subscribed customers that they add their other domains, found on the public website and DNS of their paid domain, see §3.25 |
| Report recipients | Sending your reports to the recipients you add, after their confirmation, see §3.6 |
| Abandoned payment | Reminding you of a payment started but not completed, with a link to resume it, see §3.26 |
| Sending to a provider | Sending, at the request of a signed-in client, the result of their public audit to their provider, in a single email with one-click unsubscribe, see §3.30 |
| Legal bases | Contract, legal obligation, legitimate interest, consent (depending on the processing, see §3) |
| Recipients | Our processors (hosting, email, payment, invoicing, AI); no sale of data |
| Rights | Access, rectification, erasure, objection, restriction, portability; complaint to the AEPD |
| More information | This page |
1. Who is the controller
Simon Raynaud, sole trader (autónomo), trading under the trade name Elerine, established in Spain, C/ Almazara n° 232, 30153 Corvera (Murcia), Spain — NIF (NIE) Y7168667H — EU VAT ESY7168667H. Service brand: AttackScout. Contact for your data: [email protected].
AttackScout has not appointed a data protection officer: none of the cases that require one applies (Regulation (EU) 2016/679, GDPR, Art. 37.1; LOPDGDD, Art. 34.1).
2. Our role
- For the public audit, accounts, billing, security, prospecting and audience measurement, AttackScout is the controller.
- For the in-depth check of a customer's domains and for the DMARC reports the customer has sent to us, AttackScout processes on behalf of that customer: the customer is the controller and AttackScout is a processor, under the data processing agreement (DPA) (GDPR, Art. 28).
- For the contacts collected by a partner's "Test your website" widget (§3.27), AttackScout processes data on the partner's behalf: the partner is the controller, AttackScout is the processor (GDPR, art. 28), under appendix C of the DPA.
3. What we process, why, on what basis and for how long
3.1 Public audit without an account (and "tools" pages)
- Data: the domain entered; the IP address of the person running the audit; the result. A domain may be personal data (for example
john-smith.com). - Purposes: running the audit; limiting abuse (quotas, Cloudflare Turnstile); honoring the exclusion list; producing aggregated, anonymous statistics published in the observatory (at least 30 domains per figure, never a domain name; terms of use, Art. 6.4).
- Basis: legitimate interest in providing a public security tool and protecting it from abuse (GDPR, Art. 6.1.f).
- Observatory statistics: they rely on legitimate interest (GDPR, Art. 6.1.f), for all their sources (public audits and level A audits of monitored domains, §3.3). This further use is compatible with the original purpose (GDPR, Art. 6.4): the purpose is close (understanding the state of security), the data concerns websites and not people, anonymization covers at least 30 domains and publication has no consequence for individuals. Safeguards: never a domain name, aggregates only.
- Retention: result 30 days; IP address for quotas: erased at the end of the quota window, and at the latest after 30 days; aggregated, anonymous statistics: without limit.
3.2 People mentioned in a domain's public data
While reading a domain's public data, the probe may come across data about people who did not run the audit: an email address in the DNS (SOA field, DMARC report address), a name in a subdomain listed in certificate logs, a name or address on a page of the website.
- Purpose: checking security settings. We do not look for this data and do not use it for anything else.
- Basis: legitimate interest (GDPR, Art. 6.1.f).
- Information: informing each person individually would involve disproportionate effort; this page serves as public information (GDPR, Art. 14.5.b).
- Retention: that of the audit result.
3.3 Account and domains
- Data: email, name, language, organization, domains, alert preferences, login logs, proof of acceptance of the terms (version, date, truncated IP); for the Integrator offer, proof of acceptance of the terms of sale (date, truncated IP, version of the terms of sale, company declared), kept like the proof of acceptance of the terms. Login is with a password, through a link sent by email or through an identity provider (§3.28). Your password is never stored as such: we only keep a fingerprint of it (argon2id hash), from which it cannot be read back. The profile chosen when the account is created ("business" or "private individual") is kept with each proof of acceptance.
- Purposes: managing the account and monitoring your domains; producing aggregated, anonymous statistics published in the observatory (at least 30 domains per figure, never a domain name; terms of use, Art. 6.4): the level A audits of monitored domains are also included in the sample.
- Basis: performance of the contract (GDPR, Art. 6.1.b); proof of acceptance: legitimate interest (Art. 6.1.f); observatory statistics: legitimate interest (Art. 6.1.f, see §3.1).
- Retention: as long as the account exists. A free account with no login or audit for 3 years is deleted, after a notice email. Aggregated, anonymous statistics: without limit.
3.4 Proof-of-ownership log
- Data: account, domain, value of the proof of ownership, dates, version of the terms, truncated IP, log of the in-depth check's requests (no content).
- Purpose: proving that each in-depth check was authorized, and defending ourselves in the event of a complaint.
- Basis: legitimate interest in establishing, exercising or defending legal claims (GDPR, Art. 6.1.f and 17.3.e).
- Retention: 6 years after the authorization ends, even after the account is deleted, then deletion. Until then, the data is blocked: restricted access, no other use (LOPDGDD, Art. 32).
3.5 Payment and billing
- Data: company name, address, country, tax numbers (VAT, NIF), result of the VIES check, invoices, payment history. Payment methods and transaction history are processed and stored by Mollie B.V. (Netherlands, EU); we do not keep any card number. The VAT number of an EU business is checked with the European Commission's VIES service. The currency (euro or US dollar) is recorded with the subscription, payments and invoices. When Mollie provides it, we keep the expiry date of the mandate's card (never its number), to notify you 30 days beforehand; it is replaced with each new mandate. The link in non-payment reminders is a random token of which we keep only the fingerprint, valid for 7 days. For a private individual (consumer): name, address and country, without any tax number; "private individual" profile; date of the request for immediate start of the service, made at payment (terms of sale, Art. 24.5).
- Bases: contract (GDPR, Art. 6.1.b); tax and accounting obligations (Art. 6.1.c).
- Retention: 6 years from the end of the year in which each invoice was issued (Código de Comercio, Art. 30.1), even after the account is deleted, then deletion.
3.6 Alerts, reports and integrations
- Data: email, your domains' results, the webhook addresses you configure (encrypted).
- Basis: contract (GDPR, Art. 6.1.b).
- Retention: as long as the account exists.
- Integrations: if you send alerts to Slack, Microsoft Teams or Discord, these services receive them under their own terms. You choose them; they are not our processors.
- Report recipients: if you add recipients to your reports, we process their email address to ask them for confirmation and then send them the reports you choose. Legal basis: their consent, given through the confirmation link and withdrawable in one click in every report. We keep the date and the truncated IP address of the confirmation as proof. An unconfirmed request is erased 30 days after the link expires. The link to the technical evidence report is only sent to a recipient with your agreement.
3.7 Reports written by artificial intelligence
The plain-language text of the monthly report is written by Anthropic's Claude API using only the audit results. Before sending, the domain, host names, IP addresses and email addresses are replaced with tokens, then put back into the text when it returns; the text is then checked automatically before display. Anthropic acts as our processor; its commercial terms exclude the use of this content to train its models. The text is labeled as written by an AI and may be wrong. No decision producing legal effects concerning you is made automatically: the grade concerns a domain, not a person (GDPR, Art. 22).
- Basis: performance of the contract (GDPR, Art. 6.1.b).
The weekly roundup of published vulnerabilities (CVEs) is written from public sources (NVD, CISA KEV catalog); it contains no data about our users.
Evidence report: we keep the technical facts of the report (DNS records, headers, certificate fingerprints), the signed seal, the date of issue and the issuing account, until the account is deleted. Email addresses read during the audit are removed from the facts. The public verification page only shows the domain, the dates, the fingerprint and the signature, plus a summary if the holder chose one; it is not indexed and does not keep the visitor's IP address.
3.8 Commercial emails
The weekly roundup newsletter is a separate purpose, described in §3.17.
- Without an account (after a public audit): only if you tick the box provided, which clearly states what you will receive (the result, deadline reminders and follow-up offers). Basis: consent (GDPR, Art. 6.1.a and 7; LSSI-CE, Art. 21.1). You may withdraw it at any time through the link in each email.
- Customers: information about services similar to those subscribed to, unless you object (LSSI-CE, Art. 21.2). A box lets you object at sign-up, then a link in each email. The offer of annual payment, 30 days after subscribing, relies on this legitimate interest towards an existing customer for a similar service (LSSI-CE, Art. 21.2), with one-click objection.
- Retention: until withdrawal or objection, and at most 12 months after the last deadline followed. Proof of consent or objection is kept for 3 years.
3.9 Domain exclusion requests
- Data: domain, date, confirmation method; the requester's email address until confirmation.
- Basis: legitimate interest in honoring the request over time (GDPR, Art. 6.1.f).
- Retention: domain, date and method, as long as the service exists; the requester's email is erased on confirmation, or after 30 days without confirmation.
3.10 Disputes, support and security reports
- Data: email, name, content of exchanges.
- Basis: legitimate interest in replying and correcting our results (GDPR, Art. 6.1.f); contract for customers.
- Retention: 3 years after the last exchange.
3.11 Prospecting professionals
- Channel: we do not send commercial emails to people who have not asked for them. Prospecting is done through LinkedIn messages written and sent one by one, without automation. Prospecting of integrator companies by email, at their generic address only, is described in §3.21.
- Data: name, position, company, published business contact details (LinkedIn profile, company website), history of exchanges, the company's public domains and their public audit (level A, without a grade). We keep the source of this data.
- Source and information: public professional profiles and pages. Each first message states who is writing, where the contact comes from, why, and how to object (GDPR, Art. 14.3.b).
- Basis: legitimate interest, limited to exchanges related to the recipient's professional activity (LOPDGDD, Art. 19.1; GDPR, Art. 6.1.f).
- Tools: the publisher's mailbox; the Claude API to translate and prepare messages, including replies received.
- Objection: at any time, by replying to the message or by email. We then keep only what is needed to stop writing to you (LOPDGDD, Art. 23.1). We honor the advertising exclusion systems provided for in Article 23.4 LOPDGDD where they apply.
- Retention: prospecting data is deleted 13 months after the last contact that received no follow-up; objection register, without limit.
3.12 Referrals and partners
- Data: referral code, link between accounts, credits, commissions; for the anti-fraud check, an encrypted fingerprint (HMAC) of the payment method provided by Mollie, never the card number or IBAN.
- Bases: contract (GDPR, Art. 6.1.b); legitimate interest in preventing fraud (Art. 6.1.f).
- Code: the referral code may also be entered at payment.
- A referrer or partner only sees numbers and amounts, never the audit results of their referees, except those of domains a customer has entrusted to them under the partner program.
- Retention: duration of the program, then 6 years for credits and commissions (accounting records).
3.13 Audience and journey measurement
We measure traffic, the steps of the journey (audit, account, domain, proof of ownership, payment) and clicks on a "Maybe soon" card on the server side, without cookies, without third-party scripts and without storing or reading anything in your browser (see the cookie policy). No IP address is recorded, even truncated, and no email address: a visitor receives a pseudonym that changes every day, and the domain audited by a visitor without an account is only kept as a fingerprint. Bots and test traffic are kept separate. Statistics are used only to improve the website.
- Basis: legitimate interest (GDPR, Art. 6.1.f).
- Retention: raw events 13 months; aggregated, anonymous statistics, without limit.
Question "What brings you here?". Below the result of an audit, an optional multiple-choice question ("Other" with a free-text field of 140 characters). Data: the reason, any free text (do not write an email address or any personal data in it), the language of the page, the audit concerned and, if you are signed in or create an account from this result, that account. No IP address and no pseudonym. Purpose: understanding why visitors come. Basis: legitimate interest (Art. 6.1.f). Retention: 13 months, erased with the account. A free text that nevertheless contains personal data is erased as soon as we see it.
Subscription stop history. When a domain leaves the paid subscription (removal, cancellation, non-payment, exclusion, deletion of the domain), we keep a record of it.
- Data: internal identifier of the domain (never its name), plan (monthly or yearly, multi-domain plan), start and end dates of payment, reason for the stop; linked to your account.
- Purpose: measuring subscription stops in order to improve the service.
- Basis: legitimate interest (GDPR, Art. 6.1.f).
- Retention: 13 months after the stop; erased when the account is deleted.
3.14 Service security
- Data: technical logs (truncated IP, dates, requests, errors), security logs.
- Basis: legitimate interest in protecting the service (GDPR, Art. 6.1.f; Recital 49).
- Retention: 6 months at most, unless an incident is ongoing.
3.15 Internal alerts
The publisher receives internal alerts (Discord) about the service's activity. They contain no email address or person's name, only counters, amounts, account identifiers and domains. Retention: 13 months.
3.16 Aggregate DMARC reports (if you have them sent to AttackScout)
If you add our report address to your DMARC record, mailbox providers send us aggregate reports on the emails sent in your domain's name. We process this data on your behalf, as a processor (see the data processing agreement).
- Data: domain names, IP addresses of sending servers, SPF, DKIM and alignment results, volumes. No email content, no recipients.
- Sending services: the sending IP addresses in the DMARC reports are shown to you and matched against an internal table of sending services, without any request to a third party.
- Basis: performance of the contract (domain whose ownership is proven, report address added by you).
- Retention: the raw report is deleted as soon as it is read. Daily totals are kept for 13 months, then deleted, and deleted with your account. A report sent by a mail provider we do not know yet is set aside, without being shown to you, for 30 days at most: we count it if it is recognised, otherwise we delete it.
- Processors: Cloudflare (receiving the reports, with a safeguarded transfer to the United States, see section 5) and Google Cloud (storage in the European Union).
- You may stop at any time by removing our address from your DMARC record.
3.17 Weekly roundup newsletter
Every Monday, the newsletter summarizes the vulnerabilities (CVEs) published the previous week. It is separate from account-related emails and commercial offers (§3.8).
- Basis: your consent (GDPR, Art. 6.1.a), including if you are a customer.
- Sign-up: without an account, from the footer, with double opt-in: nothing is sent until you click the confirmation link received by email, valid for 48 hours. From "My account", sign-up is immediate, since your address has already been verified there.
- Unsubscribing: in one click in each newsletter, including from your mailbox (RFC 8058), or from "My account".
- No tracking: we measure neither opens nor clicks.
- Data: email address, language, sign-up source (footer or account), history of sends without their content, and proof of consent and withdrawal (fingerprint of the address, action, source, dates, truncated IP address, version of the checkbox text).
- Recipient: Brevo, which sends the newsletter (see the "Sub-processors" page).
- Retention: the address is erased when consent is withdrawn; an unconfirmed request is erased 30 days after the link expires; the history of sends is kept for 400 days; proof of consent and withdrawal is kept for 3 years. No purge for inactivity: we do not track opens, and every newsletter lets you unsubscribe.
- Account deletion: it also deletes the newsletter subscription, even one made from the footer with the same address. Proof of consent is kept for 3 years, as evidence.
3.18 Customer reviews
30 days after you subscribe, we ask for your review of the service and, only if you agree, we publish it on our website.
- Data: rating from 1 to 5, optional comment, language, dates; if you agree to publication: first name, sector and the text of the agreement given.
- Legal bases: the review request relies on legitimate interest (GDPR, Art. 6.1.f), with one-click objection in the email; publication relies on your consent (GDPR, Art. 6.1.a), which you can withdraw at any time through the link you received.
- What is published: the rating, the comment (unless it contains a link, an address or a domain name), the first name, the sector and the month; never the email address, the last name, the account or the domain.
- Average: the average shown counts every rating received, without names.
- Recipients: no third party and no review platform (only our technical processors listed in §4 process this data).
- Retention: until the account is deleted. After a withdrawal, the review is no longer published, but proof of the agreement given and then withdrawn is kept until the account is deleted.
- Verified reviews: only customers who have been subscribed for at least 30 days can leave a rating. Every review received counts in the average, positive and negative alike; we only publish those whose author agreed.
3.19 Sharing the grade with a broker or an insurer
The holder of a verified, monitored domain may share its grade with a third party of its choice, by means of a personal token that is dated and revocable (terms of use, Art. 9.5). The insured company's data then becomes visible to the recipient it has chosen.
- Data: recipient's name entered by the holder; dates the share was created, expires and was revoked; date and number of views.
- Legal bases: performance of the contract for the holder's data (GDPR, Art. 6.1.b); for the recipient's name, as the recipient is a third party not party to the contract, the legitimate interest of the customer and of AttackScout in keeping a record of the share (Art. 6.1.f).
- Recipient: the third party chosen by the holder only sees the grade, the date and level of the latest audit, the number of failing checks, the date of the proof of ownership and the link to the latest certificate; never the details of the findings.
- IP address: no IP address of the viewer is kept in the database; it only appears in the technical log, truncated, as for any request (§3.14).
- Retention: consent log until the account is deleted; shares deleted with the domain.
The recipient may request the erasure of their name at [email protected].
3.20 Integrator pilot bookings
- Data: email address, company, domain, number of domains, country, date, truncated IP address.
- Purpose: preparing the pilot requested and writing to you about it.
- Legal bases: pre-contractual steps taken at your request (GDPR, Art. 6.1.b); separately, and only if you tick a second box, not ticked by default, your consent to receive our news (Art. 6.1.a).
- Retention: an unconfirmed booking is erased 30 days after the confirmation link expires; a confirmed booking is kept until the pilot starts, for 12 months at most.
- Processor: Cloudflare (D1 database), for the booking page of the showcase website; the data is stored in the European Union.
- Your rights: write to [email protected] (see also section 6).
3.21 Prospecting integrators by email
- Data: company name and domain, country, legal form, generic business email address (contact@, info@, sales@…) collected automatically from the public pages of the company's website, with a filter that discards any address that looks like a person's name; address of the source page; dates and number of messages.
- Basis: legitimate interest (GDPR, Art. 6.1.f). We apply the rules of the recipient's country (for example Article L34-5 of the French Postal and Electronic Communications Code, the PECR in the United Kingdom, the CAN-SPAM Act in the United States).
- Limits: no sending to Spain or to a personal address; 3 messages at most.
- Scoring: an AI processor (Anthropic) scores prospects from anonymous technical criteria (sector, size, country, grade and number of findings of the public audit, recognized CMS and hosting provider), without name, domain or address. The result, a score and a short sentence, is kept with the prospect's record (13 months).
- Processor: Brevo, which sends the messages from our sending subdomain (see the "Sub-processors" page).
- Personal follow-up: we may mark your company as "in personal follow-up". It then leaves the automatic sequences and we write to you ourselves, one message at a time, at the same generic address, after checking the objection register and the rules of your country. We keep the mark (domain name, date, author) for 13 months, with the record. Your right to object is unchanged.
- Objection: a one-click link in every message, with immediate effect. We then keep only the domain name, in the objection register.
- Retention: the record and the decision log are deleted 13 months after the last contact; objection register (domain name only), without time limit.
3.22 WordPress and PrestaShop extensions
When an administrator clicks "Run the audit", the extension sends AttackScout the website's domain name and its API key (Authorization header), nothing else. The extension's links to attackscout.com carry utm parameters (source wordpress or prestashop) that contain no identifier of the website or of the person.
3.23 Automated assistant
The assistant answers your questions about the service. Its answers are automated AI answers, which may be wrong; the assistant says so with the notice "automated AI answer, which may be wrong".
- Data sent: the text you type, at most the 6 previous turns of the conversation, the domain being viewed if there is one, and excerpts from our pages. Email addresses, IP addresses and numbers are masked before sending. No account, no IP address and no audit result is sent.
- Basis: legitimate interest in helping you use the service (GDPR, Art. 6.1.f).
- Processor: Anthropic (United States), through its Messages API, with the Claude Haiku model; transfers safeguarded by the standard contractual clauses (see section 5). API data is not used to train the models. It is deleted by Anthropic within 30 days, except as provided otherwise in its terms (in particular longer retention in the event of a breach of its usage policy) (as of November 17, 2026).
- Retention on our side: no question or answer is kept; only anonymous daily counters.
3.24 Free portfolio review for an agency
An agency may request a free review of its clients' domains: it is a level A public audit (what a visitor sees), without proof of ownership (terms of sale, Art. 21.3).
- Declaration: by ticking a box that is not pre-ticked, the agency declares: "I confirm that I am authorized by my clients to have their domains audited." We keep proof of this declaration (date, truncated IP, version of the text).
- Basis: the portfolio audit relies on legitimate interest (GDPR, Art. 6.1.f), like the public audit (§3.1): the same public data, the same level A. Proof of the declaration also relies on legitimate interest.
- Exclusion: a domain excluded at its holder's request (§3.9) is never audited.
- Retention: per-domain summaries are kept for 90 days; proof of the declaration is kept like the proof of acceptance of the terms (§3.3).
3.25 Suggesting your other domains
For a subscribed customer, we read the public website and public DNS of its paid domain (links, legal notice, MX, SPF) to suggest adding its other domains. We only keep the suggested domain names (6 months at most), we never open the website of another domain, and no audit takes place unless the customer adds them. The customer may decline each suggestion or unsubscribe from the email.
- Basis: legitimate interest (GDPR, Art. 6.1.f).
3.26 Reminder of an abandoned payment
- Data: email address, domains being switched to paid, grade and at-risk item of the latest audit; the last domain refused beyond the 3 free domains and the last payment summary opened (first checked domain, number of domains), for a single reminder of each (24 hours and one hour later).
- Basis: pre-contractual steps taken at your request (GDPR, Art. 6.1.b), with one-click objection.
- Retention: the resume link is kept for 7 days, as a fingerprint only. The refused domain and the opened summary take up one row per account, replaced each time and deleted with the account.
3.27 A partner's "Test your website" widget
A partner (agency or integrator) may display on its website a widget that tests the domain a visitor enters: it is the level A public audit (§3.1), with no account and no proof of ownership. The widget sets no cookie and no advertising tracker.
- On the partner's behalf: if you tick the box "I agree that [the partner] receives my email address, my domain and my grade so they can contact me", the partner is the controller of that data: it contacts you under its own privacy policy, whose link appears under the box with its company name. AttackScout processes the data on the partner's behalf, as a processor (GDPR, art. 28): it collects it, sends it to the partner by email and keeps it for the partner. If the box is not ticked, nothing is passed to the partner.
- Data: email address, domain tested, grade, language, date of your agreement, version of the text shown, truncated IP address (never the full address).
- Basis: your consent (GDPR, art. 6.1.a), which you can withdraw at any time.
- Retention: 12 months, or until the end of the partner's contract if that comes first; when the contract ends, the contacts are erased or returned to the partner, at its choice, within 30 days.
- Your rights: exercise them with the partner, or at [email protected]; AttackScout passes your request on to the partner within 72 hours.
- No marketing by AttackScout: AttackScout never uses these contacts for its own marketing, nor for any purpose other than passing them to the partner.
- Recipients: the partner, and our processors Google Cloud (hosting), Brevo (sending the email to the partner) and Cloudflare (network and Turnstile).
3.28 Sign-in and account creation through a provider (Google, Microsoft, LinkedIn, GitHub)
You can log in, or create your account, with your Google, Microsoft (work or personal), LinkedIn or GitHub account, instead of a password or a link sent by email. Each provider is offered only if it is enabled. You choose this way of logging in yourself: nothing is sent to a provider before you click its button.
- What we ask for: Google, Microsoft and LinkedIn through OpenID Connect, with the scopes
openid email profile; GitHub through OAuth 2, with the scopesread:user user:email. We publish nothing, read neither your contacts, nor your messages, nor your files, nor your repositories, and access nothing else than the identity described below. The provider's access token is used once, during the login, and is never stored. - Data received from the provider: the user's unique identifier at that provider, your email address and whether it is verified, your name (profile). Microsoft also sends the identifier of your organization (tenant), read only to verify the address and not stored. GitHub sends your identifier, your username and your name, and the list of the email addresses of your account: we keep only the verified primary address.
- Data stored: the provider, your identifier at that provider, the email address received when the provider was linked, the date it was linked and the date of the last login. Your name is not stored.
- Temporary data: during the login, a state value, a nonce and a PKCE verifier; at the first login, the identity waiting for you to accept the terms. They are kept for 10 minutes at most for the round trip to the provider, 15 minutes at most to complete the sign-up, then erased.
- Verified address required: an existing account is linked to a provider only if the address is verified at the provider and in AttackScout; otherwise, the login is refused.
- First login: the same box as for sign-up by email (chosen profile and acceptance of the terms of use, the terms of sale and the privacy policy) remains mandatory, with the same proof (version of the texts, date, truncated IP, see §3.3); the account is created only afterwards. The language of the page is recorded as the language of the account.
- Basis: performance of the contract or pre-contractual steps taken at your request (GDPR, Art. 6.1.b), because you choose this way of logging in yourself; proof of acceptance: legitimate interest (Art. 6.1.f).
- Retention: as long as the account exists; the stored data is erased with it (account deletion or deletion for inactivity, according to the periods in §3.3). Temporary data: see above.
- The providers are not our processors: they provide, under their own terms and as independent controllers, the identity service you choose. AttackScout entrusts them with no processing on its behalf and sends them no personal data (only the application identifier, the return address and random security values). Their processing of your data is governed by their privacy policy: Google https://policies.google.com/privacy ; Microsoft https://privacy.microsoft.com/privacystatement ; LinkedIn https://www.linkedin.com/legal/privacy-policy ; GitHub https://docs.github.com/site-policy/privacy-policies/github-general-privacy-statement.
- Cookie: the
__Host-attackscout_oauthcookie, strictly necessary for the security of the login, is set only when you click a provider login button (see the cookie policy).
3.29 Bounces and complaints on our emails
- Data: when our sending provider (Brevo) tells us that an email was delivered, bounced, was reported as unwanted, or that its recipient unsubscribed, we keep the type of the event, its date and the fingerprint of the address (never the address itself, nor the subject or content).
- Purpose and basis: keep good deliverability, stop writing to an address that no longer exists or that complained, and honour an unsubscription (legitimate interest, GDPR, Art. 6.1.f; objection honoured by design). An unsubscription reported by Brevo has the same effects as the unsubscribe link in our emails; service emails (sign-in link, alerts, invoices) continue.
- Pause of sending: when, over 7 days, the share of our emails that bounce or are reported as unwanted exceeds a threshold we set, our prospecting and marketing emails (newsletter, conversion reminders) pause by themselves; we resume them by hand only. The log keeps the date, who resumed and the rates (no address). Service emails continue.
- Retention: events are kept for 90 days; the fingerprint of an address with a permanent bounce or a complaint is kept for 3 years, so that we never write to it again; the log of pauses and resumptions, 13 months.
3.30 "Send to my provider": email to a client's provider
A signed-in client who follows a domain can have the result of that domain's public audit sent to their provider (agency, integrator, hosting company): they enter the provider's email address and AttackScout sends a single email with a private link to that result. The client triggers the sending, not AttackScout: the email contains no offer. The page it opens then offers, with no obligation, the partner program and a pilot; from 3 onwards, it also shows how many other clients have named the same provider.
- Who decides: AttackScout is the controller of the provider's address, to send this email at the client's request and to keep the unsubscribe list.
- Data: the provider's email address, entered by the client, used for the time of the sending and not kept; the client's optional message (300 characters at most, no link or address), attached to the email and not kept; SHA-256 fingerprints (never the plain values) of the domain of the provider's address (of the whole address for a consumer mailbox such as Gmail), of the client's domain and of the shared result, with the date and language of the sending; if the provider unsubscribes, the provider's fingerprint and the date. A fingerprint is a pseudonym, not anonymity: it remains personal data.
- Purposes: send the email the client asked for; send only one email per provider and per result, limit sends per account and per day, honor unsubscribes and opposition lists; show the provider, on the welcome page the email opens, how many other AttackScout clients have named them, aggregated and anonymous, only from 3 onwards (never a name, a domain or a fingerprint).
- Legal bases: for the provider, the legitimate interest of AttackScout, the client and the provider in the client being able to pass on their result (GDPR, Art. 6.1.f), with these safeguards: sending triggered by an identified client who follows the domain, a single email, no offer in the email, no open or click tracking, one-click unsubscribe with immediate effect; for the client, performance of the contract (Art. 6.1.b).
- What the provider sees: only the public result the client chose to share, that is, what anyone can see from the internet, through a private link, never indexed, valid for 30 days and which the client can withdraw. Never a full audit, any data from the client's account or any data from another client.
- Objection and unsubscribe: the "Unsubscribe" link in the email, one click, immediate effect. An unsubscribed provider no longer receives emails of this kind, neither at that address nor on its domain. We also honor the opposition and suppression lists that already exist (addresses with a hard bounce or a complaint, domains that objected to any prospecting or are excluded from prospecting, §3.21 and §3.29). The client is not told that an address is on a list.
- Retention: the address is not kept; the sending fingerprints, 13 months, then automatic deletion; the unsubscribe (fingerprint and date), as long as needed to honor it, lifted on the provider's written request; the shared result and its link, 30 days (§3.1).
- Recipients: our processors Brevo (sending the email), Google Cloud (hosting) and Cloudflare (network and Turnstile). AttackScout never uses this address for its own prospecting or for any other purpose.
- Your rights: write to [email protected], from the address concerned, since we do not keep it: we then find its fingerprint. No automated decision is made about you.
3.31 Withdrawal by a private individual
- Persons: private customers (consumers) who withdraw from the contract (terms of sale, Art. 24).
- Data: name entered in the notice, billing email, contract reference (invoice of the first payment), date of conclusion and date of the notice, amount refunded and currency; the acknowledgement of receipt sent by email.
- Purposes: carry out the withdrawal (refund, end of the subscription) and keep proof of it.
- Bases: legal obligation (consumer law, Royal Legislative Decree 1/2007, Arts. 102 to 108; GDPR, Art. 6.1.c); proof: legitimate interest (Art. 6.1.f).
- Retention: 6 years from the end of the year of the notice, like the corrective invoices that go with it, even after the account is deleted, then deletion.
4. Recipients
- Processors: the up-to-date list, with their role, country and the safeguard for each transfer, is published on the "Sub-processors" page.
- Other recipients: our gestor (accounting and tax), the tax authorities, authorities and courts upon legal request.
- Identity providers (Google, Microsoft, LinkedIn, GitHub): they are neither recipients nor processors, see §3.28.
- We do not sell or rent your data.
5. Transfers outside the European Economic Area
Our data is hosted in the European Union (Google Cloud, region europe-west1, Belgium). Some processors are established in the United States (Cloudflare, Anthropic, Discord). Cloudflare, Inc., which carries public traffic, is certified under the EU-U.S. Data Privacy Framework: the transfer relies on the European Commission's adequacy decision of July 10, 2023 (GDPR, Art. 45; Implementing Decision (EU) 2023/1795), supplemented by the Commission's standard contractual clauses incorporated in Cloudflare's data processing agreement. Other transfers rely on an adequacy decision or on the Commission's standard contractual clauses (GDPR, Art. 46.2.c; Implementing Decision (EU) 2021/914), as stated on the "Sub-processors" page. You may request a copy at [email protected].
6. Your rights
You may request access to your data, its rectification, its erasure, the restriction of processing, its portability, and object to processing based on legitimate interest or to prospecting (GDPR, Art. 15 to 21). You may withdraw consent at any time, without affecting what was done before (Art. 7.3).
- How: from your account (self-service export and deletion) or by email to [email protected]. We may ask you to prove your identity.
- Time limit: one month, extendable by two months for a complex request; we will let you know (GDPR, Art. 12.3).
- Limits: we keep what the law requires (invoices) and what serves our defense (authorization log), blocking this data (GDPR, Art. 17.3.b and 17.3.e; LOPDGDD, Art. 32).
- Account deletion: it stops the subscription, deletes your customer record at Mollie (which revokes payment mandates), your newsletter subscription (§3.17) and your data at our other processors, subject to legal retention. Database backups are replaced on a rolling basis within 7 days.
- Complaint: you may contact the Spanish Data Protection Agency (AEPD), C/ Jorge Juan 6, 28001 Madrid, www.aepd.es (GDPR, Art. 77), or the authority of your country of residence.
7. Security
Encryption in transit and at rest, a database with no public address, an administration console protected by Cloudflare Access and two-factor authentication, least privilege, logging, daily backups and exports of the database kept for 7 days at most, regular updates (GDPR, Art. 32). In the event of a data breach presenting a risk, we notify the AEPD within 72 hours, and the people concerned if the risk is high (GDPR, Art. 33.1 and 34).
8. Minors
The service is intended for businesses, professionals and adult private individuals. It is not intended for minors.
9. Changes
We date each version of this policy. If a change alters how we use your data, we notify account holders by email before it applies.