Italy’s data protection authority has handed Meta its largest-ever Italian privacy penalty, and it did so without asking Dublin for permission. On November 14, 2026, the Garante per la protezione dei dati personali announced an €805 million fine against Meta Platforms Ireland Limited over a Facebook for Android feature that reads the phone’s photo gallery to suggest content to post. Early reports described the authority as “assessing” a fine. That is not accurate: the Garante’s press release says the penalty has been imposed, together with binding orders that Meta must meet within 60 days. Meta says it strongly disagrees and plans to appeal.
TL;DR
- The Garante fined Meta Platforms Ireland €805 million on November 14, 2026, for accessing Italian Android users’ photos, videos and metadata through a Facebook gallery-suggestions feature without specific consent or adequate information.
- The authority relied on Article 122 of Italy’s Privacy Code, which implements the ePrivacy Directive, and rejected Meta’s argument that only the Irish regulator could act under the GDPR one-stop-shop.
- Within 60 days Meta must switch the feature off by default and ask for separate, specific consent; Meta has said it will appeal.

What the Garante found
The decision concerns a setting that Italian users saw as “Ottieni suggerimenti dalla galleria quando navighi su Facebook”, or “Get camera roll suggestions when you’re browsing Facebook” in the authority’s English version. Available since 2023, it surfaces photos and videos from the phone’s gallery as ideas for new posts while the user scrolls.
The inquiry started in July 2025 after a report from the Centro Tutela Consumatori Utenti, a consumer association based in Bolzano, and the Garante ran its own technical analysis of the app. According to the authority, three design choices sat at the heart of the problem:
- One permission for many purposes. Gallery access was requested through a single authorisation that applied across the whole app and covered several features with different needs.
- A vague prompt. The permission was preceded by a generic notice about enabling “other features”, which did not tell people they were also switching on gallery suggestions.
- On by default. The suggestions feature itself was pre-set to active.
The Garante stressed what a full gallery permission means in practice. Once granted, it lets an app read the entire photo archive on the device, usually on a permanent basis, and neither the user nor the regulator can verify which images and metadata are actually being used. For a feature built around personal photos, that metadata can include where and when each picture was taken.
Why an Italian regulator could fine an Irish-based Meta entity
Most GDPR cases against Meta’s European operations go to Ireland’s Data Protection Commission, because Meta Platforms Ireland is the main establishment and the GDPR’s one-stop-shop channels cross-border cases to the lead authority. Meta raised exactly that objection. The Garante rejected it.
Its reasoning rests on the legal basis it chose. The violation it found is of Article 122 of the Italian Privacy Code, the provision that transposes Article 5(3) of the ePrivacy Directive. That rule protects the user’s terminal equipment, treating the smartphone as part of the person’s private sphere. Storing or reading information on the device requires free and informed consent, unless a narrow exemption applies, and this holds regardless of whether any data is transmitted or whether anyone suffers harm. The ePrivacy regime has no one-stop-shop mechanism, so each national authority enforces it on its own territory. Regulators have used the same route before for trackers and cookies, as French enforcement over mobile app tracker consent shows, and Sweden’s regulator has explained when ePrivacy rather than the GDPR governs location-based messaging to phones.
The practical message for any company with an EU lead authority is that the one-stop-shop is not a shield for device-access practices. A national regulator in any member state where users are affected can open its own case.
The orders, step by step
The fine is only part of the decision. The Garante also imposed corrective measures with tight deadlines:
- Separate consent. Within 60 days, Meta must request consent for the gallery feature through a distinct, specific prompt, explaining what the feature does, that it involves gallery access, and how to turn it off.
- Default off for everyone. The feature must stay disabled by default, including for users who have already granted the app-level permission.
- A hard stop if Meta misses the deadline. If the 60 days pass without compliance, the feature cannot be activated for users who have not given valid consent.
- Reporting back. Meta must tell the Garante within 30 days what steps it has started, and within 90 days what measures it has adopted.
Point two matters most for product teams. The regulator is not satisfied with fixing the flow for new installs: it wants the existing installed base reset, because past consent obtained through the bundled permission does not count.
How the €805 million figure was set
The authority listed the factors behind the amount. It pointed to the large number of people affected, around 20 million Android users in Italy, and to the duration of the violation, which it says is still continuing for people who have not updated the app and for those who already granted the system permission. It also cited an earlier 2019 decision against the company and what it called poor cooperation during the investigation. As mitigation, it took into account changes Meta introduced after the complaint, though it judged them late and limited to users who update.
The Garante put the fine at roughly 0.47% of the group’s worldwide turnover. Politico described it as the largest fine Italy’s data protection regulator has ever issued. In the wider European picture, it sits below the Irish DPC’s €1.2 billion GDPR fine on Meta in 2023 over transfers to the United States, but above Luxembourg’s €746 million penalty on Amazon in 2021.
What the decision does not cover
Two limits are worth noting so the case is not overstated:
- No finding on AI training. The proceeding did not examine whether gallery content was used to train artificial intelligence models. Meta denies it was, and the Garante made no finding either way.
- The newer cloud feature is separate. A feature launched in 2026 that allows cloud processing of gallery content was not part of this decision. The Garante says it reserves the right to assess it in a separate investigation.
That second point is a signal. Concerns about Meta’s default-on AI features have grown across Europe, and moving on-device photo analysis into the cloud raises a fresh set of questions about storage, purpose and retention.
Meta’s response
“We strongly disagree,” a Meta spokesperson told ANSA, and the company told the BBC it plans to appeal. In Italy, Garante decisions can be challenged before the ordinary courts. Until a court rules otherwise, the decision and its deadlines stand, and nothing in the authority’s announcement suggests the orders are suspended pending appeal.
It is worth keeping the status straight. The Garante has made findings and imposed a sanction; Meta disputes them. An appeal could reduce or overturn the fine, but it does not turn the decision back into a proposal.
Lessons for mobile and app teams
This is a Meta case, but the pattern is common. Many apps bundle several features behind one operating-system permission and then enable new uses of that access by default. The Garante’s reasoning gives a checklist for anyone shipping features that read device content:
- Map every feature that reads photos, contacts, files or sensors, and tie each one to its own purpose and consent where ePrivacy requires it.
- Do not rely on the operating-system permission dialog as consent for a specific feature. The OS prompt grants technical access; it does not tell people what you will do with it.
- Write pre-permission screens that name the feature. Phrases like “enable other features” are exactly what the regulator criticised.
- Ship new uses of existing access switched off, and plan how to re-ask existing users rather than grandfathering them in.
- Keep a technical record of what the app actually reads and sends, because regulators are now testing apps themselves. Earlier research into Android tracking techniques showed how much can be found by inspecting app behaviour directly.
The same logic applies on the web. Consent to read or store information on a device must be specific and freely given, a principle that also drives disputes such as pay-to-reject cookie models. The Garante has also shown appetite for big-ticket cases in other sectors, including its health data fine against IQVIA.
Frequently asked questions
Is the €805 million fine final?
It has been imposed by the Garante, not merely proposed. Meta can still challenge it in court, and has said it will appeal, so the amount could change.
Does this affect iPhone users?
The decision covers the Facebook app for Android devices. The Garante’s announcement does not address iOS.
Why didn’t the Irish Data Protection Commission handle the case?
Because the Garante based it on the Italian rule implementing the ePrivacy Directive, which protects access to information on users’ devices and has no one-stop-shop. National authorities enforce it directly.
Did the Garante find that Meta trained AI on users’ photos?
No. AI training was outside the scope of this proceeding, and Meta denies it. A 2026 cloud-processing feature may be examined separately.
What should Italian Facebook users expect?
If Meta complies, the gallery-suggestions feature should be off by default, with a separate prompt asking whether to switch it on and explaining how to turn it off later.
The phone in your pocket is private space
The headline number will get the attention, but the more lasting part of this decision is the principle behind it. The Garante treated a smartphone gallery the way the law treats a home: entry needs a clear invitation, given for a specific reason, and a general “let us enable other features” is not one. Any team that builds on device permissions should assume other regulators read the decision the same way.