
Italy’s Data Protection Authority has fined Meta Platforms Ireland Limited €805 million (approximately $887 million) over Facebook’s access to photos, videos and associated metadata stored on Android users’ smartphones without obtaining specific and informed consent.
The decision, announced on November 14, 2026, concerns a Facebook feature that many users might have overlooked while browsing the platform.
But the implications go much further than a single application feature.
What actually happened?
The investigation focused on a Facebook feature introduced in 2023 called “Get suggestions from gallery when browsing Facebook.”
The feature was designed to suggest photographs and videos from a user’s mobile gallery that could potentially be shared as Facebook posts.
The problem was not the feature itself. It was how Facebook obtained permission to access the gallery.
According to the Italian regulator, Facebook relied on a single, broad Android permission covering multiple application functionalities. The notification presented to users was generic and did not adequately explain that granting permission could also enable gallery suggestions.
More importantly, the feature was enabled by default.
Once the permission was granted, the application could potentially access the entire photo archive on the device, including associated metadata.
Users were not given a sufficiently clear explanation of this access or a separate consent mechanism for the feature.
Why did Italy impose such a massive fine?
The Italian Data Protection Authority found that Meta violated Article 122 of Italy’s Privacy Code, which implements the European ePrivacy Directive.
The provision protects information stored on users’ devices and requires free and informed consent before accessing it.
The regulator considered several factors when determining the penalty:
- Approximately 20 million Android users in Italy could have been affected.
- The violation had continued for an extended period.
- Meta had faced an earlier regulatory proceeding in 2019.
- Its cooperation during the investigation was considered limited.
The regulator also acknowledged changes introduced by Meta following the complaint, but considered them insufficient and delayed.
The €805 million penalty represents approximately 0.47% of Meta’s global turnover.
What must Meta change?
The regulator has given Meta specific compliance requirements.
Within 60 days, Meta must introduce a separate and specific consent request for gallery access, clearly explain the purpose of the feature and provide users with information on how to disable it.
The feature must also remain disabled by default, including for users who had previously granted general application permissions.
Meta must report the initial measures within 30 days and communicate the implemented changes within 90 days.
Meta has disputed the decision and indicated that it intends to appeal.
The cybersecurity lesson: Permissions are not consent
This incident raises a question that every application developer and enterprise security team should consider.
When an application requests access to a device’s resources, does the user genuinely understand what they are authorising?
There is a fundamental difference between obtaining an operating system permission and obtaining informed consent for a specific purpose.
An application may legitimately require access to photographs, contacts, location or other device resources. However, that does not automatically justify using the same permission for multiple functionalities without explaining the purpose to the user.
This is where privacy engineering becomes important.
Application developers must follow the principles of data minimisation, purpose limitation and privacy by design. Permissions should be restricted to what the functionality actually requires, and users should have meaningful control over how their information is accessed.
For enterprises, this is equally relevant when evaluating third-party mobile applications, SaaS platforms and technology providers.
A security assessment that checks only encryption, authentication and vulnerability exposure is incomplete if it ignores how applications collect, access and process personal information.
The bigger picture
We often discuss cybersecurity through the lens of ransomware, zero-days, data breaches and infrastructure compromise.
But privacy violations do not always begin with an attacker.
Sometimes, the risk originates from the way a legitimate application is designed, how permissions are requested and how user information is handled.
Meta’s case is a reminder that regulatory compliance cannot be treated as a checkbox exercise.
A permission granted by a user should never become a blanket authorisation for everything an application wants to do.
The bottom line: Access is a technical capability. Consent is a legal and ethical responsibility. Confusing the two can cost hundreds of millions.



