Italy's data protection authority began its calculation of Meta's 805 million euro fine at 700 million euros, measured against a legal ceiling of about 6.84 billion euros, and raised it after weighing the company's conduct, according to the full text of the decision. The document, dated November 13, 2026, also sets out how Meta Platforms Ireland Limited can close the case: under Italian law, it can comply with the authority's orders and pay half the amount within the period allowed for an appeal. Half of 805 million euros is 402.5 million euros, by PPC Land's calculation.

The Garante per la protezione dei dati personali announced the fine on November 14, and PPC Land reported it that day. The Italian version of the press release links to the full decision, registered as measure number 815 and published on the authority's website as document 10321455. At more than 20,000 words, it records what the authority's engineers found when they installed Facebook on an Android 14 phone, answers each of Meta's defences, explains why the case was decided in Rome rather than Dublin, and shows the arithmetic behind the amount. Quotations from the decision in this article are PPC Land translations from the Italian.

In Short

Italy's privacy regulator has published the full reasoning behind its €805 million fine on Meta over the Facebook app's access to Android photo galleries. The text shows the fine started at €700 million, rose because of Meta's control over the app's design, a 2019 precedent and what the regulator calls poor cooperation, and that Meta can settle by complying and paying half. For anyone building apps, the core finding is that one Android "allow" tap given to post a photo does not count as consent for every other feature that reads your gallery.

What the full text adds to the announcement

The November 14 press release gave the headline facts: the amount, the feature, the provision breached and three compliance periods. The decision fills in several points the release left open or described differently.

Point November 14 press release Full decision of November 13
Compliance periods 30, 60 and 90 days, with no starting point given 60 and 90 days "from notification"; payment within 60 days of notification; 30 days for a first report on initiatives
2019 precedent A 2019 measure, not identified Injunction order no. 134 of June 14, 2019: 1 million euros against Facebook Ireland Ltd, jointly with Facebook Italy S.r.l., involving data on 214,077 Italian users
How the amount was set About 0.47% of worldwide turnover Starting amount of 700 million euros, 10.2% of a 6,841,395,745 euro cap, raised to 805 million euros after aggravating and mitigating factors
Users affected About 20 million A range of 18 million to 22 million, derived from AGCOM, DataReportal and Statcounter figures
Users who already granted access Italian text: "authorisation"; English text: "consent" "users who have already granted the system authorisation"

The last row matters for the record. PPC Land's November 14 report noted that the Italian and English versions of the release described the users covered by the default-off order differently. The decision settles it in favour of the Italian wording: the order reaches everyone who tapped "allow" on the Android system prompt, because the authority never treated that tap as consent for the feature.

The decision was adopted at a meeting attended by president Pasquale Stanzione, who also acted as rapporteur, vice president Ginevra Cerrina Feroni, board member Agostino Ghiglia and secretary general Luigi Montuori.

Sixteen months in the authority's own record

The file opens with a report from the Centro Tutela Consumatori Utenti di Bolzano, the South Tyrol consumer centre also known as Verbraucherzentrale Südtirol. According to the decision, the centre told the authority that Meta had changed the Facebook app "without notice" by introducing gallery-based sharing suggestions with consent "tacitly preset", and it suggested a link to the training of Meta's artificial intelligence systems. The authority did not pursue the AI link, for lack of evidence. The rest of the file is procedural, and the decision records it with protocol numbers.

Date Step Reference
July 10, 2025 Consumer centre files its report against Meta Platforms Ireland Ltd -
October 27, 2025 Garante's office requests information under Article 122 of the Privacy Code Prot. 142506
November 14, 2025 Meta replies, disputes the authority's competence and says it is answering "voluntarily"; sends a copy to the Irish DPC "as a courtesy" Prot. 152086/25
December 2, 2025 Office asks the Department of Digital Technologies and IT Security for a technical assessment Prot. 168848
May 18, 2026 Technical report delivered Prot. 76045
July 29, 2026 Formal start of proceedings under Article 166(5) of the Code Prot. 115205
August 5, 2026 Meta requests access to the file and a 45-day extension (logged August 6 and 7) Prot. 119078, 119465
August 10, 2026 Office sends the one document Meta did not yet have and extends the defence deadline to October 12 Prot. 119976
September 14, 2026 Meta says its security systems blocked the attachments, sent as ".7z" compressed files, and that the August 10 note went to a wrong address for one of its lawyers Prot. 131503
September 16, 2026 Office re-sends the documents as PDF to the correct address Prot. 132333
October 12, 2026 Meta files its defence brief (logged October 13), asks for the case to be dismissed and does not request a hearing Prot. 145274
October 25, 2026 Authority consults Irish ownership records on Meta's corporate chain -
November 13, 2026 Decision adopted Register no. 815
November 14, 2026 Press release published Doc web 10321080

