- Should you really worry about this case, or is it only about big banks?
- What exactly happened with BBVA?
- What exactly does the law say about the right to object to marketing?
- Is this an isolated case, or is the Garante really stepping up enforcement?
- What changes in practice: who does what when an opt-out request arrives?
- Three real-world scenarios: what happens in an e-commerce store, a professional firm and a manufacturing company?
- What similar cases has the Italian Garante already penalized?
- What tools and approaches exist to handle opt-outs safely?
- Why it's in the news now: has the European landscape really changed?
- How to get started: the steps to secure your opt-out system
- What are the most common mistakes that lead to fines like this?
- How can you tell if your opt-out system is really working?
- So, is it worth investing in an opt-out system audit now?
- How we see it at SHM
- Frequently Asked Questions
- The Italian Garante fined BBVA €5,508,000 because a technical failure prevented synchronization between internal systems and the CRM that sent the marketing communications.
- Under the GDPR, the right to object to direct marketing is absolute: the controller must stop everything immediately, regardless of the channel the customer used to make the request.
- The Garante's fines are growing fast: €37.7 million collected in 2025 (+54.5% vs. 2024) and already €83.7 million imposed in 2026. Waiting doesn't pay.
- An opt-out system audit, mapping the flows between your CRM and contact channels, and regular testing are the three concrete steps to avoid ending up in the same situation.
One customer who couldn't turn off a bank's promotional notifications. Seven months of waiting, ten unwanted messages, and in the end a €5.5 million fine.
Should you really worry about this case, or is it only about big banks?
The BBVA case concerns anyone who does direct marketing: email, SMS, push notifications, phone calls. The logic behind the fine applies to any company that collects data and sends marketing communications.
The €5,508,000 fine against the BBVA banking group isn't a story about banks. It's a story about systems that don't talk to each other. And that problem exists in any company that uses a CRM (the software that manages contacts and customer communications) separate from the channels where customers make their requests.
The Italian data protection authority found a simple violation: a customer had asked to stop receiving promotional messages, but for seven months the messages kept coming. The cause? A technical misalignment between the bank's internal systems. The consequence? A penalty of over five million euros.
This pattern, an opt-out that is recorded but not carried out, is far more common than you might think, even among SMEs and mid-sized companies.
| Your situation | Concrete risk | why |
|---|---|---|
| You use a CRM separate from your website or app | High | An opt-out recorded in one system might not reach the other |
| You have multiple marketing channels (email, SMS, push, phone) | High | Every channel must receive and honor the objection |
| Customers can only opt out through a dedicated email address | High | The Garante rejected this defense: any valid channel is enough |
| You have a single integrated system with request logs | Low | The risk exists but is easier to control with periodic audits |
| You don't do direct marketing to contact databases | Very low | Art. 21 GDPR applies only to processing for direct marketing |
What exactly happened with BBVA?
A customer exercised the right to object to marketing through the app and then through customer service. For seven months they kept receiving promotional notifications because of a technical failure in the bank's systems.
The customer had used the BBVA app settings to block marketing communications. They then contacted customer service again to repeat the request. The bank had recorded the choice, but a technical problem prevented synchronization between the internal systems and the CRM responsible for sending the messages.
From October 2025 to May 2026, the customer received at least ten unsolicited marketing notifications. The Garante also found another irregularity: customer service had told the customer that push notifications in the app couldn't be disabled. That wasn't true, as the bank itself later showed they could be stopped.
BBVA's defense rested on one argument: the customer should have used the email addresses listed in the privacy policy. The Garante rejected this argument without hesitation. Those who handle data must make it easy to exercise rights, not get in the way by requiring specific channels.
| Case element | Details |
|---|---|
| Company fined | BBVA (Italian branch of the Spanish banking group) |
| Duration of the violation | 7 months (October 2025 – May 2026) |
| Unwanted messages received | At least 10 marketing notifications |
| Technical cause | Failed synchronization between internal systems and the CRM |
| Fine | €5,508,000 |
| GDPR articles violated | Art. 5(1)(a), Art. 12, Art. 21, Art. 24 |
| Aggravating factor | Relevant prior infringement |
| Mitigating factor | Corrective measures taken by BBVA |
The Garante also ordered BBVA to adopt appropriate technical and organizational measures and to report the actions taken within 30 days. Paying the fine isn't enough: you have to prove you've fixed the problem.
What exactly does the law say about the right to object to marketing?
Article 21 of the GDPR states that anyone who receives a request to object to direct marketing must stop sending communications immediately, with no exceptions and no balancing of interests.
The GDPR, the European data protection regulation, provides for two types of right to object. For most processing, the controller can continue if it shows overriding legitimate grounds. For direct marketing, there is no such option: the objection is absolute.
This means that as soon as a customer says "I don't want to receive marketing messages anymore," processing must stop. Not after a week, not after checking which channel was used, not after consulting a lawyer. Immediately.
The penalty for breaching this obligation falls in the highest tier under the GDPR: up to €20 million or 4% of annual worldwide turnover, whichever is higher. In the BBVA case, the fine took into account that the violation affected just one person, but it lasted seven months and there was already a prior offense.
Is this an isolated case, or is the Garante really stepping up enforcement?
The numbers show a clear trend: fines issued by the Italian Data Protection Authority grew by 54.5% in 2025 compared with 2024, and in 2026 the pace is even faster.
The BBVA case is not an isolated incident. Last year the Authority fined Verisure Italia €400,000 in an almost identical case: a former customer kept receiving promotional text messages after exercising the right to object. In July 2026 it was Altroconsumo Edizioni's turn, fined €280,000 for violations related to email marketing and delays in responding to user requests.
The pattern is the same: opt-outs ignored or handled late, systems out of sync, incorrect information given to customers. And the fines keep growing.
In 2025 the Authority issued 229 administrative fines and 506 corrective measures overall, with 130 inspections: 78 carried out directly and 52 delegated to the Guardia di Finanza. The data is published in the 2025 Annual Report of the Italian Data Protection Authority.
In 2026 the pace is even higher: according to tracking updated to October 2026, the Authority has already imposed 166 fines totaling €83.7 million, with a single maximum fine of €31.8 million. The most affected area is privacy notices (50 cases), but direct marketing is among the most closely monitored areas.
"Insufficient technical and organizational measures", exactly BBVA's problem, is the third most penalized category in Europe, with 418 proceedings. The average fine for this category is €2 million, according to the CMS Law GDPR Enforcement Tracker Report.
What changes in practice: who does what when an opt-out request arrives?
Handling an opt-out correctly requires three different business functions (IT, customer service and marketing) to be aligned, with a written process and clear responsibilities.
- 1 · CustomerSends the opt-out requestVia app, email, phone, web form or any reasonable channel. Under the GDPR, every channel is valid.
- 2 · Customer Service / SystemLogs the request with a timestampThe date and time of the request must be tracked. The deadline to respond is one month (Art. 12 GDPR).
- 3 · IT / SystemsPropagates the opt-out to all systemsCRM, email platform, SMS system, push notifications, call center: all must receive the block in real time or close to it.
- 4 · MarketingChecks that communications have stoppedActively verify that no automated flow is still sending messages to the blocked contact.
- 5 · DPO / ComplianceArchives the documentationProof of the opt-out, execution date, updated systems. You need it in case of an inspection or complaint.
The critical point is step three: propagation to all systems. BBVA had recorded the customer's choice, but the data never reached the CRM. That is the failure behind the €5.5 million fine. In companies with multiple marketing tools, and today almost all have at least three or four, this risk is structural unless it is carefully managed.
Three real-world scenarios: what happens in an e-commerce store, a professional firm and a manufacturing company?
The risk changes with the number of channels used and the complexity of the systems, but the principle is the same: every system that sends commercial communications must receive and respect the opt-out.
Illustrative examples: the numbers and situations are meant to show the reasoning, they are not real customer data.
| Company type | Typical marketing channels | Main risk | Priority action |
|---|---|---|---|
| E-commerce (e.g. fashion, electronics) | Email, SMS, app push, remarketing | CRM and email platform out of sync after opt-out | Audit the opt-out flow across all systems; monthly test with a dummy contact |
| Professional firm (e.g. consulting, law) | Email newsletters, sales calls | Opt-out recorded by hand with no automated system | Adopt a CRM with built-in opt-out management and request logs |
| Manufacturing company with a sales agent network | Email, agent calls, trade fairs | Agents are not informed of the customer's opt-out | Written procedure: every opt-out is notified to the local agents within 24 hours |
What similar cases has the Italian Garante already penalized?
The Authority has already fined several companies for unwanted marketing after an opt-out: the Verisure and Altroconsumo cases show that the tolerance threshold is very low.
| Company | Fine | Main violation | Source |
|---|---|---|---|
| BBVA (Italian branch) | €5.508.000 | Opt-out ignored for 7 months, systems out of sync | EDPB, Oct. 2026 |
| Altroconsumo Edizioni | €280.000 | Email marketing, delayed response to user rights requests | Italian DPA, July 2026 |
| Verisure Italia | €400.000 | Promotional text messages after a former customer's opt-out | Italian DPA, Dec. 2025 |
The difference between BBVA's fine and those of the other two companies depends on several factors: company size, the presence of a prior offense, the length of the violation. But the principle is identical. As we saw in our analysis of the €825 million Uber fine for automated decision-making, European authorities are enforcing the rules with growing rigor, including against companies of every size.
What tools and approaches exist to manage opt-outs safely?
There are different technical solutions, from the simplest to the most structured: the right choice depends on the number of channels you use and the complexity of your CRM.
| Approach | Suitable for | Benefit | Limit |
|---|---|---|---|
| Single CRM with built-in opt-out management (e.g. HubSpot, Salesforce) | Companies with 1-3 marketing channels | Automatic synchronization, request logs | License cost, data migration |
| Synchronization middleware (e.g. Zapier, Make) | Companies with multiple non-integrated tools | Connects different systems without changing the CRM | Requires setup and periodic testing |
| Consent Management Platform (CMP) | E-commerce and high-traffic websites | Manages consents and opt-outs across all web channels | Does not cover offline channels (phone, agents) |
| Manual process with a paper/Excel register | Professional firms with few contacts | No technology cost | High risk of human error, not scalable |
| External audit + written procedure | Any company, as a starting point | Identifies gaps before the Authority does | Doesn't fix technical problems, it maps them |
Why it's in the news now: has the European landscape really changed?
European data protection authorities issued €1.145 billion in GDPR fines in 2025, bringing the cumulative total since 2018 to more than €7 billion. The pace of enforcement isn't slowing down.
The BBVA case comes at a time when GDPR enforcement, meaning the actual application of penalties, has reached record levels. According to the EDPB 2025 annual report (the European Data Protection Board), national authorities imposed €1.145 billion in fines in 2025 alone. Since 2018, the total exceeds €7.1 billion across more than 2,800 proceedings.
This isn't a trend that will stop. Authorities have more resources, more experience and more precedents to draw on. If you handle marketing data without a verified opt-out system, you face a real risk, not a theoretical one. The issue also overlaps with the new AI rules: as we discussed in our article on AI and compliance in ad campaigns, the default settings of automated systems are coming under ever closer scrutiny from the authorities.

