Skip to main content
The state of ai impact assessment
One Permission, Many Features: Lessons From Meta's FineData Protection & Privacy
4 min readFor Legal & Compliance Officers

One Permission, Many Features: Lessons From Meta's Fine

The Challenge

Italy's data protection regulator, the Garante, fined Meta €805 million ($886 million) for how Facebook handled a "camera roll" suggestions feature launched in 2023. This feature browsed Android users' photo galleries to recommend posts enhanced with personal photos and videos. The regulator also noted Facebook's access to related metadata.

The issue wasn't a breach or misuse by an outsider. The problem lay in the consent architecture. The Garante's stance is that accessing information on a smartphone requires free and informed consent, regardless of whether data is transmitted or harm occurs. Under this view, a compliance failure doesn't need a victim, just access without valid consent.

Design and Regulatory Constraints

Three design elements shaped the outcome:

Single App-Wide Permission: Meta asked users to grant camera roll access through one permission covering multiple features. This is often a limitation imposed by mobile operating systems, where one permission can unlock many functions. The Garante noted that such permissions typically allow full access to the photo library, often permanently, without users or regulators verifying what information is used.

Non-Specific Notice: The permission was preceded by a notice about enabling other features, without informing users they were consenting to camera roll suggestions. This failed the "informed" aspect of the consent standard.

Default-On Behavior: The feature was allegedly turned on by default, affecting about 20 million Italian Android users.

Meta contested jurisdiction, but the Garante dismissed this argument. If your privacy strategy relies on jurisdictional defenses, treat it as a litigation hedge, not a control.

Regulatory Approach

The Garante's order, which Meta plans to appeal, outlines what it considers a compliant design:

  1. Obtain consent through a request that is "separate and specific to the feature."
  2. Clearly explain the feature's purpose.
  3. Disable the option by default.

This creates a three-part consent standard: specificity, transparency, and opt-in. A technical permission prompt from the operating system doesn't satisfy this. Legal consent must be established at the feature level, in your interface, in your words.

Results and Metrics

The fine is among the largest the Garante has issued, linked to three factors:

  • Scale: About 20 million Italian Android users were impacted.
  • Duration: The violation persisted over a long period.
  • Cooperation: The regulator cited Meta's lack of cooperation during the investigation.

Scale and duration are inherent to your product, compounding the longer a flaw exists. Cooperation is the factor you can control once a regulator is involved. It's the only aspect you can change during an inquiry.

Potential Changes

Meta disagrees with the findings, so consider this analysis based on the regulator's perspective:

Decouple Feature Consent from Platform Permission: The core issue was bundling. If one OS-level grant covers many features, your in-app consent layer must separate them. Each feature accessing device content needs its own explicit, documented opt-in.

Flip the Default: Default-on is hard to defend when data resides in a private space like a phone gallery. Features accessing personal device content should default to off.

Write Notices for the Feature, Not the Platform: Notices about "other features" are insufficient. Users should understand that consenting allows the app to browse their photos and videos for suggestions.

Engage with Regulators Early: Cooperation was cited as an aggravating factor. A prepared response process, involving legal, privacy, and engineering teams, is more cost-effective than the alternative.

Takeaways for Your Team

Audit Permissions by Feature: Map each OS-level permission your apps request to every feature relying on it. If one permission supports several features with different purposes, you face the same structural exposure criticized by the Garante.

Test Consent Against Three Questions: Is it separate for this feature? Is it specific about what is accessed and why? Is the default off? A "no" to any of these is a finding.

Don't Rely on "No Harm Done": The regulator's reasoning makes access without valid consent the violation. Impact assessments focusing only on data leaving the device or causing harm will miss the exposure. Frameworks like the NIST Privacy Framework and ISO/IEC 27701 can anchor feature-level privacy reviews, and the General Data Protection Regulation should guide any EU-facing feature.

Treat Defaults as a Control Decision: Include default states on the review checklist for every release touching user content. Product teams optimize for adoption, and defaults are where adoption pressure and privacy duty collide. Someone with authority needs to own that tradeoff in writing.

Prepare for the Balance Question: Legal and compliance teams often ask how to preserve user experience under stricter consent rules. The case offers a practical answer: a specific, well-explained opt-in prompt costs some friction at the point of choice but provides a defensible record. The alternative is a design that converts more users until a regulator examines it.

Remember the Clock: The 60-day compliance window shows how quickly a regulator can demand product changes. If a redesign would take longer, you have a gap to close before anyone asks.

The lesson isn't that camera roll suggestions are off-limits. It's that consent must be built at the level where data use happens, and the default must respect the person holding the phone.

Application Security Isn’t Optional Anymore.

You Might Also Like