Garante fines Meta EUR 805 million over Facebook for Android gallery access; the release prints no turnover
The Garante's press release of 14 November 2026 fines Meta Platforms Ireland Limited EUR 805 million over a Facebook for Android feature that suggests photos from the phone gallery. It prints about 20 million users and about 0.47% of turnover, but no turnover figure.
By Parminder Kumar Sharma · LinkedIn · · 16 min read
About EUR 40 per Android user, on a turnover the release never prints
The Garante's press release of 14 November 2026 fines Meta Platforms Ireland Limited EUR 805 million and prints two figures that invite arithmetic: "around 20 million Android users in Italy" and a fine that is "about 0.47% of the group's global revenue". Divide the fine by the users and the result is EUR 40.25 per Android user in Italy (derived: 805,000,000 divided by 20,000,000). Work back from the percentage and the group's turnover comes to about EUR 171 billion (derived: 805 million divided by 0.0047), or anything from EUR 169.5 billion to EUR 173.1 billion if the printed 0.47% is itself rounded (derived: 805 million divided by 0.00475 and by 0.00465). The release prints no turnover figure of its own, and its Italian text says "circa lo 0,47%", so the second number rests on a rounded percentage and a turnover this site has to infer.
What those two figures do not establish. EUR 40.25 is a quotient, not a per user penalty: the release does not say the fine was built from a per user amount, and it does not say all 20 million had the feature switched on. It gives the 20 million as the size of the group of people involved, one of four factors in setting the amount. The release also does not say which year of turnover the 0.47% is taken from, or what the group is counted as. No comparison with any other fine is made here, because the saved page prints none.
Whose account this is matters. The page is a press release from the Italian data protection authority, the Garante per la protezione dei dati personali, describing its own decision. It is not the decision text, which this site has not read. The Garante both took the decision and wrote the account of it, and the findings below are its findings, attributed throughout and given no verdict by this site. Meta's position appears in the release only through the Garante's words: it rejected Meta's objection on jurisdiction, and it says Meta denies the potential use of the content to train AI. The saved page prints no statement from Meta and says nothing about an appeal. Coverage by other outlets was not read. The release prints the fine in euros only, so any figure in dollars would be a conversion made by the outlet that prints it, and none is repeated here.
What the Garante says happened, in its order
The release is about one feature of the Facebook app for Android. Its Italian name is "Ottieni suggerimenti dalla galleria quando navighi su Facebook" and the English text gives it as "Get tips from your gallery while browsing Facebook". The release says it has been "available since 2023" and, while a person browses, shows photos and videos from the phone's gallery as suggestions to post. The investigation was "launched in July 2025" after a complaint by a Bolzano consumer protection centre and used a technical analysis made by the Authority itself. Through the app, the release says, the company "accessed photos, videos, and related metadata stored on Italian users' smartphones" without specific consent and without properly informing them.
The release lists three findings. Access to the gallery is requested through "a single permission, valid for the entire app and for several functions serving different purposes". That permission is preceded by a generic notice, "enable other features", which in the Garante's words does not let users understand that they are also authorising gallery suggestions. And "the feature was enabled by default". The release then adds a general statement, and its wording is conditional: "If fully granted, such authorisation allows the app to read the entire photo archive on the device, on an ongoing basis", without the user or the Authority being able to verify what is actually used. That is a description of what a full grant of this kind makes possible. It is not a finding that every photo was read, and the release does not say how many were.
The legal basis is "Article 122 of the Privacy Code implementing the European ePrivacy Directive", which the Garante says protects the smartphone as part of a person's private sphere. Any access to what the phone holds, it says, needs free and informed consent, "regardless of whether the data is transmitted or any harm occurs". That sentence is a statement about the law. It is not a finding that nothing was transmitted or that nobody was harmed; the release is silent on both.
Two further points shape the decision. The Garante rejected Meta's objection that the Irish authority had jurisdiction, "because the ePrivacy rules do not provide for the 'one-stop-shop' mechanism". And it limited the case: the procedure "did not concern the potential use of content to train artificial intelligence", and it reserves a separate assessment of a new feature, launched in 2026, that allows cloud processing of gallery content. The release does not describe that new feature beyond those words.
What Meta is ordered to do, and by when
The release lists four orders. The table sets each beside the Garante's wording and what the text leaves open.
The orders as the Garante's release states them (English text, with the Italian checked beside it). Source: the Garante's press release of 14 November 2026.
| Order | Deadline | What the release does not say |
|---|---|---|
| Ask for consent through "a separate and specific request for the feature", explain what it is for, that it involves gallery access, and how to disable it | Within 60 days | When the 60 days start; what a valid request must look like beyond those words |
| Keep the feature "switched off by default, even for those who have already given consent" | Within 60 days | How the switch off is to be applied to existing installs; who checks |
| After the deadline without compliance, the feature "cannot be activated for users who have not given valid consent" | After the 60 days | Whether any further step follows a failure to comply |
| Tell the Garante the initiatives undertaken, then the measures adopted | Within 30 days, then within 90 days | The form of the reports; whether the Garante will publish them |
The release is dated Saturday 14 November 2026 (derived: the calendar). It does not say that the 30, 60 and 90 days run from that date, from notification to Meta, or from anything else. If they were counted from the release date, which is an assumption and not a statement of the Garante, the three dates would be 14 December 2026, 13 January 2027 and 12 February 2027 (derived). The release also does not say whether the decision is final or open to challenge, so whether the clocks are running, paused or contested is not established by anything saved here.
The numbers the release prints, and the ones this site worked out
The release prints these numbers: EUR 805 million, about 20 million users, about 0.47%, the periods of 60, 30 and 90 days, and the dates 2019 (a previous decision), 2023 (the feature), July 2025 (the probe) and 2026 (the new cloud feature). The next figures are this site's. The table keeps them apart so that a derived number is never read as the Garante's.
Figures in the Garante's release and in this briefing, with what each does not tell the reader. Source: the Garante's press release of 14 November 2026; derived figures are this site's arithmetic.
| Figure | Printed or derived | What it does not tell you |
|---|---|---|
| EUR 805 million | Printed | Which penalty provision it was set under; how the amount was calculated beyond the four listed factors |
| About 20 million Android users in Italy | Printed, as the number of people involved | How many had the feature on; whether it counts installs, accounts or people |
| About 0.47% of global turnover | Printed, with "circa" in the Italian | The turnover figure, its year, or which companies the group covers |
| EUR 40.25 per Android user | Derived: 805,000,000 divided by 20,000,000 | That any per user amount was used. It is a quotient |
| About EUR 171 billion turnover | Derived: 805 million divided by 0.0047; 169.5 to 173.1 billion if rounded | The group's actual turnover, which the release does not print |
| Available since 2023 | Printed | The month; whether every Android version had it from then |
| Investigation from July 2025 | Printed | The day; the length of the probe. Derived: 15 to 16 months to 14 November 2026, depending on the day in July |
The release names the factors behind the amount. The Garante considered the high number of people involved, the duration of the breach, a previous 2019 decision against the company and limited cooperation during the investigation; it treated as mitigating the changes made after the complaint, though it judged them late and limited to users who update the app. It prints no weight for any factor and no arithmetic from the factors to the 0.47%. Which of them moved the amount most cannot be read from the page.
Words doing the work of consent
A label is not a control. Several words in this case describe a state of consent without being one, and the release is explicit about where. The table sets each label beside what the release says.
Labels in the case and what the Garante's release says about each. Quoted words are the release's. Source: the Garante's press release of 14 November 2026.
| Label | What the release says | What it does not say |
|---|---|---|
| The feature's name, "Get tips from your gallery while browsing Facebook" | It shows photos and videos from the phone gallery as suggestions to post; a full grant would let the app read the whole archive | What the app actually read, or whether it left the phone |
| The notice, "enable other features" | Generic: users cannot understand that they also authorise gallery suggestions | The screen itself; its layout, wording in other languages, or date of introduction |
| "permission" (the English text) or "autorizzazione" (the Italian) | One permission for the whole app and several purposes; the law needs a separate, specific consent | Any permission name or Android setting |
| Preset on | The feature was enabled by default | How many users it applied to |
| Changes after the complaint | Treated as mitigating, judged late and limited to users who update the app | What the changes were |
The distinction that matters is between the two things users are asked for. The release uses one word, "autorizzazione", for the technical grant the phone shows, and a different one, "consenso", for what the law requires. In the Garante's account a permission granted for one purpose, under a generic notice, is not consent for another purpose it never named. That is the Garante's reading of the law as stated in its release, and this site reports it as such. The release prints no permission name, no app version and no screen, so nothing here shows what a user saw.
Where the Italian and English texts differ
The page prints the Italian text first and then an English version, and the two are not word for word. The differences below are reported and left as they are: the page does not say which text governs. The most consequential difference is in the first row.
Differences between the Italian and English texts of the Garante's release of 14 November 2026. Each cell quotes the page; this site resolves none.
| Point | Italian text | English text |
|---|---|---|
| Who the breach is still ongoing for | "tuttora in corso per chi non ha aggiornato l'app e per chi ha già concesso l'autorizzazione al sistema" | "still ongoing for those who have not updated the app" |
| How a full grant reads the archive | "di regola in modo permanente" | "on an ongoing basis" |
| Cooperation | "la scarsa collaborazione prestata durante l'istruttoria" | "the limited cooperation during the investigation" |
| The mitigating factors | "ha valutato come attenuanti le modifiche introdotte dopo la segnalazione" | "It treated as a mitigating factor the changes made after the complaint" |
| A subheading | A subheading states the 60 day order and separate consent: "Entro 60 giorni la funzione dovrà essere disattivata per impostazione predefinita e il consenso chiesto in modo distinto" | No subheading before the text |
| The word for the grant | "un'unica autorizzazione" | "a single permission" in the first finding, then "the authorisation" |
The first row is the one that changes meaning. The Italian text says the breach continues for two groups, users who have not updated the app and users who already granted permission to the system, so a user who updated could still be inside the breach if they had granted permission earlier. The English text names only users who have not updated. The second row matters for the same reason: "di regola" means as a rule, and the English text drops that hedge. This site follows the Italian wording where the two differ and says so, because the Italian text is the one the page prints first. The English text is described on the page as a version. A reader relying on the English alone gets a smaller picture of who is still affected.
Coverage by other outlets was not read, so no line by line comparison with it is possible. The one difference worth stating without reading it is currency: the release gives the fine only in euros, so any figure in dollars is a conversion made by the outlet that prints it.
What the release states, and what it does not
The Garante's press release of 14 November 2026: stated and not stated, as read on 15 November 2026.
| Topic | Stated | Not stated |
|---|---|---|
| The decision | A fine of EUR 805 million on Meta Platforms Ireland Limited; release dated 14 November 2026 | The decision's own text, number and date; whether it is final or can be appealed; any Meta statement or plan to appeal |
| The feature | Its name, availability since 2023, suggestions shown while browsing | The month it began; which Android versions; any permission name, version number or screen |
| The access | The company accessed photos, videos and metadata without specific consent; a full grant would allow reading the whole archive | How many users had it on; how many photos or videos were read; whether any content left the phone. The Garante says transmission does not matter to the breach |
| The law | Article 122 of the Privacy Code, implementing the ePrivacy Directive; no one-stop-shop route | The penalty provision, any ceiling or tariff, or other national authorities' action |
| Meta's position | Objection on jurisdiction rejected; Meta denies the potential use of content to train AI | Meta's own words; what its post complaint changes were; whether it will comply |
| The orders | Consent request, default off, reports at 30 and 90 days, all within a 60 day main deadline | When the clock starts; the consequence beyond the feature being blocked |
| The amount | Four factors considered and one mitigation; about 20 million users; about 0.47% of global turnover | A turnover figure or year; how the factors were weighted; how the amount was calculated |
| The 2026 cloud feature | Launched in 2026, allows cloud processing of gallery content, reserved for separate checks | What it does, when it launched, whether it is available in Italy, any link to AI training |
What to do, in order
First, the steps the Garante ordered. These are orders to Meta, not to readers, and the release is the only source for them.
Take this with you
The Garante's orders to Meta, as the release states them
- Within 60 days, ask for consent through a separate and specific request for the feature, and explain what it is for, that it involves gallery access and how to disable it.
- Keep the feature switched off by default, even for users who already gave permission. If the deadline passes without compliance, the feature cannot be activated for users without valid consent.
- Tell the Garante within 30 days the initiatives undertaken and within 90 days the measures adopted.
Then the suggestions below, which are this site's and not the Garante's. None depends on the decision text, which this site has not read.
Take this with you
This site's suggestions, by reader
- Android Facebook users (this site's suggestion): the release says the feature was enabled by default. Look at the photo and video access the Facebook app holds in the phone's app permission settings, and at whether the feature the release calls Get tips from your gallery while browsing Facebook is on in the app. The release does not say where either setting sits, and this site does not either.
- App makers (this site's suggestion): one permission that covers several features with different purposes is the pattern the Garante criticises. Asking separately for each feature, with a notice that names it, is what the Garante ordered of Meta.
- Compliance teams (this site's suggestion): the Garante applied the ePrivacy rule and found no one-stop-shop route, so the Garante rejected the argument that the Irish authority should lead. What that means for your own estate is a question for your counsel, not for this briefing.
- Journalists and readers comparing coverage (this site's suggestion): check the currency of every figure, whether the outlet read the release or a relay, and whether it prints a turnover. The release prints none, and it prints the amount in euros only.
- Everyone (this site's suggestion): keep the release, and watch for the decision text and for any statement from Meta. Neither is in the saved page, and either could change what is stated above.
The question the release leaves open
The Garante says a violation can be complete without any transmission or harm, says the user and the Authority could not verify what the app used, and lists four factors and one mitigation. It does not print a turnover, the weight of any factor, how many people had the feature on or what was read. If the breach rests on what the app could read rather than on what it did, what will the decision text show about the road from about 20 million users to EUR 805 million, and from which turnover to 0.47%?
Sources
- PrimaryPress release, Facebook: il Garante Privacy sanziona Meta per 805 milioni di euro, Italian text then English version, dated Rome 14 November 2026 (docweb 10321080): the findings, the legal basis, the orders, the fine factors and the percentage. A regulator's press release, not the decision text. Saved by the lead on 15 November 2026Garante per la protezione dei dati personali (Italian data protection authority)accessed 2026-11-15