One clerical slip surfaces along the way. The July 29 notice of proceedings named "Meta Platforms Technologies Ireland Limited", a typing error according to the decision. Meta Platforms Ireland Limited confirmed it was the controller responsible for the feature, received the notice and defended itself in full, so the authority held that the error caused no prejudice and addressed the decision to Meta Platforms Ireland Limited.

What the authority's engineers found inside the app

The technical assessment is the backbone of the case. Analysts installed the Facebook app from scratch on a phone running Android 14, so they could observe its behaviour on first use. They also extracted the AndroidManifest.xml file - which, as the decision puts it, declares to the operating system "what the app is and what it intends to do" - from the installation package of version 548.1.0.51.64. The package was downloaded from a third-party site, its authenticity was checked with the apksigner tool, and the file was examined with Apk Analyzer and Android Studio.

According to the decision, the report found the following:

  • A single prompt for two permissions. On first launch, access to "Photos and videos" is denied. The app gains access only after the user grants operating system permissions, through one request covering both photos and videos, although these are two distinct permissions, READ_MEDIA_IMAGES and READ_MEDIA_VIDEO.
  • A setting switched on before it could work. The option "Get tips from your gallery while browsing Facebook" was preset as active, but produced no suggestions until the system permission was granted.
  • A generic explanation at the moment of asking. The first attempt to create a post with a single photo, a story or a reel brought up a screen saying gallery access serves to "share photos and videos, receive suggestions on photos to upload and enable other features", which steered the user towards the broad READ_MEDIA permissions. Access granted this way is, as a rule, permanent and can be revoked only in the device settings.
  • A location permission in the manifest. The manifest declares READ_MEDIA_IMAGES, READ_MEDIA_VIDEO, READ_MEDIA_VISUAL_USER_SELECTED and ACCESS_MEDIA_LOCATION, the last covering location data held in photos' EXIF metadata. Granted through a single system window, the photo permission also covers location data without a second request. The report considered it "very likely" that the app uses this mode, but could not verify it.
  • The whole archive, and a route out of the phone. Under "Allow all", the READ_MEDIA permissions let the app read every photo and video, process them locally or in the cloud and, with the INTERNET permission that almost every app receives at installation, transmit them to the provider's systems.
  • Permissions inherited automatically. For people already using Facebook when their phone updated to Android 13, an app holding the older READ_EXTERNAL_STORAGE permission received the READ_MEDIA permissions automatically when the feature was introduced.

The report also put the feature in the context of Android's history. Android 13, introduced in June 2022, offered only "Allow all" and "Don't allow" for photo and video access. The "Allow limited access" option arrived with Android 14 in the autumn of 2023. Since 2023, Android has also offered a "photo picker", which lets an app reach only the photos selected at that moment without requesting system permissions at all.

That last point became central. Publishing a single photo can work through the picker. A feature that scans the gallery to propose content cannot, because it needs broader and continuing access. In the report's view, that access "should have been the subject of a separate request, linked only to it and deactivated by default". Instead, according to the decision, "Meta merged into a single request several functions with different access requirements."

The report's final finding was a limit rather than a discovery. The Facebook app is proprietary software whose code is not available, and its traffic to Meta's systems is encrypted. The authority could not verify which data are transmitted, nor rule out that photos and their metadata reach Meta's systems without the user knowing. A black-box analysis of the traffic, according to the report, "would be long, costly and of uncertain outcome".

The decision is careful about what this does and does not prove. The authority "has not established that the Feature accesses location data, that the contents are transmitted or used for further purposes, nor that special categories of data are processed", and those hypotheses "are not the basis of the decision". Its case rests on the access itself.

Meta's defence, point by point

Meta's brief of October 12, 2026, ran through a sequence of principal and fallback arguments. The decision answers each one.

