Skip to content

Facebook camera roll: Italy's Garante fines Meta €805M

Filip LuchianencoUpdated 7 min read

Last updated: 2026-11-17

On November 13, 2026, Italy's data protection authority, the Garante per la protezione dei dati personali, fined Meta Platforms Ireland Limited €805,000,000 in decision n. 815 (doc. web 10321455) over Facebook camera roll suggestions in the Facebook app for Android. The Garante found that the app accessed photos, videos and their metadata on Italian users' phones without consent specific to that feature, contrary to article 122 of the Italian Privacy Code, the national rule that transposes the ePrivacy Directive's consent requirement for access to information stored on a user's device. The fine was announced on November 14 in a press release with an English version.

The regulated act in this decision is the reading of the photo library on the phone. The Garante held that article 122 requires consent for that read regardless of any transfer, and made no finding that any photo was sent to Meta.

What did the Facebook app do with the camera roll?

The feature, "Get camera roll suggestions when you're browsing Facebook", has been in the app since 2023, according to Meta. Facebook shows the user photos and videos from the phone's gallery as ideas for posts. The Garante opened the case on a report filed on July 10, 2025 by the Centro Tutela Consumatori Utenti of Bolzano, a South Tyrol consumer association.

The Garante's technology department tested Facebook version 548.1.0.51.64 on an Android 14 phone. From its technical report of May 18, 2026 (section 1.3 of the decision):

  • Photos and videos, two separate permissions (READ_MEDIA_IMAGES and READ_MEDIA_VIDEO), are requested in one system dialog.
  • The first time a user creates a post with one photo, a story or a reel, a notice screen appears: gallery access is used to share photos and videos, get suggestions on photos to upload and "abilitare altre funzioni" (enable other features). The system dialog follows. The grant is, as a rule, permanent and revocable only in the device settings.
  • The in-app setting for the suggestions was preset to on.
  • Where a user already had the app, with the older READ_EXTERNAL_STORAGE permission granted, when the phone was upgraded to Android 13, the READ_MEDIA permissions were granted automatically and were in place when the feature was introduced.

From the English release: "When given in full, such permission allows the app to access the entire photo library on the device, usually on a permanent basis, without the user or the Authority being able to verify what information is actually being used."

According to Meta, all processing for the feature takes place on the device: the gallery index is queried for the most recently added items, and "basic metadata" (date and time, favorites, type and orientation) is read. ACCESS_MEDIA_LOCATION, the permission for location data in photo EXIF, is also declared in the manifest; Meta said the feature does not use it, and the Garante made no finding on location data.

Meta argued that article 122, and article 5(3) of the ePrivacy Directive that it transposes, apply only when information leaves the device, citing paragraph 44 of the EDPB Guidelines 2/2023. The Garante relied on the guidelines as a whole (section 3.3): under paragraph 32, article 5(3) applies whenever an entity takes steps to gain access to stored information, and under paragraph 44 itself it applies "when this information or any derivation of this information is accessed". The suggestions are derived from the gallery and, once published, are known to Meta. From the release: access to the information stored on the device "requires free and informed consent, regardless of whether data is transmitted or any harm occurs."

The Garante rejected the Android permission as consent for the feature: the permission applies to the whole app, and Meta conceded that the feature "non può operare su una base 'una foto alla volta'" (cannot operate on a "one photo at a time" basis). The Garante also rejected Meta's fallback argument, strict necessity for a service the user requested, because Meta itself described the feature as "uno strumento opzionale dell'App" (an optional tool of the App). With Android's photo picker, an app receives only the items the user selects and needs no media permission, so a single photo can be posted without gallery-wide access. The Garante cited the picker as a fact that rules out strict necessity, and imposed no duty to use it.

Why did Italy decide this instead of Ireland's DPC?

Meta argued that Ireland's Data Protection Commission, its lead authority under the GDPR one-stop shop in article 56, had exclusive competence. The Garante found that the ePrivacy Directive has no one-stop shop, and Meta accepted in its own brief (section 4.1) that the Garante enforces the Italian ePrivacy rules where they apply. Competence therefore turned on whether article 122 applied. The Garante used GDPR articles 6, 7, 12 and 13 only to define valid consent and information, and made no separate GDPR finding. A GDPR case against a company with its EU main establishment in Ireland goes to the DPC as lead authority, as in the DPC's €403M location data decision against Google.

How did the Garante calculate €805 million?

Under article 166(2) of the Privacy Code, the GDPR article 83(5) cap applies to an article 122 breach. The Garante applied the cap to the turnover of the Meta Platforms, Inc. group rather than the Irish company whose accounts Meta filed, citing the CJEU's Deutsche Wohnen judgment (C-807/21).

