Italy's data protection authority, the Garante, fined Meta Platforms Ireland €805 million on 14 November 2026 over a Facebook Android feature that suggests photos from a user's camera roll. The size of the number has drawn the attention. The more useful question is what the decision actually establishes, and where it overreaches.
The strongest case for the Garante
The argument for the regulator deserves a fair statement first. A phone's photo library is among the most intimate stores of personal data most people own. The Garante's decision says Facebook asked for access through a single Android permission that covered photos and videos alongside "other functions", preceded by a non-specific notice. The feature, "Get camera roll suggestions when you're browsing Facebook", has been available since 2023 and was switched on by default. When a user grants the full-library permission, the Garante noted, the app can usually read the whole library on a lasting basis. Neither the user nor a regulator can easily verify what is actually used. The Garante also reported that the app is closed-source and its traffic encrypted, so it could not check what was transmitted. If a platform can open a door that wide with one tap, the case for requiring a separate, specific question is strong.
That is not an exotic reading of the law. The Garante proceeded under Article 122 of the Italian Privacy Code, which implements Article 5(3) of the ePrivacy Directive (2002/58/EC). That provision has long required consent for storing or gaining access to information on a user's device. Because ePrivacy has no one-stop-shop mechanism, the Garante also rejected Meta's argument that the Irish Data Protection Commission should have handled the case. On the consent question the regulator is on firm ground.
Where the decision is right
The finding that an operating-system permission is not the same as consent for a particular feature is sensible, and it is good for the open internet. A permission prompt tells the system what an app may touch. It does not tell the user what the feature will do with that access. Meta itself admitted, according to the decision, that the in-app toggle could appear active before the OS permission was granted. A default-on setting that depends on a broad permission is the kind of design that erodes user trust in every app, not only Meta's.
The remedy is also reasonable. Within 30 days Meta must report what it has done. Within 60 days it must ask for separate, feature-specific consent, explain the purpose and how to switch the feature off, and make it off by default, including for users who already granted permission. Within 90 days it must report the measures adopted. That is a clear product change that a company of Meta's size can implement.
Where the penalty overreaches
The fine is a different matter. The Garante's own decision sets limits on what it found. It did not conclude that location data was accessed, that content was transmitted or used for other purposes, or that special-category data was processed. It did not assess whether the photos were used to train AI systems, which Meta denies. Meta says the feature works on the device and reads only basic metadata such as date, time and favourite status. The Garante could not disprove that, and it said it was not required to: access without valid consent is a violation whether or not data is sent anywhere or harm occurs.
That reasoning is legally coherent, but it makes for a poor basis for the largest fine in the authority's history. The Garante put the penalty at about 0.47% of Meta's global turnover, citing the roughly 20 million affected Android users, the duration of the violation, a 2019 decision against the company and limited cooperation. Meta disputes the 20 million figure. The Garante gave some credit for changes made after the complaint but treated them as late, since they reach only users who update the app.
Proportionality matters because fines are a signal as well as a punishment. When a consent-design failure with no demonstrated misuse draws a penalty of this scale, companies learn that the safest response is to add friction everywhere. Users then face more prompts, and developers face more uncertainty about what "specific" consent requires. A graduated approach would serve the same goal: a binding corrective order with a firm deadline, and a financial penalty that rises sharply only if the company fails to comply or if evidence of onward use emerges.
What to watch
Three things will decide how much this case matters. First, Meta has said it will appeal and calls the fine disproportionate. A court review of both the jurisdiction ruling and the amount could shape how other national authorities use Article 122 against large platforms. Second, the Garante has reserved the right to examine a separate 2026 feature that processes camera roll content in the cloud. That feature raises harder questions, because content would leave the device. If it does, the case for strict scrutiny is much stronger than it is here. Third, the Garante said it would send the decision to the Irish DPC, so the interaction between ePrivacy enforcement and GDPR one-stop-shop oversight is likely to stay contested.
The lesson for policymakers is to separate the two questions the headline merges. Requiring feature-specific, opt-in consent for access to a photo library is good, proportionate regulation that protects users without hindering innovation. Pairing it with a nine-figure penalty before any harm has been shown is less defensible. Regulators will have more credibility, and companies will have more room to build useful features, if penalties follow demonstrated harm and the rules on consent are stated clearly in advance.