Meta's argument The Garante's answer
The charges were generic, with no link between the GDPR articles listed and the reasoning Rejected. Meta replied to every point, which shows it understood the charges; no standalone GDPR violation is found
Article 122 and Article 5(3) of the ePrivacy Directive require a communications network and information leaving the device, citing EDPB Guidelines 2/2023, paragraphs 32, 44 and 53; the feature runs on-device, reads only date and time, and sends nothing to Meta's servers Rejected. Article 122(1) contains no reference to a network; paragraph 44 still applies Article 5(3) to access to information "or any derivative"; Meta's own statements and privacy policy describe Meta obtaining and processing gallery data; no technical proof was offered that nothing leaves the device
The app is a "software-based service", not a network, and publishing a suggestion is a separate "Publication Phase" started by the user Rejected. Reading, selecting and proposing content happen before the user chooses anything
GDPR Articles 6, 7, 12 and 13 fall to the Irish DPC as lead authority (Facebook Belgium, C-645/19; EDPB Opinion 5/2019) Rejected. ePrivacy has no one-stop shop, as Meta itself acknowledged; the GDPR articles serve only to define consent and information
The operating system permission is a positive act and so free, specific, informed and unambiguous consent for a single purpose, facilitating sharing (recital 32; EDPB Guidelines 5/2020) Rejected. The permission is app-wide, requested to publish a photo and introduced by the words "enable other features"
The in-app toggle is not a consent mechanism and is not a pre-ticked box (Planet49; Orange România) The authority accepts the premise and draws the opposite conclusion: if the toggle is not consent, the only act left is a permission given for another purpose
Access is strictly necessary for an "efficient and effective photo upload process" Rejected. The argument took one paragraph and no evidence; Meta itself calls the feature "an optional tool of the App"; the photo picker shows uploads work without broad access
The legal basis is contract for adults and legitimate interest for minors Irrelevant to the access: under Article 122, only consent or the narrow exemptions apply
Users were informed through the privacy policy (wording in place since July 2022), the notice before the permission request, the suggestion itself and an April 2026 Help Center article Rejected. The notice reaches only those who have not yet granted permission; the suggestion appears after processing has started; the policy wording predates the feature
There was no harm, only basic non-sensitive metadata; the 20 million estimate is unsupported; at most, a non-public warning would fit Rejected. Harm is not a condition; Meta gave no alternative figure; public sources put the range at 18 million to 22 million; the violation is not "minor"

Meta's main line of defence was technical. The feature, it argued, works entirely on the device: it queries the gallery index, picks a recent item and shows a suggestion, without Meta's servers collecting or storing gallery data. Without data leaving the phone, there would be no "access" under the ePrivacy Directive and so no case for the Italian authority.

The Garante disagreed on the law first. Article 122(1) of the Italian Privacy Code, which transposes Article 5(3) of the directive, makes access to information already stored on a user's device conditional on consent after information. Its text, according to the decision, does not require that the information leave the device, nor that a network be used. The reference to a network appears only in paragraph 2-bis of the same article, which the authority deliberately left out of the charges. The European Data Protection Board itself, the decision notes, observed that the 2009 amendment of the directive removed precisely the reference to the "use of the electronic communications network".

On the EDPB's guidelines, which Meta relied on, the decision argues they "must be read in full, and not only in the passage invoked by the Company". Paragraph 44 of Guidelines 2/2023, in version 2.0 adopted on October 7, 2024, says that local use of information by an app through system APIs is not "access" as long as the information does not leave the device. The same paragraph adds, in the decision's rendering, that "when such information or any derivative of it is accessed, Article 5(3) would apply". For the Garante, a suggestion built from a selection of gallery content and metadata is such a derivative, and if the user publishes it, Meta learns of it anyway. The guidelines, the decision adds, are soft law: "an authoritative interpretative aid", but not binding on the scope of Article 122. PPC Land covered the EDPB's work on those guidelines when the first draft was adopted in November 2023.

Then came Meta's own words. In its reply of November 14, 2025, the company told the authority, according to the decision: "When a user grants Meta access to their gallery through the device settings [...] Meta obtains local access to the gallery on the user's device [...] Meta processes the media content from the user's gallery in connection with the Feature." It also gave contract and legitimate interest as the legal bases for processing data "to provide the Feature". If Meta did not process data through the feature, the authority reasoned, there would have been no reason to name a legal basis at all.

Facebook's privacy policy pointed the same way. Its section on device information says, in the Italian text quoted in the decision, that if users give permission to access photos on their device, "we collect metadata", which Meta uses "to do things like remind you when you have new photos to upload". Meta cited that wording as proof users were informed. The authority turned it around: "Either the metadata are collected by Meta, and Article 122 applies; or they are not, and the privacy notice, which Meta considers sufficient to inform users, describes the processing inaccurately."

The decision also explains why the size of the archive matters even if no file is copied. "The media archive of a smartphone is among the most intimate places in a person's digital life," the authority writes. "It holds images and videos of private and family life, often also of third parties and minors, which the user never intended to make accessible to a service provider."

That left the question of proof. Meta asserted that "no data" leaves the device, but, according to the decision, produced no architecture description, traffic logs, attestations or independent verification; documents 1 to 4 attached to its brief were screenshots of interfaces. The authority framed this as a matter of accountability under Articles 5(2) and 24 of the GDPR. "The controller cannot, therefore, take advantage of an opacity that derives from its own technical choices," the decision says. Meta's answer, in the authority's words, was "an apodictic statement, unproven and unverifiable", and at odds with its earlier statements, "with respect to which the Authority would have to confine itself to an act of faith". The decision notes that Article 168 of the Privacy Code sanctions false statements to the authority.

