Technical Lead / Web, SaaS & AI
Home / Blog

Meta's €805M Fine: Facebook Was Reading Your Photo Gallery. Here's How to Turn It Off

Get new posts by email

Security alerts, SEO and web development guides, sent when they are published.
No spam. Unsubscribe anytime. Privacy Policy
Meta's 805 million euro fine: how to close Facebook's access to your photo gallery

Updated November 15, 2026 · Status: Meta plans to appeal · 60-day deadline to change the feature in Italy

One tap on a vague "enable other features" prompt was enough to give Facebook access to your entire photo gallery. On November 14, 2026, Italy's data protection authority put a price on that: a €805 million fine against Meta over Facebook gallery access on Android.

The ruling only applies in Italy. If you're in the US, the same feature is still sitting in your Facebook app, and nothing will change unless you change it yourself.

The 2-minute fix:

  1. In Facebook, open Settings and search for camera roll
  2. Turn off both camera roll toggles
  3. In your phone settings, set Facebook's photo access to None or Limited

Below is what happened, what the ruling did and didn't find, step-by-step instructions for Android and iPhone, and the lesson for anyone who builds apps.

Meta's €805M fine at a glance

Item Detail
Regulator Garante, Italy's data protection authority
Company Meta Platforms Ireland Limited
Fine €805 million (about $887 million, roughly 0.47% of Meta's global revenue)
Announced November 14, 2026
Feature "Get tips from your gallery while browsing Facebook" in Facebook for Android, available since 2023
Users affected About 20 million Android users in Italy
Finding Gallery access without specific, informed consent
Order Feature off by default and a separate consent prompt, within 60 days
Meta's response Plans to appeal, calls the fine "disproportionate"

Meta's 805 million euro fine at a glance: Italy's Garante fined Meta on November 14, 2026 over Facebook for Android reading photo galleries without specific consent, about 20 million users affected, 60 days to switch the feature off by default

What did Facebook do with your photo gallery?

The "gallery suggestions" feature

Since 2023, Facebook for Android has offered a feature that, while you scroll, shows you photos and videos from your phone's gallery as suggestions to post. Meta calls it "Get tips from your gallery while browsing Facebook."

To do that, the app needs to read your gallery. Once you grant full access, it can read the whole archive: photos, videos and the metadata attached to them, such as when and often where each one was taken.

The three consent problems the Garante found

The Garante's issue was not that the feature exists. It was how Facebook got permission to run it:

  1. One permission for many purposes. Gallery access was requested through a single permission that covered the whole app and several features with different purposes. Saying yes to one meant saying yes to all of them.
  2. A vague notice. The prompt talked about letting you "enable other features." According to the Garante, it didn't make clear that you were also switching on gallery suggestions.
  3. On by default. The feature was active unless you went looking for the setting and turned it off.

The Garante treats your smartphone as part of your private sphere. Under that view, any access to what's stored on it needs free and informed consent, whether or not data leaves the phone and whether or not anyone is harmed. The Garante decided that a broad permission, a vague prompt and a default-on setting don't add up to that.

One tap, many features: a single broad Facebook gallery permission with a vague enable other features prompt also switched on gallery suggestions by default

What the ruling did not find

It's worth being precise here, because headlines tend to run ahead of the facts:

  • No finding on AI training. The investigation did not examine whether gallery content was used to train AI models.
  • No finding that photos were sold or used for ads. The case was about access and consent.
  • Cloud processing is a separate question. The Garante said it may separately assess a newer feature, launched in 2026, that allows cloud processing of gallery content.

So the accurate takeaway is this: Facebook could read your gallery without asking you properly. That's serious enough on its own.

What Meta has to change in 60 days

In Italy, Meta must:

  • Turn the feature off by default, including for people who already granted gallery access
  • Ask for consent with a separate, specific prompt for this feature
  • Explain clearly what the feature does, that it accesses the gallery, and how to turn it off
  • Report back to the Garante on what it changed

If Meta misses the deadline, the feature can't be switched on for anyone in Italy without valid consent. Meta told Reuters it plans to appeal and called the fine "disproportionate." An appeal could take a long time, so the 60-day order is the part to watch.

Does this affect you in the US?

Not directly. The order covers Facebook users in Italy only. In the US, Meta has no regulator telling it to switch the feature off by default or to ask again.

That means your settings are whatever they were the day you installed or updated the app. If you tapped through a permission prompt without reading it, which most of us do, the gallery features may be on right now. The US has no single federal privacy law with a rule like the one Italy applied, so in practice the control sits with you.

The good news: it takes about two minutes to check and fix.

How to turn off Facebook gallery access (step by step)

There are two layers: the settings inside the Facebook app, and the photo permission in your phone. Do both. The app settings control what Facebook does, and the phone permission controls what it can reach at all.

Turn off Facebook gallery access in two layers: switch off both camera roll toggles in Facebook settings, then set photo access to None or Limited in Android or iPhone settings

Step 1: Turn off camera roll suggestions in the Facebook app

  1. Open the Facebook app and tap the menu (three lines, or your profile picture).
  2. Go to Settings & privacy → Settings.
  3. Tap the search box at the top of Settings and type camera roll. Menu labels change between app versions, so searching is the fastest route.
  4. Open Camera roll sharing suggestions.
  5. Turn off both toggles (they turn gray when off):
    • Get camera roll suggestions when you're browsing Facebook
    • Get creative ideas made for you by allowing camera roll cloud processing

If you only see one toggle, turn that one off. Some accounts don't have the cloud processing option yet.

Step 2: Limit photo access on Android

The exact wording varies a little between Samsung, Pixel and other phones, but the path is similar:

  1. Open Settings → Apps → Facebook → Permissions.
  2. Tap Photos and videos.
  3. Choose Don't allow, or Allow limited access if you still want to post photos from your phone.

With limited access, Facebook only sees the photos you pick. You can add more any time you post.

Step 3: Limit photo access on iPhone

  1. Open Settings → Privacy & Security → Photos.
  2. Tap Facebook.
  3. Choose None or Limited Access, then pick only the photos you want to share.

Step 4: Spend 5 minutes on your other apps

Facebook is not the only app with full photo access. While you're in your phone's privacy settings:

  • Open the photo permission list and look at every app with full access
  • Switch anything you rarely use to Limited or None
  • Do the same for Contacts, Location and Microphone
  • Set a calendar reminder to repeat this every three months

Most apps work fine with limited photo access. The ones that truly need full access, like a backup app, are usually obvious.

The lesson for anyone building apps and SaaS

This is the part I care about most as a developer. Meta isn't the only company that bundles permissions or ships data-hungry features switched on. Most teams do it because it's easier and it lifts adoption numbers. Italy has now shown what that shortcut can cost.

If you build mobile apps, SaaS products or browser extensions, here's what this ruling says about consent design:

  1. One feature, one permission request. Don't use a single "allow access" prompt to cover several features with different purposes. Ask for each one separately.
  2. Ask at the moment of use. Request gallery access when someone taps "add photo," not on first launch when they'll tap yes to anything.
  3. Default new data features to off. If a feature reads personal data in the background, let people opt in.
  4. Say exactly what you access and why. "Enable other features" is the kind of wording the Garante rejected. "Let us read your photo gallery to suggest pictures to post" is honest.
  5. Make turning it off as easy as turning it on. One toggle, easy to find, explained in plain words.
  6. Log consent. Record what someone agreed to, when, and which prompt text they saw. If a regulator or client asks, you can prove it.

Here's the difference in practice:

Weak prompt Strong prompt
"Allow access to enable other features" "Allow access to your photos so we can suggest pictures to post? You can turn this off in Settings."
Shown at first launch Shown when you tap "Add photo"
Covers the whole app Covers one feature
On by default Off until you choose it

Weak vs strong app permission prompt: a vague prompt at first launch covering the whole app and on by default, versus a clear prompt shown at the moment of use, covering one feature and off until chosen

The same pattern, convenience quietly turning into exposure, shows up in other places too. A "Don't ask again" setting in Claude Code ended up leaking secrets on GitHub, and third-party apps with broad store permissions led to checkout hijacking on Shopify. Every broad permission you grant or request should have a clear reason behind it.

What businesses should tell their staff

If your team uses personal or work phones that hold client photos, receipts, ID scans or documents, a social app with full gallery access is a real exposure. A simple policy covers most of the risk:

  • Social and messaging apps get limited photo access on any phone that holds work files
  • Camera roll suggestion and cloud processing features stay off
  • Staff review app permissions every quarter
  • Sensitive files live in a work app or managed folder, not the main camera roll

For the wider picture, my developer laptop security checklist and website security guide for small businesses cover the other devices and systems attackers target.

Not sure your app's permissions or your team's devices would pass this test? I've recovered 50+ attacked websites. Request a security review.

Meta Fine and Facebook Gallery Access FAQs

Why was Meta fined €805 million?
Italy's data protection authority found that Facebook for Android accessed users' photo galleries for a suggestions feature without specific, informed consent. It used one broad permission, a vague prompt and a default-on setting.
Does Facebook have access to my camera roll?
If you gave the app photo permission and the camera roll suggestion toggles are on, yes. It can read your gallery to suggest photos to post. Check both toggles in Settings and your phone's photo permission.
How do I stop Facebook from accessing my photos?
In Facebook, go to Settings & privacy, then Settings, search for "camera roll" and turn off both toggles. Then set Facebook's photo permission to None, Limited or Don't allow in your phone settings.
Does the Meta fine affect users in the US?
No. The order covers users in Italy. In the US, the feature stays as it is, so you need to change the settings yourself.
Does Meta use my gallery photos to train AI?
The Italian investigation did not examine AI training, so there is no ruling on it. Camera roll cloud processing is a separate toggle, and turning it off is the safest choice if you're unsure.
Is Meta appealing the fine?
Yes. Meta told Reuters it plans to appeal and called the fine disproportionate.
What is camera roll cloud processing on Facebook?
It's an optional setting that lets Facebook upload and process gallery content in the cloud to create things like collages and recaps. The Garante said it may assess this feature separately.
Should I give apps full access to my photos?
Only when an app genuinely needs it, like a photo backup app. For posting and messaging, limited or selected-photos access is enough.

Conclusion

The €805 million fine isn't about a hack or a leak. It's about a feature that read people's photo galleries behind a prompt that didn't clearly say so. Italy has drawn a line: access to what's on your phone needs specific, informed consent.

If you're in the US, that line doesn't protect you automatically, so draw it yourself: turn off both camera roll toggles, set Facebook's photo access to Limited or None, and spend five minutes checking your other apps. If you build apps, treat this as a free lesson in consent design. Ask for each permission separately, explain it in plain words, and leave data-hungry features off until people choose them.

If you want a second pair of eyes on your app's permissions, your website's security or your team's devices, see my website security services.

Sources: The Hacker News · Financial News · Which?

Get new posts by email
New guides and alerts, sent when they are published. No spam. Unsubscribe anytime.

Comments (0)

Related Blog

APT root flaw CVE-2026-109518 title graphic: a server rack with a package that is half verified and half tampered, linked to a hooded attacker, with the line Patch With Retries Off for Debian 12+ and Ubuntu 22.04+, fixed November 4
Security Alerts
  • 16 Nov 2026
  • <25
  • 0 Comment

APT CVE-2026-109518: Patch Your Debian and Ubuntu Servers Safely

APT CVE-2026-109518 can install a swapped package as root on Debian and Ubuntu. Patch APT with retries off, verify the version and rebuild Docker images.


WordPress update flaw CVE-2026-119977: block, then update. Exploited now, fixed in WordPress 7.1.4
Security Alerts
  • 14 Nov 2026
  • 75
  • 0 Comment

WordPress CVE-2026-119977: Why Updating Can Expose Your Site

WordPress CVE-2026-119977 is exploited, and the update to 7.1.4 itself can be raced. Block wp-content/upgrade first, then update and verify, step by step.


CVE-2026-124194 Outlook zero-day: update Office, not just Windows. Exploited, leaks NTLM hashes, patched November 10, 2026
Security Alerts
  • 13 Nov 2026
  • 60
  • 0 Comment

CVE-2026-124194: The Outlook Zero-Day Stealing Windows Passwords (and How to Patch)

CVE-2026-124194 is an exploited Outlook zero-day that leaks Windows NTLM hashes. Who is affected, why Windows Update is not enough, and how to patch Office.


,