4 ms·
this isn't true. Because it's not personally identifiable information. If I take a photo of a crowd of people and upload it to a cloud service, that does not c
by marcus_holmes 9y ago
this isn't true. Because it's not personally identifiable information.
If I take a photo of a crowd of people and upload it to a cloud service, that does not create an obligation on either me or the cloud service to identify all those people and give them to opportunity to opt out (or in).
I own the copyright of photos I take. I don't need permission from people to take their photo in a public space. They have no right to ask me to delete the photo or remove their face from any photo that includes them. Even if I store it on a computer.
If I provide a service that identifies all the people in a photo, then I am storing personally-identifiable information and I need to give the person I have identified the opportunity to remove their data from my system.
That doesn't mean removing their face from the photo, but does mean removing the data that allowed me to identify them in the photo. There's a difference.
- s17n 9y agoAll I know is that my company stores image data and we don' do any face recognition but the lawyers say that to comply we need to start removing faces.
- marcus_holmes 9y agothat's interesting. Do they say why?
- s17n 9y agoBecause faces are personal information under the gdpr.
- AstralStorm 9y agoWhy? You do not know which user uploaded which picture? Accidental uploads of private data by the user are perfectly fine in terms of GDPR but you must allow for these to be removed on request. If you automatically scrub them it is good, but you do not really have to do that. Telling the user how any pictures will be used and how to get rid of them is enough.
- s17n 9y agoWhich user uploaded which picture is irrelevant - whoever's face is in the picture has rights under gdpr.
- marcus_holmes 9y agoI'm not a lawyer, but surely their face must be identified to be covered? A random face in a crowd is not identification of a person... That's like screening all your binary executables for accidental inclusion of someone's name in ASCII amongst the bytes.