Why the case did not go to Dublin

Meta's jurisdiction argument was, on the decision's account, undercut by Meta itself. In its brief, the company acknowledged that the ePrivacy Directive provides for no one-stop shop and that the Garante can enforce national rules transposing it, where they apply. Once Article 122 applied, the question of competence was settled.

The authority relied on the same sources Meta had cited. EDPB Opinion 5/2019 of March 12, 2019, states that the GDPR's cooperation and consistency mechanisms "do not apply to the enforcement of the provisions contained in the ePrivacy Directive as such", while processing before and after the access remains under the GDPR and the lead authority. In Facebook Belgium (C-645/19, June 15, 2021), the Court of Justice recalled that the storage and reading of personal data through cookies fell within the scope of the ePrivacy Directive "and not within the 'one-stop shop' mechanism". The decision also invokes the Court's Bundeskartellamt judgment (C-252/21, July 4, 2023), under which an authority acting on its own competence can find a processing operation non-compliant with the GDPR without taking over the role of data protection authorities.

The Garante drew the boundary narrowly. Its finding covers only the access stage, only Article 122, and only Italian users with Facebook installed on Android devices. The Irish Data Protection Commission keeps competence over what Meta does before and after that access, which the decision does not examine. The authority adds that it will send the decision to the DPC "for any checks within its competence that the Irish authority considers necessary".

Jurisdiction is not an abstract risk for the Garante. In March 2026, a Rome court annulled its 15 million euro fine against OpenAI because Ireland's regulator had become OpenAI's lead authority under the GDPR. The Meta decision is built on a different footing: a national ePrivacy rule outside the GDPR's cooperation system.

One tap, many features

The consent analysis turns on a sentence Meta wrote in its own defence. "Android's permission model does not allow apps to request access to media content on an individual basis for each feature," the company argued, according to the decision. "The Operating System Level Authorisation applies to the App as a whole." Meta also conceded that the gallery feature "cannot operate on a 'one photo at a time' basis", and that the ACCESS_MEDIA_LOCATION permission is declared "to be used by other, distinct functions of the App".

For the authority, those admissions defeat the consent argument. A permission requested to publish a photo, valid for the whole app and introduced with the phrase "enable other features", cannot be specific consent for a feature that scans the gallery. The decision cites the Court of Justice in Planet49: consent "must relate specifically to the processing of the data in question and cannot be inferred from an expression of will with a different object".

Meta's claim that one purpose, "facilitating sharing", covered both posting and suggestions met a broader objection. "Using the same criterion, every function of a social network could be traced back to the purpose of 'sharing', which represents the prevailing aim of anyone who intends to join a community," the decision says. Under recital 43 of the GDPR and the Court's Meta Platforms ruling (C-252/21, paragraph 144), consent is presumed not freely given if it cannot be given separately for different processing operations.

The authority also found Meta's two lines of defence incompatible. To argue valid consent, Meta said the permission served a single purpose. To argue that Article 122 did not apply, it said access and publication were separate operations. "The two positions are irreconcilable," the decision says. "If the purpose is single, the access is the first act of a unitary operation; if the phases are distinct, the generic authorisation does not cover the Feature and is not specific."

Then there is Google. The technical report cited the policy of Google LLC, which created Android and sets the permission rules developers must follow to distribute apps through Google Play. For photo and video permissions, that policy calls for sensitive permissions to be requested incrementally, in the context where they are needed, with fresh consent for additional purposes. The authority saw the source as decisive: "Meta therefore cannot invoke the Android model to justify a single request that the policy of its own creator advises against."

Two further facts weighed against Meta. First, it admitted in its brief that the in-app setting could appear "active" before the user granted the system permission, contrary to what it had told the authority on November 14, 2025. Meta says it fixed this in version 581 of the app, while users who have not updated still see the previous interface. Second, users who granted gallery access before the feature launched in 2023, including those whose permission was carried over automatically on Android 13, never received any request relating to the feature.

Android 14's "limited access" option did not change the outcome. According to the decision, it is not offered on Android 13 and earlier; it applies to the whole app, not to a feature; and every change to the selected set requires repeating the procedure, which in practice pushes users towards the broadest grant. "For the Authority, the limited nature of the access makes no difference."

What users were told, and when

