You ll need certainly to recognize whether each data type is linked towards the user s identity (via their account, device, or any other details) by you and/or your partners that are third-party. Data accumulated from an application is actually for this user s identification, unless particular privacy defenses are positioned in position before collection to de-identify or anonymize it, such as for instance:
- Stripping information of any direct identifiers, such as user ID or title, before collection.
- Manipulating data to split the linkage and steer clear of re-linkage to real-world identities.
Furthermore, to allow information to not ever be associated with a particular user s identification, you have to avoid particular tasks after collection:
- You mustn’t try to link the info back into the user s identification.
- You must certainly not connect the information to many other datasets that help it to be connected to a specific user s identity.