Back to Blog

Meta, €805 Million Over Facebook's Photo Gallery: An Android Permission Is Not Consent

·9 min read
Isometric Tomato Blue illustration captioned in Italian "Meta's €805 million fine over Facebook's gallery — An Android permission is not legal consent": a smartphone showing the photo gallery with a photo-access toggle wired to different features (camera, chat, notifications), a checklist with a compliance shield and cloud servers protected by a padlock.

On 14 November 2026 Italy's data protection authority, the Garante per la protezione dei dati personali, announced an €805 million fine against Meta Platforms Ireland Limited: through the Facebook app for Android, the company accessed photos, videos and metadata stored on Italian users' smartphones without specific consent and without adequate notice. The figure will make headlines, but the point that matters to anyone who builds software is different: authorization granted to the operating system is not the same as the consent the law requires. They are two different objects — one technical, one legal — and the decision sanctions precisely the pretense that they coincide.

The case: one feature, one permission, twenty million users

The decision concerns the feature "Get suggestions from your gallery when you browse Facebook", available since 2023: while browsing, the app proposes photos and videos taken from the phone's gallery as content the user might want to post. The investigation began in July 2025 from a complaint filed by the Centro Tutela Consumatori Utenti of Bolzano and relied on a technical analysis carried out directly by the Authority.

According to the announcement, the findings line up three elements. Access to the gallery is requested through a single authorization, valid for the entire app and for features with different purposes. The request is preceded by a generic notice ("enable other features") that gives no way to understand that it also authorizes the suggestions. The feature, finally, was active by default.

Within 60 days Meta must request separate, specific consent, explaining what the feature is for, that it involves access to the gallery, and how to turn it off; it must also keep it off by default, including for users who had already granted the authorization. The company must report to the Garante within 30 days on the initiatives undertaken and within 90 days on the measures adopted. Meta has announced it will appeal: that is a statement from its spokesperson reported by the press, not content of the Authority's announcement.

Two exclusions deserve attention. The proceeding did not cover the possible use of the content to train AI systems, which Meta denies. And the Garante has reserved separate scrutiny for the feature, launched in 2026, that allows cloud processing of gallery content.

Article 122 of the Privacy Code: the device is protected before the data

The rule applied is not the GDPR. It is Article 122 of Legislative Decree 196/2003, which transposes Article 5(3) of Directive 2002/58/EC (ePrivacy): storing information on a user's device, or accessing information already stored there, is allowed only with the data subject's consent, clearly informed, unless the operation is strictly necessary to provide a service the user has explicitly requested.

It is the "cookie rule", and here lies the first lesson: it is not only about cookies. The Court of Justice clarified this in Planet49 (C-673/17): the provision protects the user's private sphere from any interference with their device, regardless of whether the information amounts to personal data, and a pre-ticked box does not constitute valid consent. The EDPB Guidelines 2/2023 on the technical scope of Article 5(3) then expressly extended the reasoning beyond cookies, to any technique that reads information from the device. The Garante draws the consistent conclusion: the smartphone is part of a person's private sphere, and access requires free, informed consent "regardless of the transmission of data or the existence of harm".

The consent required is the one defined by the GDPR (Articles 4(11) and 7): free, specific, informed, unambiguous. Each of the three findings strikes at one requirement. A single authorization covering multiple features violates specificity. The generic notice violates the information requirement. Default activation violates unambiguity, because a setting the user merely fails to change is not a positive act.

The "strictly necessary" exception still stands. Uploading a photo the user has chosen to post obviously requires reading it. Scanning the gallery to suggest content the user did not ask for is a different operation, with a different purpose: useful to the service, but not necessary to what the user actually requested.

The technical knot: Android permissions are per-app, consent is per-purpose

Android's permission model answers one question — can this app read media files? — not the question that matters legally: for what purpose? The permission is granted to the application as a whole. Once obtained, any component of the code can use it, including modules introduced in later updates and third-party SDKs. Purpose-level granularity simply does not exist at the operating-system level: it has to be built inside the app.