Article 122 requires information before consent. The decision lists four failings.

  1. Existing users were told nothing. Meta did not dispute this; it argued that "an additional and separate notification" was not required. The notice before the permission request appears only to people who have not yet granted it.
  2. The privacy policy wording predates the feature. The sentence Meta pointed to, about reminding people "when you have new photos to upload", has been in the policy since July 2022, according to Meta, while the feature launched in 2023. The closest wording to the feature, "Content you provide through our camera features, your gallery settings or voice features" in a translation of the Italian text quoted in the decision, appears 23 times in the policy, including in connection with ad personalisation. Meta's brief did not reply on that point.
  3. The notice before the request was generic. "Enable other features" did not tell users which processing they were allowing, did not distinguish single-photo posting from gallery scanning, and did not say that the permission lets the app read every photo and video and stays valid for every function.
  4. The settings screen did not match reality. For a period, the option could show as active before any permission was granted.

The authority took note of version 581, the April 2026 Help Center article and further updates Meta announced. All came after the July 2025 report and the October 2025 request for information, apply only to people who update the app and, according to the decision, "cannot remedy the unlawfulness of access that took place earlier". They count only towards the amount of the fine.

Several issues raised during the investigation were set aside as grounds for the decision. The technical report had said the complexity of the settings screens "could constitute" an obstacle and that some elements "could constitute" deceptive design patterns, the practices often described as dark patterns, under EDPB Guidelines 3/2022. Because those findings were cautious, the authority treated them only as context. The same applied to the feature's shifting names in the app and to the location permission.

How the Garante reached 805 million euros

The decision follows the EDPB's Guidelines 4/2022 on calculating fines, version 2.1 of May 24, 2023, in six steps.

  1. The provision and the cap. A breach of Article 122 of the Code is punished under Article 83(5) of the GDPR, through Article 166(2) of the Code. Because one provision was breached through one course of conduct, Article 83(3) on multiple infringements does not apply. The maximum is 20 million euros or 4% of total worldwide annual turnover in the preceding financial year, whichever is higher.
  2. The undertaking. The relevant turnover is that of the group, not the Irish subsidiary. The decision applies the competition-law notion of an undertaking, the Court of Justice's Deutsche Wohnen judgment (C-807/21) and the Akzo presumption that a parent holding all or almost all of a subsidiary's capital exercises decisive influence. Meta Platforms Ireland Limited (Irish company number 462932) is owned 100% by Facebook International Operations Limited (514293), which is owned 100% by Facebook Ireland Holdings Unlimited Company (466405), whose capital is held entirely by Meta Platforms, Inc., according to the Media Ownership Ireland records, a project of Coimisiún na Meán and the DCU School of Communications. Meta's annual report filing lists the Irish company among its subsidiaries.
  3. The turnover. Meta Platforms, Inc. reported 2025 revenue of 200,966 million dollars and net income of 60,458 million dollars in its Form 10-K. At the European Central Bank reference rate for December 31, 2025, 1 euro to 1.1750 dollars, that gives turnover of 171,034,893,617 euros and net income of about 51,454 million euros. The 4% cap is 6,841,395,745 euros. The decision stresses that the cap is not linked to Italian turnover or to the scope of the charges.
  4. Seriousness and starting amount. Weighing the factors in the table below, the authority classed the violation as of medium seriousness, "in the lower part of the band". For medium seriousness, the starting amount lies between 10% and 20% of the cap, between about 684.1 million and 1,368.3 million euros here. The authority set it at 10.2% of the cap, 700 million euros. No size adjustment applies, because the size of the company is already reflected in the turnover-based cap.
  5. Aggravating and mitigating factors. One moderate mitigating factor was outweighed by three aggravating ones, so the amount rose to 805 million euros, still within the 10% to 20% band.
  6. Final check. The authority tested the result for effectiveness, proportionality and dissuasiveness. It applied no deterrence multiplier and no reduction.

The factors that shaped the starting point were these, according to the decision:

Seriousness factor Assessment
Nature of the violation The precondition of the protection, prior specific and informed consent, was never sought for the feature; commercial processing through a closed system
Scope and number of people National and "systemic"; about 20 million Android users, including people who never used the feature
Purpose Increasing use and sharing on the platform, central to Meta's business
Duration Since 2023, according to Meta, and still ongoing for users who have not updated and those who already granted permission
Damage No concrete individual damage proven; potential loss of control over private content, given "limited weight"
Intent or negligence Negligent, not intentional, but negligence "not slight" for a global operator familiar with Android's permission model
Categories of data Ordinary data; no location or special category data established; but the whole archive is reachable under "Allow all"

The circumstances weighed after the starting point were these:

