Italy Fines Meta EUR 805 Million Over Facebook Gallery Access
Independently fact-checked against primary sources (last audited November 21, 2026). · 8 primary sources cited on this page. How we verify our legal content

Italy's data protection authority fined Meta Platforms Ireland Limited EUR 805 million on 13 November 2026 over a Facebook for Android feature that read users' photo galleries. The legal basis was Article 122 of the Codice privacy, not the GDPR.
Information last verified on November 21, 2026. This is a developing story; we update it as the record changes.
Status: The Garante per la protezione dei dati personali adopted the sanction on 13 November 2026 (register of provvedimenti no. 815, doc. web 10321455) and announced it in Rome on 14 November 2026. The full decision is published on the Garante's website in Italian with an official English translation. The decision is not final: under Article 152 of the Codice privacy and Article 10(3) of d.lgs. 150/2011 an opposition may be filed with the ordinary court within 30 days of communication of the decision, or 60 days for a party resident abroad. That window had not expired as at 21 November 2026, and we have found no record of a filed opposition on the Garante's site, which would not in any event ordinarily record a court filing, and no statement published by Meta itself; news reporting on 16 November 2026 said Meta had told other outlets it strongly disagreed and planned to appeal the amount, which it called disproportionate. We have not independently confirmed that statement with Meta.
Jurisdiction scope: This article covers an Italian administrative decision applying Italian law, specifically Article 122 of the Codice privacy and the ePrivacy Directive it transposes, to Italian Facebook users on Android devices. It does not cover any proceeding before the Irish Data Protection Commission, any other EU authority, or any US litigation about the same feature. All figures are in euro unless stated otherwise.
What Happened
The Garante per la protezione dei dati personali found that Meta Platforms Ireland Limited unlawfully accessed photographs, videos and the related metadata stored on Italian users' Android phones through the Facebook app, and fined the company EUR 805,000,000. The decision is Provvedimento del 13 novembre 2026, doc. web 10321455, entered in the authority's register of provvedimenti as no. 815 of 13 November 2026, with Pasquale Stanzione as both president and rapporteur. The Garante announced it the following day.
"Il Garante per la protezione dei dati personali ha sanzionato Meta Platforms Ireland Limited per 805 milioni di euro." Source: Garante per la protezione dei dati personali, press release, Rome, 14 November 2026 (doc. web 10321080). In English: the Garante has fined Meta Platforms Ireland Limited EUR 805 million.
The feature at the centre of the case is a setting called "Ottieni suggerimenti dalla galleria quando navighi su Facebook", which the Garante's English version of the press release renders as Get camera roll suggestions when you're browsing Facebook, and the decision's own English text as Get suggestions from your gallery whilst browsing Facebook. When it is active, the app reads the most recent items in the phone's gallery and offers them back to the user as ready-made post ideas. Meta told the authority the feature has been available since 2023.
The file opened on a complaint, not on the authority's own initiative. The Centro Tutela Consumatori Utenti of Bolzano, a consumer association, reported the change on 10 July 2025. The Garante's office sent Meta a formal request for information on 27 October 2025 and received a reply on 14 November 2025, then asked its own Digital Technologies and IT Security Department for a technical assessment on 2 December 2025. That assessment, delivered on 18 May 2026, installed the Facebook app fresh (package version 548.1.0.51.64) on an Android 14 handset and read the app's AndroidManifest declarations.
Three findings carried the decision. First, access to the gallery is requested through a single operating-system permission that applies to the whole app and covers several features with different needs. Second, that request is introduced by a generic notice, which in the Italian interface speaks of enabling other functions, so the user is not told that suggestions from the gallery are among the things being authorised. Third, the setting was preset to active, and once broad READ_MEDIA permission is granted it is, as a rule, permanent until the user revokes it in device settings. The manifest also declared ACCESS_MEDIA_LOCATION, the permission covering EXIF location metadata, which a single system prompt can sweep in without a second request.
The Garante was explicit about what it did not find. It did not establish that the feature accessed location data, that gallery content was transmitted to Meta's systems, or that special categories of data were processed. Nor did it examine whether content was used to train artificial intelligence, which Meta denies. What it did find was that Meta had created the conditions for all of those outcomes through broad, continuing and unverifiable access obtained under a permission requested for something else. The app is closed-source and its traffic is encrypted, so the authority recorded that it had no way to check what actually leaves the device. Meta said nothing does, but produced screenshots of interfaces rather than architecture documents, traffic logs, certifications or audits. The Garante treated that as a failure to prove the one fact Meta relied on to exclude its own liability.
The authority also noted that the conduct had not stopped. Meta shipped changes in version 581 of the app and published a Help Centre article in April 2026, but those reach only users who update, and the company did not say it had asked Italian users who had already granted system permission for fresh consent.