Over the years the platform has narrowed the scope. Up to Android 12 the relevant permission was READ_EXTERNAL_STORAGE, which opened the entire shared storage. Android 13 split it by content type (READ_MEDIA_IMAGES, READ_MEDIA_VIDEO). Android 14 introduced partial access, letting the user select individual photos and videos. Above all, the system Photo Picker lets the user choose a piece of content without the app obtaining any permission on the gallery at all. The tools to minimize access, in other words, already existed when the feature was designed: a point that weighs on the assessment of fault and that echoes, on the GDPR side, data protection by design (Article 25).

Three technical aspects deserve specific attention.

  • Persistence. The announcement notes that a blanket authorization allows reading the entire photo archive "typically on a permanent basis". It follows that the Garante's order cannot be executed by acting on the permission itself, which remains under the control of the user and the system: Meta will have to disable the feature on the application side and the server side, even on installations where the permission is still in place.
  • Metadata. A photograph carries date, time, device model and, where present, geographic coordinates. A gallery, moreover, does not contain only the user: it contains family members, minors, photographed documents, medical reports, banking screenshots. Taken together it can reveal special categories of data and involves third parties nobody consulted.
  • Verifiability. This is the Authority's most interesting finding: neither the user nor the Garante can verify which information is actually used. From the outside one observes that the app can read; what it reads, when, and whether processing stays on the device or reaches the servers can only be reconstructed through code and traffic analysis, made difficult by encryption and obfuscation. Whoever claims that processing is purely local must be able to prove it.

One last point: for users who do not update the app, the violation, according to the Garante, is still ongoing. Fragmentation of installed versions is a well-known technical fact; the decision turns it into a factor of the duration of the infringement. Whoever distributes an app must be able to disable a feature remotely, without depending on the client being updated.

Why Rome decides, not Dublin

Meta argued that the Garante lacked jurisdiction in favor of the Irish authority, the seat of its main establishment. The objection was rejected because the ePrivacy framework does not provide for the "one-stop-shop" mechanism.

The reasoning rests on solid ground. The one-stop shop is a GDPR institution (Articles 56 and 60) and applies to the cross-border processing the GDPR governs. The ePrivacy Directive instead leaves it to each Member State to designate the competent authority and the penalties, and the European Data Protection Board already acknowledged this in Opinion 5/2019 on the interplay between the two frameworks. It is the same path followed by the French CNIL in its December 2020 cookie decisions against Google and Amazon, upheld by the Conseil d'État.

The practical consequence goes beyond this case. An operator whose main establishment sits in another Member State cannot rely on a single point of contact for what happens on the device: for access to the terminal it potentially answers before twenty-seven authorities with twenty-seven sanctioning regimes. For the subsequent processing of the data so collected, the lead authority is competent again. The same feature is therefore subject to two distinct procedural tracks.

Open questions: where the decision will be tested

A fine of this size will be challenged before the ordinary courts (Article 152 of the Code and Article 10 of Legislative Decree 150/2011; an appeal does not by itself suspend enforcement). It is worth identifying now the points the dispute will turn on — not to downplay the decision, but because they are the same points every data controller should be asking itself.

Actual access or possible access.The announcement states that the company "accessed" the content, but also acknowledges that it is not verifiable which information was actually used. The gap between the capacity to read and reading itself is the most delicate evidentiary ground, and here the Authority's technical analysis will be decisive. Only the full statement of reasons will show how much was proven and how much presumed.

Local processing.If the selection of suggestions happened entirely on the device, with no content ever reaching the servers, would there still be "access" under Article 5(3)? The Garante answers yes, because the protection does not depend on transmission. It is a reading consistent with the purpose of the rule, but it is also the point where the expansive interpretation of the EDPB Guidelines 2/2023 has been most debated. The consequences are systemic: it concerns every on-device feature, including locally run AI models.

