Updated
Spain's data protection authority issued 299 sanctions totalling around €40 million in 2025. Cookie failures are among the easiest to detect, the cheapest to prevent, and the ones foreign marketing teams most reliably import from a home market where the rules are looser.
A company selling into Spain from abroad usually arrives with a consent banner that was designed for a different legal culture: a notice bar, an "accept" button, analytics already running, and a "we use cookies to improve your experience" line. In Spain that configuration is not a soft compliance gap. It is the specific pattern the supervisory authority looks for, and the one that generates fines.
Two instruments govern this. The LSSI-CE — the Spanish law on information society services and electronic commerce — requires site operators to identify themselves and to inform users about cookie use. The GDPR supplies the consent standard. The AEPD enforces both, and publishes guidance on what an acceptable banner looks like.
The requirement is narrower than most imported banners assume, and it is testable from outside: a regulator, a competitor or a complainant can open the site and observe whether trackers fire before any interaction.
If Google Analytics or an advertising pixel loads on arrival, the breach is already complete and observable. If "Accept all" is a button and "Reject" requires opening preferences, the consent obtained is treated as not freely given. Both are visible from the outside in under a minute.
| Practice | Common outside the EU | Position in Spain |
|---|---|---|
| Analytics on page load | Standard | Breach — requires prior consent |
| Notice-only banner | Often sufficient | Insufficient — notice is not consent |
| "Accept" prominent, "Reject" hidden | Widespread | Consent not freely given |
| Implied consent by scrolling | Historically accepted | Not valid |
| Single global privacy policy | Normal | Acceptable only if it meets EU content and language expectations |
| No legal identification on site | Common for brand sites | LSSI requires name, NIF, address and contact |
| Consent records not retained | Frequent | Must be demonstrable on request |
Marketing teams reasonably worry that a compliant banner destroys measurement. The workable answer is a consent management platform wired to a consent-mode implementation: tags load in a denied state by default and update only when the user agrees, so nothing personal is collected pre-consent while modelled reporting still functions.
Site identification under LSSI, a compliant consent flow, and privacy and cookie documentation that match how your site actually behaves. Cheap before launch; expensive to reconstruct afterwards.
Generally yes. GDPR reaches processing connected to offering goods or services to people in the EU or monitoring their behaviour, regardless of where the controller is established. A US or UK company running a Spanish-language site, advertising to Spanish users and measuring their behaviour is within scope — and being outside Spain does not make the site harder for a regulator or a complainant to inspect.
Establishment is one route into scope, not the only one. Targeting and monitoring bring a foreign site within the regime, and a non-EU controller may additionally face representation obligations.
One compliant consent implementation serving all EU traffic is cheaper than maintaining divergent versions and far cheaper than remediation after a complaint.
Unofficial translations of the BOE consolidated texts, with the articles named on each page. All of them are in our library of Spanish laws in English.
Describe what you are building. We reply with the structure we recommend, a timeline with real dates and a fixed fee that does not change once we start.