Summary
Most privacy regulations require that you only keep data as long as it’s needed. Keeping data that you cannot use or are not using may be costing you money but certainly leaves you open to unnecessary risk. The privacy regulations also usually specify that the subject has the right to have their data removed on request.
Therefore, when designing software, it makes sense to consider building in a mechanism for removing data when no longer required or at the request of the subject. Anonymization is another option, but it must be done correctly so that the data cannot be linked back to the subject, even when correlating multiple datasets.
You’ve now covered the threat types described on the cards from the Retention/Removal suit of the Elevation of Privacy extension card deck. These threats deal with the storage limitation principle and a subject’s right to be forgotten. Unless it is in the public interest, for scientific research, freedom of expression...
