The social media platform Facebook announced last year that it would turn to policies to increase privacy for data. Allegedly, the company started working on personalized ads without using user data. However, this study will only target iOS users. Because Facebook had to make changes in advertising after Apple released the App Tracking Transparency feature.
According to the information that has emerged now, Facebook will experience many difficulties in terms of data. Because he himself does not know how to manage user data. Let’s take a look at the details of the news together.
Facebook will struggle to comply with privacy laws
Facebook’s privacy engineers have no way of tracking the personal data the company collects, according to the report’s statement. Therefore, the company does not know how to use the data collected by the system. In addition, he will have difficulty in complying with privacy laws because he is not fully informed about this issue.
According to the privacy engineers’ statement, Facebook collects and combines information from various sources. Even after the user data is combined, it is not clear exactly where the information comes from. The prepared report makes it impossible to comply with the policy changes of this situation.
Facebook made the following statement on the subject:
“We do not have sufficient control and accountability over how our systems use data. Therefore, we cannot confidently make controlled policy changes or external commitments such as “We will not use data X for purpose Y”.
The Facebook privacy team has submitted a project to tag user data as created on Facebook with the Purpose Policy Framework (PPF) for tracking user data. To implement the plan, Facebook will first send many uncontrolled data retrieval points into a single choke point. PPF policy will be added to user data at the point of bottleneck. In this way, Facebook will correctly use the data for which it is responsible.
What do you, our readers, think about this issue? You can express your thoughts in the comments section or on the SDN Forum.
6517