How to get started: the steps to secure your opt-out system
The starting point is a flow audit: map where opt-out requests arrive and verify that they actually reach every system that sends commercial communications.
You don't need to start from scratch. You need to find where the gaps are. Here's a six-step path, suitable even if you don't have a dedicated IT team.
- 1 · Marketing + ITMap all active marketing channelsEmail, SMS, app push, phone calls, trade shows, agents. List every channel that sends commercial communications.
- 2 · IT / CRM ManagerCheck that every channel receives the opt-outTest with a dummy contact: opt out from one channel and check whether the block reaches all the other systems.
- 3 · Customer ServiceTrain the team to handle verbal requestsA phone call or a chat message is a valid request. The team must know how to record it and propagate it.
- 4 · DPO / LegalUpdate the privacy policy with the accepted channelsYou can't limit opt-out to a single channel. The policy must reflect reality, not the channel the company prefers.
- 5 · IT / MarketingSet up an automatic request logDate, channel, system updated, execution date. This log is your defense in case of an inspection.
- 6 · Compliance / ManagementSchedule a quarterly system testA technical failure like BBVA's can surface at any time. Regular testing catches it before the Garante does.
What are the most common mistakes that lead to fines like this?
BBVA's technical failure is only one of the ways companies end up facing penalties: organizational and process errors are just as common.
| Common mistake | Why it is risky | How to avoid it |
|---|---|---|
| Opt-out recorded only in the main CRM, not propagated to other systems | The customer keeps receiving messages from channels that weren't updated | Automatic synchronization or a monthly manual test |
| Customer service saying 'it's not possible to disable X' | False information that aggravates the violation (as in the BBVA case) | Specific training and updated scripts for the team |
| Opt-out valid only if made through a dedicated email address | The Garante rejected this defense: any reasonable channel is valid | Accept and record requests from any channel |
| No log of opt-out requests | Impossible to prove you honored the request in case of an inspection | Logging system with timestamps and execution status |
| Automated marketing flows not updated after opt-out | Automations keep sending messages even after the block | Include the opt-out check as a condition in every automated flow |
A related topic worth keeping an eye on is the EU regulation on AI in content: there too, technical responsibility falls on the data controller, not on the tool provider.
How can you tell if your opt-out system is really working?
There are concrete indicators that let you check how well the system works before a complaint or an inspection arrives.
| Indicator | How to measure it | Alert threshold |
|---|---|---|
| Average opt-out execution time | From the moment of the request to the block across all systems | Over 24 hours is a risk; over 72 hours is a potential violation |
| Complaint rate for unwanted marketing | Complaints received / contacts in database | Any repeated complaint from the same contact is a warning sign |
| Request log coverage | % of opt-outs with a timestamp and documented status | Below 100% means some requests aren't being tracked |
| Periodic test result | Dummy contact that opts out: how many systems receive it? | Any system that doesn't receive the block is a gap to fix |
| Customer service training | % of the team trained in handling rights requests | Below 100% means someone might give incorrect information |

