Last updated: 12 November 2026
This page is for people who install Shield on their own server. It explains what Shield does with visitors' data and gives you text to add to your privacy notice.
| Data | Use | Retention |
|---|---|---|
| IP address, declared browser (user agent), page requested, time of request | Recognise waves of automated traffic and attack attempts; decide whether to let through, ask for a check or refuse | In memory, as long as the decision needs |
| Pseudonymised session records, keyed with a secret that stays on your server | Improve recognition on your site's traffic | Deleted after 14 days |
Technical cookie shield_pass | Pass after the check, so it is not repeated. Contains no personal data | 24 hours |
Shield builds no commercial profiles, does not track visitors across sites and does not use data for advertising. The browser check is automatic and asks nobody to solve images or puzzles. If Shield refuses a request by mistake, the visitor can contact you and you can let them in at once, for example by switching to observe with sudo shield mode observe.
Only if you link Shield to an account, and only aggregate data: counts, wave state, countries and network operators as totals, paths searched by attack scanners. Full list in section 5 of Luviner's privacy policy.
No. shield_pass is a technical cookie strictly necessary for the site's security; under the ePrivacy rules it needs no consent. It should still be listed in your cookie policy.
Protection of the site against automated traffic and attacks. To protect the site and its users from automated traffic, request floods and attack attempts we use Shield, software installed on our server. Shield automatically analyses the technical data of each request (IP address, browser type, page requested, date and time) to decide whether to serve it, ask the browser for a short automatic check, or refuse it. The data is processed on our server and is not disclosed to the software provider, which receives only aggregate, anonymous statistics. The legal basis is our legitimate interest in ensuring network and site security (Art. 6(1)(f) and Recital 49 GDPR). Records used to improve protection are pseudonymised and deleted after 14 days. Shield uses a technical cookie (
shield_pass, 24 hours) so the check is not repeated. If you believe you were blocked by mistake, contact us.
If you keep a record of processing (Art. 30), you can add: Purpose site security and abuse prevention. Data subjects site visitors. Data IP, user agent, requested URL, date and time. Basis legitimate interest (Art. 6(1)(f)). Recipients none. Transfers none. Retention 14 days, pseudonymised. Measures processing on own server, pseudonymisation with a local key.
This information helps you prepare your documentation but is not legal advice. For special cases ask your privacy adviser or DPO.