Skip to main content
green gradient background, "The Future of Application Security Is Already Here." and a read the report button.
A Paid Phone Line Cost One Controller EUR 100,000Data Subject Rights
4 min readFor Data Protection Officers (DPOs)

A Paid Phone Line Cost One Controller EUR 100,000

A consumer association raised concerns about video surveillance notices that directed individuals to a 902 telephone number to exercise their rights of access and objection. This number incurred charges. The Spanish supervisory authority (AEPD) found this violated Article 12(2) GDPR and fined Securitas Direct EUR 100,000.

This decision highlights how assumptions about rights channels can fail under scrutiny. Rights handling is often designed in one area (the DSAR workflow) and communicated in another (notices, signage, contracts, call scripts). The gap between them is often overlooked. Here are five myths that exist in that gap.

Myth 1: "If a free channel exists somewhere, we're covered"

Reality: A free option elsewhere doesn't excuse a notice that directs people to a paid one.

Securitas Direct had free channels on its website, but the AEPD still found an infringement because the notice specifically pointed to the 902 number. The test isn't whether a compliant path exists in theory, but what the controller actually instructed the individual to do.

Consider the data subject's perspective. They follow the instructions in front of them, not searching your website for alternatives. If the instruction costs money, it creates a barrier, and Article 12(2) requires controllers to facilitate the exercise of rights under Articles 15 to 22.

Myth 2: "Article 12 is about response deadlines and fees, not telephone numbers"

Reality: The obligation to facilitate extends beyond mere response mechanics.

Many teams interpret Article 12 as a rule about timing (one month to respond) and fees (information and actions are free, except for manifestly unfounded or excessive requests). The AEPD's decision shows the facilitation duty includes how people are told to reach you.

A chargeable number could discourage data subjects from exercising their rights. This potential chilling effect was enough for the supervisory authority to act. The issue was the design of the channel, not whether anyone was actually refused or charged.

Myth 3: "A premium-rate or non-geographic number is just a customer service detail"

Reality: When a number is designated for rights, it's a compliance issue.

Customer service teams choose numbers for operational reasons like routing and cost recovery. These choices are fine for sales and support but become a GDPR issue when the same number is used for access or objection requests.

Watch for this pattern. Channels from commercial operations may be repurposed for privacy requests without checking the cost to the caller. If your DSAR route involves a line that bills the individual, you've effectively attached a charge to a right that Article 12 says must be free.

Myth 4: "The fine was for a big, systemic failure"

Reality: The issue was with notice wording and channel choice, yet it resulted in a significant penalty.

The decision didn't describe a collapsed rights process or mass refusals. It was about notices directing people to a chargeable number. This falls under the penalties in Article 83(5)(b) GDPR, which covers data subjects' rights under Articles 12 to 22.

This is important for risk assessment. Rights-related infringements are in the upper fining bracket, regardless of how minor the defect seems internally. A single line of text on a widely deployed notice can be a significant compliance failure.

Myth 5: "We can fix it going forward and the problem disappears"

Reality: Remediation is required, with a deadline and logistical challenges.

Alongside the fine, the AEPD ordered Securitas Direct to replace, within 12 months, the notices referring to the 902 number. For a controller with real-world notices, this means reprinting, redistributing, and re-verifying materials. Updating a web page is the easy part.

If your rights instructions are on signage, stickers, contracts, packaging, or welcome packs, correction involves logistics that far exceed the effort of getting the wording right initially. A corrective order also means the supervisory authority sets the timeline, not your project plan.

What to do instead

Treat every place you instruct people on exercising their rights as an auditable asset. Here's a practical sequence for your DPO team:

  1. Build an inventory of rights touchpoints. List every notice, sign, contract clause, email footer, IVR script, and web page that mentions how to make an access, erasure, objection, or other request. Include physical materials, which are the hardest to change.
  2. Test every listed channel for cost to the individual. Check telephone numbers with your telecoms provider. Confirm whether a number is free from mobile and landline, and from abroad if you serve customers elsewhere. Postal routes and email should be free of charge to the requester in practice.
  3. Check what you instruct, not just what you offer. Review the exact wording. If a notice names a single route, that route must be free. Prefer listing several free options, such as an email address, a web form, and a postal address, so no one is funneled into a paid path.
  4. Assign ownership across functions. Customer service, marketing, legal, and facilities all produce material containing rights instructions. Make the DPO's review a required sign-off step for new notice templates.
  5. Plan for the lifecycle of printed material. Date-stamp and version notices so you can trace what's deployed where. If you ever need to correct a channel, you'll know the scale of the job.
  6. Re-audit when channels change. A provider switch, a new call center contract, or a rebrand can quietly alter the cost of a number. Add a rights-channel check to your change management process.

The lesson from this decision is procedural. Your rights process is only as compliant as the instructions people actually receive. These instructions are often written far from the privacy team unless you actively review them.

Promotional banner for the CUI buildout guide

You Might Also Like