So, is it worth investing in an opt-out system audit now?
Worth it if you do direct marketing across multiple channels (email, SMS, push, phone) and have never verified that opting out on one channel also blocks the others. The risk is real, and the cost of an audit is a fraction of any fine.
Somewhere in between: you use a single marketing channel with an integrated system, but you've never tested the flow end to end. A quick test and a written procedure are enough to let you sleep easy.
Not yet if you don't do direct marketing to contact databases and don't send unsolicited commercial communications. Art. 21 GDPR doesn't apply to your specific case, but it's worth checking with your DPO.
How we see it at SHM
For us, the BBVA fine says something we often see: digital systems grow by accumulation. You add a CRM, then an email platform, then an app, then an automation tool. Nobody checks that they talk to each other when it really matters, which is when a customer wants to stop everything.
We believe technology should serve people, not create obstacles. An opt-out system that doesn't work isn't just a legal problem: it's a sign that the company's digital architecture needs attention. And that's true for marketing as for any other automated process.
If you want to understand where the gaps are in your consent and commercial communications management, we can help with a structured audit. We work on the strategic integration of digital systems, on data flow mapping and on training teams in automation and business processes. You can find more insights on digital regulation and technology in the Project management and technology section.
The topic of digital compliance also ties in with the EU fine on Meta under the DSA and with European digital sovereignty: they're all signs of the same regulatory direction.
Frequently Asked Questions
You must stop all marketing communications immediately, on every channel. You can't limit it to one system or require the request to come through a specific channel. Under the GDPR, any reasonable request is valid: email, phone, app, web form.
For direct marketing, Art. 21 GDPR doesn't set an explicit deadline but requires processing to stop 'immediately'. Art. 12 GDPR sets a one-month deadline for formally responding to the request, but the block on communications must happen sooner.
No. The Italian Garante explicitly rejected this defense in the BBVA case: the data controller must facilitate the exercise of rights, not hinder it. Whether the customer makes the request through the app, by phone or by email, all requests are valid.
Yes. Art. 24 GDPR establishes that the data controller is responsible for adopting appropriate technical and organizational measures. A technical failure is not a valid excuse: it's proof that the measures adopted were not sufficient. That's exactly why BBVA received the fine.
A violation of Art. 21 GDPR falls into the highest penalty tier: up to €20 million or 4% of annual worldwide turnover, whichever is higher. In the BBVA case, the fine was €5.5 million for a violation involving a single customer that lasted seven months.
The simplest way is a hands-on test: create a dummy contact in your database, opt out through one channel, and check that the block reaches every other system (CRM, email platform, SMS, app). Repeat the test every three months and document the results.
The fine didn't happen because BBVA wanted to ignore its customers. It happened because nobody had ever tested whether its systems actually talked to each other.
Related articles
Discover more articles exploring similar topics, selected to offer you a more complete and stimulating perspective. Each piece of content is carefully chosen to enrich your experience.