Article 83(2) factor Garante's finding Effect
(c) Steps to mitigate Version 581, April 2026 Help Center article, announced updates; late, limited to updated apps, no change to how consent is obtained Mitigating, moderate
(d) Degree of responsibility Meta controls the app's architecture and the permission request and did not separate the feature's access request from posting Aggravating, moderate
(e) Previous infringements Order no. 134 of June 14, 2019: 1 million euros, generic notice and non-specific consent with preselected settings, 214,077 Italian users; weight reduced by the time elapsed and the different rules then in force Aggravating, slight
(f) Cooperation Cooperation presented as "voluntary"; inaccurate statement on the setting's state; no technical evidence; no user count Aggravating, significant
(h) How the authority learned Report from a consumer association, not notification by Meta Neutral
(k) Financial benefit Meta Platforms Ireland bills advertising on Facebook and other group services, so more use brings an economic advantage, but none could be quantified Not aggravating
(i), (j) Prior orders, codes of conduct None on the same subject; no relevant code or certification Neutral
Pending proceedings in Meta's accounts No definitive findings on this feature Not considered

The 2019 precedent was the fine the Garante's English-language announcement of June 28, 2019, described as a Cambridge Analytica case, involving the "thisisyourdigitallife" app. The 2026 decision describes it only by its content: the communication of data on 214,077 Italian users "on the basis of a generic notice and non-specific consent, with preselected settings and no alternatives for the user".

On cooperation, the decision is pointed. Meta presented as "voluntary" a cooperation that is "due by law", corrected an inaccurate statement only in its defence brief, offered no technical evidence for a closed, encrypted system, and did not give the number of users who had granted the permission. That attitude, according to the decision, "left to the Authority the burden of reconstructing facts within the exclusive availability of the Company".

The missing user count shaped the estimate itself. The authority started from AGCOM's figure of 35.6 million monthly unique Facebook users in Italy in September 2025, based on Audicom-Audiweb data, and DataReportal's estimate of about 28.5 million at the end of 2025, based on Meta's advertising tools. Applying Statcounter's share of about 63% for Android in Italian mobile use gave a range of about 18 million to 22 million users. The uncertainty, the decision says, "derives from the Company's failure to cooperate and cannot therefore operate in its favour".

The final figures, as the decision states them:

Measure Amount
Meta Platforms, Inc. revenue, 2025 $200,966 million (€171,034,893,617)
Meta Platforms, Inc. net income, 2025 $60,458 million (about €51,454 million)
Legal maximum (4% of turnover) €6,841,395,745
Medium-seriousness band (10% to 20%) About €684.1 million to €1,368.3 million
Starting amount €700,000,000 (10.2% of the maximum)
Increase after aggravating and mitigating factors €105,000,000 (15% of the starting amount, PPC Land calculation)
Final fine €805,000,000
Fine as share of worldwide turnover About 0.47%
Fine as share of group net income About 1.56%
Fine as share of legal maximum 11.7% according to the decision; 11.77% by PPC Land's calculation
Settlement amount under Article 166(8) €402,500,000 (PPC Land calculation)

Meta's request for a non-public warning failed. The number of users, the duration, the structural nature of the violation and the fact that part of the conduct continues rule out treating it as "minor" under recital 148 of the GDPR, according to the decision. On deterrence, the authority went beyond Meta. The amount, it says, "also signals to operators that the use of generic operating system authorisations to access users' content for different purposes is sanctioned to a significant degree".

What Meta must do, in the decision's words

The decision's operative orders are reproduced below in PPC Land's translation. The authority found the conduct still ongoing: version 581 reaches only people who update the app, and Meta has not said it asked Italian users who already granted the permission for new consent.

Legal basis Order Deadline
GDPR Article 58(2)(d) (i) "obtain consent to gallery access for the Feature through a distinct and specific request, not combined with the authorisation request for publishing photos and videos or with other functions, and without generic formulas such as 'enable other features'" 60 days from notification
(ii) "inform the user, at the time of the request, clearly and comprehensibly, of the purpose of the Feature, of the fact that it involves access to the media archive and of how to deactivate it and revoke the authorisation" 60 days from notification
(iii) "keep the Feature deactivated by default and activate it only following an expression of the user's will that refers to it" 60 days from notification
(iv) "obtain consent in this way also from users who have already granted the system authorisation, keeping the Feature deactivated until that expression of will" 60 days from notification
(v) "ensure that the state of the setting matches the actual state of the processing, for all versions of the app in use in Italy, including through server-side controls or mandatory updates" 60 days from notification
GDPR Article 58(2)(f) If the 60 days pass without compliance, a ban on "making the Feature operational for Italian Facebook users on Android devices who have not given consent in the manner indicated, until compliance"; and a ban on "processing any information processed through the Feature without consent obtained in the manner indicated" After 60 days
GDPR Article 58(1)(a); Code Article 157 Report the initiatives under way, also with a view to settling the case 30 days
GDPR Article 58(1)(a); Code Article 157 Report the solutions adopted, "attaching the relevant technical documentation (including screenshots of the new interfaces and statements on how the processing works, indicating whether gallery information, including derived information, is transmitted to Meta's systems before publication), as well as the number of Italian users on Android devices who have given consent under the new procedure" 90 days from notification
GDPR Articles 58(2)(i) and 83; Code Article 166 Pay 805,000,000 euros, unless the case is settled 60 days from notification
Code Article 166(8) Settle by complying with the orders and paying half the fine Within the period for an appeal
Code Article 166(7) Publication of the injunction on the Garante's website, as an accessory sanction -

