Skip to main content
Commerce Security logo, "All 12 PCI DSS Requirements in Plain English," "Get it now for free," "Complete Survival Guide" and a button toclick to get it
Meta's €805M Fine Shows How One Permission Prompt FailsConsent Principles
4 min readFor Data Governance Teams

Meta's €805M Fine Shows How One Permission Prompt Fails

The Italian Data Protection Authority fined Meta Platforms Ireland Limited €805 million over a gallery feature in the Facebook app for Android. This case illustrates how a single permission prompt, a default-on setting, and jurisdictional arguments can all fail. Here's the breakdown.

Incident Overview

Meta accessed photos, videos, and related metadata on Italian users' devices through the Facebook app without specific consent or adequate information. The feature, "Get suggestions from gallery when browsing Facebook," suggested gallery content for posting while users browsed.

The Authority identified three issues. First, gallery access was requested through a single permission covering multiple functions with different needs. Second, a generic warning ("enable other functions") failed to inform users they were authorizing gallery suggestions. Third, the feature was enabled by default. Approximately 20 million Android users in Italy were affected.

The violated provision was Article 122 of Italy's Privacy Code, implementing the ePrivacy Directive. The proceedings didn't address whether content was used to train AI; Meta denies that.

Timeline

  • 2023: The gallery suggestions feature launches.
  • 2019: A previous action against Meta, considered an aggravating factor.
  • July 2025: Investigation begins after a report from the Bolzano Consumer Protection Center, supported by the Authority's technical analysis.
  • Post-report: Meta makes changes, but the Authority views them as belated and limited to users who updated the app.
  • November 14, 2026: The fine is announced.
  • Within 30 days: Meta must notify the Authority of initiatives started.
  • Within 60 days: Meta must request separate, specific consent for the feature and keep it disabled by default, including for users who previously granted authorization.
  • Within 90 days: Meta must notify the Authority of the measures adopted.

If the 60-day deadline passes without adjustment, the feature can't be activated for users who haven't given valid consent.

Failed Controls

No Granularity. One permission bundled several functions. Users couldn't decline gallery suggestions without losing other capabilities.

Weak Purpose Disclosure. "Enable other functions" didn't inform users their photo archive would be used for suggestions. Users couldn't know what they were authorizing.

Default-on Activation. The feature was enabled by default, contrary to Data Protection by Default, meaning no clear affirmative action was tied to this specific use.

Unverifiable Scope. The Authority noted that a fully granted gallery permission typically allows the app to read the entire photo archive permanently. Neither users nor regulators could verify which information was used. A control you can't audit is indefensible.

Stale Consent. Users who had already granted permission remained exposed, prompting the Authority to order the feature disabled even for them. Consent obtained under a defective request doesn't become valid over time.

Slow Remediation. Fixes came only after a complaint and only reached users who updated the app. The Authority cited the violation as ongoing and noted a lack of cooperation during the investigation.

Compliance Requirements

Article 122 of the Privacy Code implements Article 5(3) of the ePrivacy Directive. The Authority views a smartphone as part of a person's private sphere, requiring free and informed consent for any Terminal Equipment Access. Three points matter for your team:

  1. Access, Not Harm, Triggers Consent. Consent is required regardless of data transmission or harm. Reading the gallery is enough.
  2. Informed and Specific Consent. The consent standard borrows from the GDPR, so the EDPB Guidelines on consent apply: granularity, purpose disclosure, and clear affirmative action. A bundled prompt with a vague label fails all three.
  3. No One-Stop-Shop Shield. Meta argued the Irish authority had jurisdiction. The Italian Authority rejected this, as ePrivacy legislation doesn't provide a one-stop-shop mechanism. Any member state authority can enforce its national ePrivacy implementation against you, even if your main establishment is elsewhere.

Action Items for Your Team

  1. Inventory Permissions. Map each OS-level permission to each feature relying on it. If one permission supports multiple purposes, you have a granularity problem. Fix it before a regulator finds it.

  2. Add In-App Consent Steps. The system dialog can't carry your purpose disclosure. Build a separate, feature-specific request that states what the feature does, what access to the gallery means, and how to turn it off. This mirrors what the Authority ordered Meta to do.

  3. Ship Sensitive Features Off by Default. Treat data protection by default as a release gate. If a feature reads from the device, it starts disabled and activates only after clear affirmative action for that feature.

  4. Plan for Re-consent. If your existing permissions were collected under vague or bundled prompts, assume they won't hold up. Decide now how you'll run re-consent for existing users, and make withdrawal of consent as easy as giving it.

  5. Don't Rely on Lead-Authority Arguments. Where ePrivacy rules apply, assume enforcement can come from any member state. Build your consent design to the strictest national reading you operate under.

  6. Ensure Remediation Reaches Everyone. Fixes that only apply to users who update the app leave a non-compliant population behind. Use server-side controls where you can, so a correction doesn't depend on user behavior.

  7. Keep Verifiable Records. If you can't demonstrate what a user was told and what they agreed to for each feature, you can't prove valid consent. Log the disclosure version, the choice, and the timestamp.

  8. Cooperate Early and Document It. The Authority cited lack of cooperation and a prior action in setting the amount. Your response posture is part of your exposure.

The core lesson is simple. A permission prompt isn't consent unless users know what they're agreeing to, can say no to that one thing, and start from a state where nothing has been switched on for them.

Promotional banner for the CUI buildout guide

You Might Also Like