What the Law Actually Says
The charge is not a GDPR charge. Article 122 of the Codice in materia di protezione dei dati personali (the Italian Data Protection Code, d.lgs. 30 giugno 2003, n. 196, universally called the Codice privacy) is the national transposition of Article 5(3) of the ePrivacy Directive, and it governs one narrow thing: getting at information that is already sitting on someone's device. Its first paragraph, in the text in force since 19 September 2018, reads:
"L'archiviazione delle informazioni nell'apparecchio terminale di un contraente o di un utente o l'accesso a informazioni già archiviate sono consentiti unicamente a condizione che il contraente o l'utente abbia espresso il proprio consenso dopo essere stato informato con modalità semplificate." Source: Codice in materia di protezione dei dati personali (d.lgs. 30 giugno 2003, n. 196), art. 122, comma 1, text in force from 19 September 2018, via Normattiva.
In English, storing information on a subscriber's or user's terminal equipment, or accessing information already stored there, is permitted only if that person has consented after being informed in a simplified manner. Paragraph 2 adds that consent may be expressed through software or device settings, provided they are easy and clear to use. Those two paragraphs are what the Garante found Meta had breached. Paragraph 1 does not stop there. Its second sentence carries an exception the quotation above omits: consent is not required for technical storage or access used solely to carry out the transmission of a communication over an electronic communications network, or as strictly necessary for an information society service the user has explicitly requested. Meta argued in the alternative that gallery access was strictly necessary for an efficient and effective process of uploading photographs. The Garante rejected that at paragraph 3.6, reading the exception restrictively, noting that Meta itself describes the feature as an optional tool within the app rather than a service the user requested, and pointing to Android's photo picker as proof that the requested service can be delivered with access limited to the items the user selects.
Paragraph 2-bis matters here for what it does not do. It separately prohibits using an electronic communications network to reach information stored on terminal equipment. On the Garante's reading, paragraph 1 makes no network an element of the rule at all, and 2-bis is the only paragraph of Article 122 that does. The Garante charged paragraphs 1 and 2 and not 2-bis, and set out its reasons for that choice at paragraph 3.2 of the decision. That is why Meta's argument that the Facebook app is software rather than a network never engaged the provision actually relied on.
That distinction traces back to an amendment most readers will know only as the reason cookie banners exist. The 2002 original of Article 5(3) protected against "the use of electronic communications networks to store information or to gain access to information stored in the terminal equipment of a subscriber or user", and gave the user a right to refuse. Directive 2009/136/EC replaced that wording. The consolidated text now reads:
"Member States shall ensure that the storing of information, or the gaining of access to information already stored, in the terminal equipment of a subscriber or user is only allowed on condition that the subscriber or user concerned has given his or her consent, having been provided with clear and comprehensive information, in accordance with Directive 95/46/EC, inter alia, about the purposes of the processing." Source: Directive 2002/58/EC, art. 5(3), consolidated text as amended by Directive 2009/136/EC, via EUR-Lex.
The network is gone from the condition the rule attaches to, and an opt-out became consent. The rule now attaches to the device, not to the transport. Our explainer on the ePrivacy Directive's consent rule sets out how that same provision reaches cookies, pixels and local storage across the EU; this decision applies it to an operating-system media permission instead.
The Garante framed the protected interest in terms that do not depend on personal data at all:
"the provision is not a rule on the processing of personal data in the strict sense, but a rule safeguarding the integrity of the user's private sphere: it makes any access by parties other than the user to the user's terminal equipment and to the information stored therein subject to a free and informed choice by the user." Source: Garante, Provvedimento del 13 novembre 2026, doc. web 10321455, official English version, para. 3.1.
The consent standard itself is borrowed. Article 2(f) of the ePrivacy Directive points to the data subject's consent as defined in the GDPR, so Article 122 consent must be freely given, specific, informed and unambiguous, given per purpose, and incapable of arising from silence, inactivity or a pre-ticked box. That is the point the pre-set switch and the bundled permission failed, and it is the same test we describe in our guide to what counts as valid consent under the GDPR. The Garante treated the GDPR articles on consent and transparency as the yardstick for Article 122 and not as separate charges, and said so in terms: no separate breach of Articles 6, 7, 12 or 13 was established.
Why an Italian authority could act against an Irish company
The GDPR's one-stop-shop in Article 56 sends cross-border cases to the lead authority where the controller has its main establishment. Meta's position in the proceeding, as the decision records it, is that its main establishment for Facebook in the EU is Meta Platforms Ireland Limited in Dublin, so the Irish Data Protection Commission is the lead authority. The ePrivacy Directive has no equivalent. Each member state designates its own competent authority for the national transposing rules, and the GDPR cooperation and consistency machinery does not run over them.
The press release compresses this into a single clause, and the Italian text describes it as the ePrivacy framework rather than, as the authority's own English rendering has it, the ePrivacy Regulation. The instrument Article 122 transposes is Directive 2002/58/EC; there is no adopted ePrivacy Regulation. The full decision is more precise, and more interesting, than the announcement:
"With regard to jurisdiction, Meta itself acknowledges that the ePrivacy Directive does not provide for a one-stop shop mechanism and that the Data Protection Authority is competent to enforce the transposition provisions where applicable" Source: Garante, Provvedimento del 13 novembre 2026, doc. web 10321455, official English version, para. 3.3.
Meta did press a one-stop-shop objection, contesting the Garante's competence in favour of the Irish Data Protection Commission under Article 56 of the GDPR; what it conceded was that the ePrivacy Directive itself has no such mechanism, which left the whole jurisdictional question riding on whether Article 122 applied. So the real fight was not about the one-stop-shop. Meta conceded that ePrivacy has none, and argued instead that Article 122 and Article 5(3) simply did not apply to a feature operating on the device, relying on paragraphs 23, 32 and 44 of the European Data Protection Board's Guidelines 2/2023 on the technical scope of Article 5(3), the final version 2.0 of which the EDPB adopted on 7 October 2024 and published on 16 October 2024. If Article 122 did not apply, nothing was left for the Garante to enforce and the matter fell to the Irish Data Protection Commission under the GDPR alone. The jurisdictional question therefore collapsed into the substantive one, and the Garante resolved it by reading the guidelines as a whole rather than at paragraph 44, and by treating them as an interpretative aid that cannot narrow the text of the provision.
On authority, the decision cites EDPB Opinion 5/2019 and the Court of Justice's Facebook Belgium judgment for the proposition that storage and reading on terminal equipment sit under the Directive and outside the one-stop-shop, while the operations before and after remain GDPR matters for the lead authority. The Garante limited its own case to the access stage for that reason, and said the Irish authority's competence over subsequent processing is untouched. Its corrective measures are imposed directly under Article 58(2)(d) and (f) of the GDPR, with Article 157 of the Codice privacy supplying the power to demand information; the fine itself is imposed under Article 83(5) of the GDPR by way of Article 166(2) of the Code. For the wider division of labour between the national code and the Regulation, see our explainer on how the Codice privacy and the GDPR fit together in Italy.