Step (decision n. 815, section 6) Figure
Meta group revenue, 2025 (Form 10-K) US$200,966 million, about €171,035 million at the ECB rate of 1.1750
Maximum fine, 4% of group turnover €6,841,395,745
Seriousness Medium, low end of the band
Starting range, 10% to 20% of the maximum about €684.1 million to €1,368.3 million
Starting amount €700,000,000 (10.2% of the maximum)
Final fine €805,000,000 (11.7% of the maximum, about 0.47% of turnover, about 1.56% of 2025 net profit)

Source: Garante decision n. 815, sections 6.1 and 6.2.

Poor cooperation weighed most among the aggravating factors: Meta presented its answers as "voluntary", misstated the setting's state in its reply of November 14, 2025 and corrected it only in its defense brief, supplied no technical evidence, and omitted the number of Italian Android users who had granted the permission. Meta's control of the permission design counted moderately. Order n. 134 of June 14, 2019 counted slightly: a €1,000,000 fine on Facebook Ireland and Facebook Italy over the disclosure of the data of 214,077 Italian users on the basis of a generic notice and preselected settings. App version 581, which keeps the setting off until the system permission is granted, counted as moderate mitigation, because it came late and applies only to users who update.

The Garante put the affected users at about 20 million, from AGCOM, DataReportal and Statcounter figures (section 3.8); Meta disputed the estimate without giving its own number.

What must Meta change, and can it appeal?

The Garante ordered Meta, within 60 days of notification and for Italian Facebook users on Android (decision, section 5):

  • to ask for gallery access for the feature in a separate request that explains it, without wording such as "enable other features";
  • to keep the feature off by default, also for users who already granted the permission, until they agree;
  • to make the setting match the actual processing in every app version in use in Italy, by server-side controls or forced updates if needed.

After the 60 days, Meta may not operate the feature for users without that consent. Within 90 days, Meta must report the measures with technical documentation, including whether gallery information, derived information included, is sent to Meta's systems before a post is published.

Under article 166(8) of the Privacy Code, Meta can close the case by complying and paying half, €402,500,000, within the appeal period: 30 days, or 60 for an appellant resident abroad. A Meta spokesperson told Adnkronos that the company considers the fine "sproporzionato" (disproportionate) and "Intendiamo presentare ricorso" (we intend to appeal). As of November 17, 2026, news reports mention no appeal filed in court; I did not search Italian court records.

What did the decision leave open?

Meta denies using unpublished gallery content to train AI; the Garante could not verify the denial, since the app's code is closed and its traffic encrypted. A second feature, cloud processing of the camera roll, launched in the EU in early 2026, according to Meta. The Garante reserved a separate inquiry into its legal basis, user information and consent, the reuse of content for AI training, and its relation to the permission already granted. The decision covers Italian users of the Android app only.

What a CITT scan and capture show for photo library access

When I scan an Android build with CanITrustThat (CITT), the static report lists each media and storage permission declared in the manifest (READ_MEDIA_IMAGES, READ_MEDIA_VIDEO, READ_MEDIA_VISUAL_USER_SELECTED, READ_EXTERNAL_STORAGE, MANAGE_EXTERNAL_STORAGE) and each class outside the AndroidX library that constructs the AndroidX photo picker contract (PickVisualMedia or PickMultipleVisualMedia), with the file it was found in. Those are the two facts the Garante weighed: a broad, app-wide grant, and the narrow route Android offers for a single photo. Both are findings of presence in the build; which feature reads the gallery once the permission is granted is outside the scope of a static scan.

In the Garante's technical report, a black-box analysis of Facebook's traffic is described as "lunga, onerosa e dall'esito incerto" (long, costly and of uncertain outcome). In a network capture on a test phone, every request and response of the session is recorded and split into those sent before and after the app's consent screen, so a photo, thumbnail or EXIF field sent during the session over a decrypted connection is in the recording. A connection that cannot be decrypted, for example because the app pins its certificate, is recorded as failed, with its server address and without its content. A gallery read that stays on the phone produces no request. Under article 122 as the Garante applied it, that read is the regulated act, and the evidence for it is the notice, the system dialog and the feature's default state. Those screens are in the screen video kept for each capture session when the session reaches them; code paths the session did not trigger are outside the recording (limits).

Related posts: the CNIL's Fnac app tracker fine under the French transposition of the same ePrivacy article, the Garante's Character.AI age verification decision, its BBVA in-app marketing fine and the Meta localhost tracking lawsuit over the Facebook and Instagram Android apps.

I run permission and consent investigations of apps for lawyers and for researchers working with lawyers, on one app or a list of apps in bulk. Sign up for a CanITrustThat account to run your own research, let us run an investigation for you, or read the teardowns.

App privacy law, applied to real apps.

Posts on new laws, fines and studies, and teardowns of the apps those laws apply to.

How we use your address: privacy notice. Prefer a feed reader? Use the RSS feed.