Question of the Day
One question per day to look beyond the headlines.
How did a default-on Facebook Android feature turn “device photos” into a GDPR-scale consent violation?
Take-away Consent fails structurally when a default-on data flow is justified via bundled OS permissions: purpose-specific consent is separate from access grants, so disclosure must be distinct.
The issue with Facebook's Android feature arose from its gallery-suggestion capability, which accessed users' photo galleries without obtaining separate, clear, and informed consent from users. This feature was enabled by default, and the consent for access was ambiguously integrated into a broader permission request that did not clearly disclose the specific purpose of using gallery data [1], [2], [3]. As a result, Facebook was in violation of the ePrivacy Directive as implemented in Italian law, which requires specific and informed consent for accessing such personal data [2], [3]. This failure to properly inform users and obtain distinct consent for the use of device photos led to a significant fine under regulations akin to the General Data Protection Regulation (GDPR) [3], [4].
- Italy slams $887m fine on Meta over access to Android users' photo galleries - Tribune Online tribuneonlineng.com (opens in new tab)
- Meta fined $887 million for accessing millions of users' private photos without conse ynetnews.com (opens in new tab)
- Meta Fined €805 Million in Italy Over Facebook’s Default Photo Gallery Access securityaffairs.com (opens in new tab)
- CPI | Meta Faces $887 Million Italian Privacy Fine Over Access to Android Users’ Photos pymnts.com (opens in new tab)