How the Garante Got to EUR 805 Million
The arithmetic is set out in the decision, and it follows the EDPB's Guidelines 4/2022 on calculating fines.
The ceiling first. Article 83(5) of the GDPR caps the fine at EUR 20 million or 4 per cent of total worldwide annual turnover for the preceding financial year, whichever is higher. The relevant undertaking is the group, not the Irish subsidiary, because Meta Platforms Ireland Limited is wholly owned up a chain ending at Meta Platforms, Inc. The Garante recorded consolidated revenue of USD 200,966 million and net profit of USD 60,458 million for the year ended 31 December 2025 from Meta Platforms, Inc.'s Form 10-K, converted at the European Central Bank reference rate for that date (EUR 1 = USD 1.1750) to give turnover of about EUR 171,035 million. Four per cent of that is roughly EUR 6,841 million, so the EUR 20 million static cap was irrelevant.
The authority then graded the breach as of moderate seriousness, at the lower end of that band: national in scope, systemic, running since 2023, central to the platform's core business, negligent rather than intentional, with no proven individual harm, no established transmission and no special categories of data. For medium gravity the guidelines set a starting point between 10 and 20 per cent of the ceiling. The Garante took 10.2 per cent, or EUR 700,000,000.
Aggravating and mitigating circumstances moved it from there. The post-complaint app changes counted in Meta's favour, with moderate weight, because they were late and reached only users who updated. Against the company: its full control over the app's permission architecture, with no evidence it had separated the feature's request from the publishing permission; a prior Garante order, no. 134 of 14 June 2019 (doc. web 9121486), which fined Facebook Ireland Ltd and Facebook Italy S.r.l. EUR 1,000,000 jointly over the data of 214,077 Italian users on a generic notice and non-specific consent with pre-selected settings; and, weighted most heavily, poor cooperation. On that last point the decision is pointed: Meta presented as voluntary a cooperation the law requires, gave inaccurate information about the configuration status in its November 2025 reply, produced screenshots rather than technical evidence, and declined to say how many users had granted the permission even after being asked, leaving the authority to reconstruct the roughly 20 million figure from AGCOM, DataReportal and Statcounter data.
The balance came out aggravating, lifting EUR 700 million to EUR 805,000,000, which is 11.7 per cent of the ceiling, about 0.47 per cent of worldwide turnover and about 1.56 per cent of 2025 group net profit. The Garante checked that figure against Article 83(1):
"the amount cannot be absorbed as a mere business cost by an undertaking of this size, which ensures specific deterrence; it also signals to market participants that the use of generic operating system permissions to access users' content for different purposes is subject to significant penalties" Source: Garante, Provvedimento del 13 novembre 2026, doc. web 10321455, official English version, para. 6.2.
Publication of the order on the Garante's website was imposed as an additional penalty under Article 166(7) of the Code.
What Happens Next
Several deadlines run from notification of the decision, not from its announcement.
Within 60 days, under Article 58(2)(d) of the GDPR, Meta must bring the feature into compliance for Italian Facebook users on Android: a separate, specific consent request not bundled with permission to post photos and videos and free of generic phrasing; clear information at the point of the request about the purpose, the gallery access it involves and how to switch it off; the feature off by default; the same fresh consent sought from users who had already granted system-level permission; and setting state matched to actual processing across every app version in use in Italy, including by server-side checks or forced updates.
If that deadline passes without action, a prohibition bites under Article 58(2)(f): the feature may not operate for Italian Android users who have not consented in the specified way, and Meta may not process information obtained through it.
Within 30 days Meta must tell the Garante what it has initiated, and within 90 days what it has actually implemented, with technical documentation, interface screenshots, a statement on whether gallery information or anything derived from it reaches Meta's systems before publication, and the number of Italian Android users who have consented under the new flow.
Separately, Article 166(8) of the Codice privacy offers a settlement route: a sanctioned party may close the matter by complying with the authority's prescriptions and paying half the fine, within the period allowed for filing an opposition. On these figures half the fine is EUR 402,500,000. The alternative is opposition to the ordinary court under Article 78 of the GDPR, Article 152 of the Code and Article 10 of d.lgs. 150/2011, within 30 days of communication or 60 days for a party resident abroad. There is precedent for that route: the 2019 order records that Facebook Ireland had taken the related provvedimento of January 2019 to the Tribunale di Roma. Payment of the EUR 805 million, absent settlement, falls due 60 days after notification, with enforcement under Article 27 of Law 689/1981 if it is not made.
One further thread stays open. The Garante expressly reserved the right to investigate a different, newer setting, launched in the EU in early 2026, that allows cloud processing of gallery content, including its legal basis, its information and consent, any reuse of content for model training, and its relationship with the system permission already granted. It said it may use its information-gathering and inspection powers under Articles 157 and 158 of the Code and may coordinate with the Irish authority on the parts that fall to it.
Analysis: Why This Matters
The following is analysis from the Recording Law Editorial Team.
The headline number will travel further than the reasoning, and the reasoning is the part that changes how device permissions get argued about.
Two framings of a mobile app have coexisted comfortably for years. In the first, a permission dialog is a contract term: the user taps allow, and the scope of the permission is the scope of the consent. In the second, which Article 122 and Article 5(3) express, each distinct purpose for reaching into the device needs its own informed choice before access happens. The Garante's decision says the second framing governs, and that the operating system's permission model is Meta's design problem rather than its defence. The decision records Meta's own submission that Android permissions apply to the app as a whole, and treats that as the reason a separate in-app consent was required, not as an excuse for its absence.
The jurisdictional mechanics deserve more attention than the fine. For years the practical answer to a privacy complaint against a large platform in Europe has been that it belongs to the lead authority in Ireland or Luxembourg. The ePrivacy Directive is the gap in that arrangement, and it is not a loophole: it is the deliberate consequence of a directive that predates the GDPR and was never folded into its cooperation machinery. On the reasoning in this decision, a national regulator can enforce its own transposition of Article 5(3) directly, without routing the case to a lead authority at all. What makes the decision notable is scale rather than novelty. The same provision is the one behind the EU's cookie-consent regime; applying it to an operating-system media permission, and measuring the penalty against a group-level turnover ceiling, is what turns a familiar rule into a nine-figure exposure.
That also sets the real stakes of an appeal. Both sides agreed there is no one-stop-shop under ePrivacy, so a court reviewing this decision would be asked whether a feature that reads the gallery through system APIs constitutes gaining access to information already stored within the meaning of Article 122, and whether EDPB Guidelines 2/2023 can narrow the statutory text. Those questions are genuinely open, and we take no view on how a court would answer them. A ruling either way would matter well beyond Italy, because every member state has a version of this provision.
The cooperation findings are worth separating from the privacy findings, because they moved real money. The Garante treated closed-source code and encrypted traffic as a reason to demand more from the controller, not less, and treated the absence of architecture documents or logs as a failure to discharge the burden of proving the fact Meta relied on. It then reconstructed the affected population from public sources after the company declined to supply the number only it held. In a regime where the ceiling is a percentage of group turnover, the record a company builds during an investigation is a quantifiable line item.
Finally, note what this decision is not. It is not a finding that Facebook uploaded Italians' private photographs, and it is not a finding about AI training. The Garante said so expressly on both points, and the distinction will be lost in most retellings. Its holding is narrower and harder to escape: a company that arranges to be able to read an entire photo library, under a permission obtained for a different purpose, has already interfered with the private sphere the provision protects, whether or not anything was ever read or sent.
How This Affects You
For Facebook users in Italy on Android, nothing changed automatically when the fine was announced. The order gives Meta 60 days from notification to redesign the consent flow, and the remedy expressly reaches users who had already granted gallery permission, so people who never revisited the setting are inside its scope. In the meantime the switch sits on the Facebook app's gallery sharing-suggestions settings page, and media permissions can be reviewed or withdrawn in Android's own app-permission screens. Nothing in the decision requires a user to do anything, and nothing in it awards users any payment: an administrative fine under the Codice privacy is a penalty, not compensation.
For anyone building or publishing an app that reads device content in the EU, the operative lesson is sequence. Article 122 and Article 5(3) require information first, then consent, then access, and they attach to each purpose rather than to the app. A permission that an operating system grants app-wide does not supply the specificity the provision demands; a default-on switch does not supply consent at all. Where a feature needs broader or continuing access than a single-item picker provides, the decision indicates that a request tied to that feature alone, off by default, is what compliance looks like. Anyone considering a complaint about processing in Italy can read how the authority handles them in our guide to the Garante and how complaints reach it; the file here began with exactly such a report from a consumer association.
Readers outside Italy should not read across. This is Italian law applying an EU directive through national transposition, and both the competent authority and the enforcement route differ by member state.
This is general legal information, not legal advice. It covers Italian law, specifically Article 122 of the Codice in materia di protezione dei dati personali (d.lgs. 196/2003) and the ePrivacy Directive 2002/58/EC it transposes, and reflects sources verified on November 21, 2026. Laws change and this story is developing; consult a lawyer licensed in your jurisdiction about your specific situation.
Related articles
- How the Codice privacy and the GDPR fit together in Italy
- The Garante and how complaints reach it
- The ePrivacy Directive's consent rule
- What counts as valid consent under the GDPR
- An earlier Garante decision on employee email monitoring
Last updated: 2026-11-21. This is a developing story; details verified as of 2026-11-21.
Frequently Asked Questions
Is the EUR 805 million fine against Meta final?
No. The Garante adopted the sanction on 13 November 2026, but under Article 152 of the Codice privacy and Article 10 of d.lgs. 150/2011 an opposition may be filed with the ordinary court within 30 days of notification, or 60 days for a party resident abroad. As at 21 November 2026 we have found no record on the Garante's site of an opposition having been filed.
Why could Italy's regulator fine a company established in Ireland?
Because the charge rests on Article 122 of the Italian Codice privacy, which transposes the ePrivacy Directive, and that directive contains no one-stop-shop mechanism directing cross-border cases to a lead authority. The decision records that Meta accepted this and argued instead that Article 122 did not apply to the feature at all.
What did the Garante find Meta did wrong?
That the Facebook app for Android accessed photos, videos and related metadata on Italian users' phones for the gallery-suggestions feature without separate, specific, informed consent for that feature and without adequate prior information, in breach of Article 122, paragraphs 1 and 2, of the Codice privacy. Gallery access was bundled into one app-wide permission introduced by a generic notice, and the feature was preset to active.
Did the Garante find that Meta used people's photos to train AI?
No. The decision states expressly that the possible use of content for artificial intelligence training was not part of the proceeding and that Meta denies it. The Garante reserved the right to investigate separately a newer setting, launched in the EU in early 2026, that allows cloud processing of gallery content.
Could the EUR 805 million be reduced?
Article 166(8) of the Codice privacy allows a sanctioned party to settle by complying with the authority's prescriptions and paying half the fine within the period for filing an opposition, which on these figures would be EUR 402,500,000. A court hearing an opposition could also annul or vary the decision. We make no prediction about either outcome.
What must Italian Facebook users on Android do now?
Nothing is required of users. The order obliges Meta, within 60 days of notification, to ask for separate consent and keep the feature off by default, including for users who had already granted system permission. Users who want to act sooner can switch off the gallery sharing-suggestions setting in the Facebook app and review media permissions in Android's app-permission settings.
Updates
Independently fact-checked against the cited primary sources
Sources and References
- Garante per la protezione dei dati personali, Provvedimento del 13 novembre 2026, doc. web n. 10321455, register of provvedimenti no. 815 of 13 November 2026 (ordinanza-ingiunzione against Meta Platforms Ireland Limited; the full decision with official English translation, supporting the EUR 805,000,000 figure, the finding under art. 122(1) and (2) of the Codice privacy, the fine methodology from the EUR 6,841,395,745 ceiling and the EUR 700,000,000 starting point, the 60/30/90-day remedial deadlines, the art. 166(8) half-payment option and the art. 152 opposition route)(garanteprivacy.it).gov
- Garante per la protezione dei dati personali, press release 'Facebook: il Garante privacy sanziona Meta per 805 milioni di euro', Rome, 14 November 2026, doc. web n. 10321080 (the authority's own account of the sanction, the roughly 20 million affected Italian Android users, the 0.47 per cent of worldwide turnover figure, and the rejection of Meta's jurisdictional objection; includes an official English version)(garanteprivacy.it).gov
- Codice in materia di protezione dei dati personali, d.lgs. 30 giugno 2003, n. 196, art. 122, text in force from 19 September 2018, Normattiva (verbatim text of paragraphs 1, 2 and 2-bis, supporting the quoted consent requirement and the point that only paragraph 2-bis refers to an electronic communications network)(normattiva.it).gov
- Directive 2002/58/EC (ePrivacy Directive), consolidated text of 19 December 2009 as amended by Directive 2009/136/EC, art. 5(3), EUR-Lex CELEX 02002L0058-20091219 (verbatim current wording of the consent requirement for storing or gaining access to information in terminal equipment)(eur-lex.europa.eu).gov
- Directive 2002/58/EC (ePrivacy Directive), original text as published in OJ L 201, 31 July 2002, art. 5(3), EUR-Lex CELEX 32002L0058 (the pre-2009 wording referring to 'the use of electronic communications networks', supporting the comparison with the amended text)(eur-lex.europa.eu).gov
- European Data Protection Board, Guidelines 2/2023 on the technical scope of Article 5(3) of the ePrivacy Directive, final version 2.0, published 16 October 2024 (the guidance Meta relied on and the Garante construed as a whole rather than at paragraph 44)(edpb.europa.eu).gov
- Garante per la protezione dei dati personali, Ordinanza ingiunzione nei confronti di Facebook Ireland Ltd e Facebook Italy s.r.l., 14 June 2019, provvedimento n. 134, doc. web n. 9121486 (the EUR 1,000,000 fine over the data of 214,077 Italian users, treated as an aggravating prior infringement in the 2026 decision, and the record that Facebook Ireland had taken the related provvedimento to the Tribunale di Roma)(garanteprivacy.it).gov
- Garante per la protezione dei dati personali, Provvedimenti recenti listing, consulted 21 November 2026 (used to locate the published decision of 13 November 2026 and to check that no later related measure appears on the authority's register)(garanteprivacy.it).gov
- Suzanne Smalley, report on the Garante's EUR 805 million fine against Meta, Recorded Future News (The Record), 16 November 2026 (headline 'Italian regulator fines Meta $886 million for violating data privacy law'; reports the fine as EUR 805 million with its own USD conversion, and paraphrases Meta as strongly disagreeing, planning to appeal and calling the amount disproportionate; also reported by Italian outlets on 16 November 2026)(therecord.media)
- 'Italy fines Meta $880m over photo privacy', Al Jazeera with AFP and Reuters, 14 November 2026 (contemporaneous report stating that Meta had not yet publicly commented and that it has a right of appeal; supports the dated state of Meta's public position on announcement day)(aljazeera.com)