Quantification.Article 166(2) of the Code subjects a violation of Article 122 to the penalty under Article 83(5) GDPR: up to 4% of worldwide annual turnover. At 0.47%, the Garante stays far from the maximum, but in absolute terms the fine is, to our knowledge, the highest ever imposed by the Authority: roughly €40 for each of the estimated 20 million users. Three criteria will likely be contested. The 2019 precedent, which the announcement does not identify and which, if it is the one relating to the Cambridge Analytica case, involves different conduct and an earlier legal framework. "Poor cooperation", which must be kept distinct from the legitimate exercise of the right of defense. And the proportionality of an amount of this order in the absence of proven harm — an objection to which the Garante replies in advance with the nature of the rule itself: the infringement is the interference, not the damage.

Dual track. The Garante sanctioned access to the device. Subsequent processing — legal basis, transparency, any special categories of data — falls under the GDPR and the competence of the Irish authority. If Dublin were also to act, the issue of ne bis in idem would arise, which the Court of Justice (bpost, C-117/20) resolves through an overall proportionality test and coordination between proceedings. Coordination that, between ePrivacy and GDPR, no rule today organizes.

Content already read. The announcement describes measures aimed at the future: new consent, feature off by default. It does not mention orders to erase or restrict what was acquired since 2023. That may depend on the nature of the processing or on the limits of Article 122; it is one of the first things to look for in the full text.

AI and cloud.Excluding model training from the scope is not an acquittal: it is a matter not investigated. And the reservation on the cloud-processing feature signals where attention will shift next. Once content leaves the device, the GDPR applies in full alongside Article 122 — with the question of third parties depicted in photos and Article 9 data — and, if that content feeds models, the AI Act's obligations on documenting training data come into play.

Operational checklist for anyone building or commissioning an app

The case concerns Meta, but the rule applies to any app that reads anything from the device: gallery, contacts, location, identifiers, sensors. Six checks, in the order it makes sense to run them.

  1. Map permissions to features. For every permission declared in the manifest, list which features use it, including those from third-party SDKs. A permission with no feature to justify it should be removed.
  2. Qualify every access. Distinguish what is strictly necessary for a service the user requested from what is merely useful. Only the former is exempt from consent under Article 122.
  3. Separate consent from permission. The system dialog is not enough. A dedicated screen is needed first, stating the specific feature, what is read and how to turn it off, with a separate choice for each purpose.
  4. Default to off. Every non-necessary feature starts disabled, even when the system permission has already been granted for something else. A new use of an existing permission requires new consent.
  5. Prefer minimal access. Where the user needs to choose a piece of content, use the system picker instead of a permission over the entire archive. It is the easiest privacy-by-design measure to demonstrate.
  6. Make it verifiable. Keep proof of consent per feature, document what is processed on the device and what is transmitted, and build a remote kill switch that does not depend on the app being updated.

In short

The Garante did not sanction a data leak or a proven unlawful use of the photos. It sanctioned a design flaw: a single technical authorization used as if it were legal consent for purposes the user could not tell apart, with the feature already switched on. Article 122 of the Privacy Code protects the device as a private space, and violating it only takes entering without valid consent.

Serious questions remain, which Meta's announced appeal will bring before a judge: the proof of actual access, the treatment of local processing, the criteria for quantification, coordination with the GDPR. But none of them touches the operational rule. The operating system decides whether an app can read; for what purpose it is allowed to do so has to be asked, feature by feature, and has to be demonstrable.

Sources

  • Garante per la protezione dei dati personali, press release of 14 November 2026 (web doc. no. 10321080).
  • Legislative Decree 196/2003, Arts. 122, 152 and 166; Directive 2002/58/EC, Art. 5(3); Regulation (EU) 2016/679, Arts. 4, 7, 25, 56, 60 and 83.
  • Court of Justice of the EU, Planet49 (C-673/17) and bpost (C-117/20); EDPB, Opinion 5/2019 and Guidelines 2/2023.

Does your app request permissions that serve more than one feature?

We map permissions, SDKs and consent flows and align them with Article 122 and the GDPR, before an authority asks. Let's talk.

Let's talk about your app's permissions →