The 90-day reporting order goes further than the press release suggested. It requires Meta to state in writing whether gallery information, or anything derived from it, reaches its systems before a user publishes, which is the question the authority could not answer from outside the app.

When the clock starts

PPC Land's November 14 report counted the 30, 60 and 90-day periods from the date of the press release, because the release gave no starting point. The decision supplies one for the 60-day and 90-day periods and for payment: notification of the decision to Meta. The published text does not give that date, and its signature line reads "Rome, _______________". Calendar deadlines cannot be fixed from the public record.

Appeals go to the ordinary courts under Article 78 of the GDPR, Article 152 of the Code and Article 10 of Legislative Decree 150 of September 1, 2011. The decision gives 30 days from communication of the measure, or 60 days if the appellant lives abroad. It does not say which applies to Meta, whose registered office is in Dublin and which elected domicile with Italian lawyers for the proceedings. The names of those lawyers are redacted in the published text.

The cloud feature in the same settings page

One of the decision's most open-ended passages starts in a footnote. In note 4 of its brief, Meta mentioned that the same settings page contains a separate feature, labelled in Italian "Ottieni idee creative su misura per te consentendo l'elaborazione nel cloud della galleria fotografica", which translates as "Get creative ideas tailored to you by allowing cloud processing of your photo gallery". According to Meta, it is presented as "New" and was launched in the European Union at the start of 2026 following a consultation with the DPC.

PPC Land reported in October 2025 that Meta had introduced opt-in camera roll suggestions in the United States and Canada that upload photos to its cloud on an ongoing basis. The decision does not connect the two, and the newer feature was outside the proceedings.

The authority nonetheless lists four questions it "cannot resolve on the current record". By its own name, the new feature involves cloud processing of gallery content, which is exactly what Meta denies for the feature under review. Because Meta says the system permission applies to the app as a whole, the new feature could rest on permissions users have already granted. It is unclear whether and how users are informed and asked to consent. And Meta's denial on AI training covers only "unpublished" content and is phrased as an intention, "does not intend", so it does not settle whether content processed in the cloud, or its derivatives, is or could be reused to develop its AI.

On that last point, the decision records Meta's November 2025 statement that its AI is trained only on content adult users make public or share with Meta AI in a prompt, unless they object. That matches the policy Meta set out in April 2025, when it said it would use public posts from adult accounts to train its models subject to an objection form.

None of this underpins the fine. But the authority reserves the right to open separate inquiries into the new feature, using requests for information under Article 157 of the Code and access, inspections and checks under Article 158, covering legal basis, information and consent, reuse of content for model training and the relationship with permissions already granted, and to coordinate with the DPC where competences overlap.

Why the reasoning travels beyond Facebook

The decision is framed around one feature in one app. Its reasoning is broader, and the authority says so.

Article 122, according to the decision, "is not limited to so-called tracking tools": it governs access to stored information "whatever the technology used", a point the Garante already made in its cookie guidelines of June 10, 2021. The decision also cites paragraph 11 of the EDPB guidelines, under which consent is needed even to read a read-only value through an operating system API, with reference to the Article 29 Working Party's 2014 opinion on device fingerprinting. The decision does not address advertising or measurement software, but its reading of "access" does not depend on whether the information read is a photo.

The burden-of-proof reasoning is equally portable. A company that says data never leaves the device, and runs closed code over encrypted connections, is expected to prove it with architecture descriptions, traffic records or independent verification. Screenshots of the interface were not enough.

The case also adds to a run of enforcement under national ePrivacy rules, which sit outside the one-stop shop. France's CNIL fined Google 325 million euros in September 2025, partly under its transposition of the same Article 5(3), and in October 2026 it fined Fnac 7 million euros after the retailer's app kept sending browsing activity to a recommendation service after users refused consent. In November, the EDPB's final guidelines indicated that cross-site ad tracking will rarely pass the legitimate interest test, and the Meta decision applies the same separation of regimes: storage and access to device information run on consent, whatever basis a company names for later processing. Meta's reliance on contract and legitimate interest for the feature, the decision says, could only ever apply to processing before and after the access.

