Cookie policy
Version 0.1.0, November 18, 2026.
Cookie policy
1. In short
AttackScout uses no advertising cookies, no audience measurement cookies and no third-party trackers. The only items stored in your browser are strictly necessary for the service you request: staying logged in, logging in through a provider, protecting against bots, making a few steps of the website work (section 4). That is why the website shows no consent banner.
2. The rule
Spanish law requires consent, after clear and complete information, to store or read information on a user's device (Law 34/2002, LSSI-CE, Art. 22.2; Directive 2002/58/EC, Art. 5.3).
It does not require it for technical storage or access whose sole purpose is to transmit a communication, or which is strictly necessary to provide a service expressly requested by the user (LSSI-CE, Art. 22.2). The Spanish Data Protection Agency (AEPD) places in this category, among others, session cookies and those used for the security of the requested service (AEPD, Guía sobre el uso de las cookies).
The rule does not only cover cookies: it also covers the browser's local storage and other techniques that read information on the device (guidelines of the European Data Protection Board on the technical scope of Article 5.3 of Directive 2002/58).
3. Cookies
| Name | Set by | Where | Purpose | Duration | Why it is exempt |
|---|---|---|---|---|---|
__Host-attackscout_session | AttackScout | Customer account, after login | Keeping you logged in | 14 days, or until logout | Strictly necessary for the requested service (login) |
__Host-attackscout_oauth | AttackScout | Login and sign-up pages, when you click a provider login button (Google, Microsoft, LinkedIn, GitHub) | Login security: linking the provider's return to the browser that requested it, against forgery and replay; random value with no personal data; HttpOnly, Secure, SameSite=Lax | 10 minutes during the round trip to the provider; at the first login, replaced by a cookie of the same name lasting 15 minutes at most to complete the account creation; erased as soon as it ends | Strictly necessary for the service expressly requested (LSSI-CE, Art. 22.2; Directive 2002/58/EC, Art. 5.3) |
Cloudflare security cookies (for example __cf_bm, cf_clearance) | Cloudflare, for AttackScout | All pages, depending on traffic | Telling humans from bots, blocking abuse | Set by Cloudflare: 30 minutes for __cf_bm, the validity period of a passed challenge for cf_clearance | Security of the requested service |
| Cloudflare Turnstile | Cloudflare, for AttackScout | Audit, sign-up and opt-out forms | Checking that a person, not a bot, submits the form | The time of the check | Security of the requested service; no advertising |
CF_Authorization, __Host-attackscout_console_mfa | Cloudflare Access, AttackScout | Administration console only | Access control and two-factor authentication of the administrator | 8 hours | Strictly necessary; do not concern visitors |
4. Technical storage in the browser
The website also keeps some technical information in the browser's storage. None of it contains personal data, none is used to track you, and none is read by a third party. Any new information of this kind will be added to this list before it is used.
| Purpose | Type of storage | Duration | Why it is exempt |
|---|---|---|---|
| Avoiding a reload loop after a website update | Tab storage (sessionStorage) | Erased when the tab is closed | Strictly necessary to display the requested website |
| Finding the payment in progress when returning from Mollie's checkout page | Tab storage (sessionStorage) | Erased on return, or when the tab is closed | Strictly necessary for the requested payment |
| Not suggesting a password again until the tab is closed, after "Later" | Tab storage (sessionStorage) | Erased when the tab is closed | Linked to the requested login |
| Knowing that a session was opened in this browser, to show "My account" instead of "Log in" | Local storage (localStorage) | Erased at logout or when the session expires | Linked to the requested login |
| Knowing that a sign-up was just requested, to show the right page when the link is opened | Local storage (localStorage) | Erased when the session opens | Linked to the requested sign-up |
| Remembering the interface language | Local storage (localStorage) | Until a language change or until you erase it | Customization chosen by the user |
| Not showing the "deadline between two audits" banner of a domain for 30 days, after "Hide" | Local storage (localStorage), key attackscout.bandeauSurveillance: technical identifier of the domain and date it was hidden, never sent to our server | 30 days, or until you erase it | Necessary for a feature you requested (clicking "Hide") |
Nothing else is stored or read in your browser: no IndexedDB, no browser fingerprinting.
5. How we do without trackers
Audience measurement. We count visits and journey steps from the requests our server already receives (page requested, language, referrer, browser type), without storing or reading anything in your browser. No IP address is recorded, even truncated.
Counting visitors. To count distinct visitors over a day, the server computes a pseudonym from the date, the truncated IP address and the browser type, with a secret key. This pseudonym changes every day, is never stored in your browser, does not allow the IP address to be recovered and is never matched with another website. This measurement, with no cookie or identifier in the browser, is exempt from consent (LSSI-CE, Art. 22.2).
Page tests. If we compare two versions of a page, the version shown is chosen without cookies or browser storage.
Referrals and campaigns. The referral code (ref) and campaign parameters (utm_*, gclid) are read from the page address, kept in the page's memory during the visit, and attached to the account at sign-up. No cookie or storage keeps them: reloading the page loses them.
Customer badge. The badge image displayed on a customer's website is served without cookies, and the IP address of its visitors is not recorded.
A partner's "Test your website" widget. The widget sets no cookie and no advertising tracker. To check that a person, not a robot, is submitting the form, it uses Cloudflare Turnstile, like the site's forms (see the table above: security of the service requested; no advertising).
No other embedded third-party service: apart from Cloudflare Turnstile on forms, no script, font, video, map, social media button or advertising script is loaded from another domain. On public pages, the language is chosen by the address (/fr/, /en/, /es/, /de/, /it/, /pt/).
6. If this changes
If we ever add an item that is not strictly necessary, we will only do so after your consent, with a "Reject" button as visible as "Accept", and we will update this page beforehand.
7. Controlling cookies and storage
You can delete or block the website's cookies and storage in your browser settings. Without the session cookie, you will not be able to stay logged in; without the security items, some forms may refuse submission.
8. Contact
[email protected] · See also the privacy policy.