Whether the fine survives is another question. An analysis PPC Land reported in May 2026 found that about 40% of the 7.1 billion euros in GDPR fines announced since 2018 had been annulled or were under challenge. The two routes open to Meta point in different directions: complying and paying 402.5 million euros ends the case, while an appeal would put the authority's reading of Article 122 before the Italian courts.

What the decision does not say

The published text gives no notification date, so the deadlines cannot be placed on a calendar, and it records no response from Meta after the brief of October 12. It does not establish whether gallery data leaves the device, whether the location permission is used, how many users granted access, or what the newer cloud feature does with photos. Whether the authority opens the inquiry it has reserved into that feature is not yet known.

Key facts

  • Authority: Garante per la protezione dei dati personali, Piazza Venezia 11, Rome
  • Source document: "Provvedimento del 13 novembre 2026 [10321455]", type "Ordinanza ingiunzione o revoca", register of measures no. 815 of November 13, 2026
  • Source URL: https://www.garanteprivacy.it/web/guest/home/docweb/-/docweb-display/docweb/10321455
  • Related press release: "Facebook: il Garante Privacy sanziona Meta per 805 milioni di euro", doc web 10321080, November 14, 2026; the Italian version links to the decision
  • Publication date of the decision page: not shown; the signature date in the published text is blank
  • Decision makers: Pasquale Stanzione (president and rapporteur), Ginevra Cerrina Feroni (vice president), Agostino Ghiglia (member); Luigi Montuori (secretary general)
  • Party: Meta Platforms Ireland Limited, Merrion Road, Dublin 4, D04 X2K5, registration number IE462932
  • Feature: "Ottieni suggerimenti dalla galleria quando navighi su Facebook", in the settings page "Suggerimenti da condividere provenienti dalla galleria", Facebook for Android, available since 2023 according to Meta
  • App versions: 548.1.0.51.64 analysed; 581 introduced changes to the setting, according to Meta
  • Android permissions declared: READ_MEDIA_IMAGES, READ_MEDIA_VIDEO, READ_MEDIA_VISUAL_USER_SELECTED, ACCESS_MEDIA_LOCATION
  • Violation: Article 122(1) and (2) of the Italian Privacy Code (Legislative Decree 196 of 2003), transposing Article 5(3) of Directive 2002/58/EC; no standalone violation of GDPR Articles 6, 7, 12 or 13
  • Fine: 805,000,000 euros under GDPR Article 83(5) via Article 166(2) of the Code; starting amount 700,000,000 euros; cap 6,841,395,745 euros
  • Settlement option: comply and pay half, 402,500,000 euros (PPC Land calculation), within the appeal period, under Article 166(8) of the Code
  • Appeal: ordinary court, 30 days from communication or 60 days for an appellant resident abroad
  • Prior measure cited: injunction order no. 134 of June 14, 2019, doc web 9121486, 1,000,000 euros
  • Complainant: Centro Tutela Consumatori Utenti di Bolzano (Verbraucherzentrale Südtirol), report of July 10, 2025
  • Technical report: Department of Digital Technologies and IT Security, prot. 76045 of May 18, 2026
  • Out of scope: the "Suggerimenti personalizzati da condividere provenienti dalla galleria" option, which Meta says was never available in Europe; the cloud processing feature launched in the EU in early 2026; AI training on unpublished content

Timeline

Summary

Who: The Garante per la protezione dei dati personali, Italy's data protection authority, and Meta Platforms Ireland Limited, which operates Facebook in the EU. The case began with a report from the Centro Tutela Consumatori Utenti di Bolzano and covers an estimated 18 million to 22 million Android users in Italy.

What: The full text of the decision behind the 805 million euro fine for accessing photos, videos and metadata through the "Get tips from your gallery while browsing Facebook" feature without specific consent or prior information, in breach of Article 122 of the Italian Privacy Code. It shows a 700 million euro starting point against a 6.84 billion euro cap, a 105 million euro increase for Meta's design control, a 2019 precedent and poor cooperation, five corrective orders, and the option to settle by complying and paying half.

When: The decision is dated November 13, 2026, and was announced on November 14. The 60-day and 90-day periods and the payment deadline run from notification to Meta, a date the published text does not give.

Where: Italy, with the decision adopted in Rome. The Garante kept the case because ePrivacy rules have no one-stop shop, and it will send the decision to Ireland's Data Protection Commission.

Why: The Garante holds that reading a phone's gallery is access to the user's device whether or not data leaves it, and that an app-wide Android permission granted to post a photo is not consent for a separate feature that scans the archive. It says the amount is also meant to signal to other companies that using generic operating system permissions for different purposes will be sanctioned significantly.