3 ms·
Note that while the Google recording data was arguably "anonymized", the reviewers of the leaked recordings were able to in many cases find enough personal info
by ocdtrekkie 7y ago
Note that while the Google recording data was arguably "anonymized", the reviewers of the leaked recordings were able to in many cases find enough personal information to contact the people recorded. Which means they were not, in fact, anonymized.
"We let ordinary Flemish people hear some of their own recordings. ‘This is undeniably my own voice’, says one man, clearly surprised."
"A couple from Waasmunster immediately recognise the voice of their son and their grandchild."
https://www.vrt.be/vrtnws/en/2019/07/10/google-employees-are-eavesdropping-even-in-flemish-living-rooms/ https://www.vrt.be/vrtnws/en/2019/07/10/google-employees-are...
- luckylion 7y agoIt's largely impossible to anonymize data you don't understand, isn't it? They have somebody transcribe the recording because they don't know what it said, so they can't know whether PII is in there. I suppose they might try to split it into multiple parts and have different people work on each part, but that may lead to problems, as you need the full sentence as context in some cases.
- dash2 7y agoThis. There's a nice paradox. Until the AI is good enough to understand the voice data, it can't know that it isn't privacy-violating -- up to and including extremes like somebody telling their most intimate secrets. Exposing this data to any other human, whether a subcontractor or internal employee, is a potential privacy violation, full stop.
- laumars 7y agoI would rather the voice processing happened locally on your device. We must be getting to the stage where that's becoming viable? If not entirely in software then via a custom chip. Even if that transcript then still needs to be sent to the cloud for processing (eg for translating human sentences into logical actions might still be out of the grasp of home devices), developers can at least then send the data tokenised (which wouldn't be possible if it was a compressed audio stream) and then get a server response referencing those tokenised place holders. A simplistic example of my point might be Message: I need to book a doctors appointment for erectile dysfunction. Sent: I need to book a $ARG[0] appointment for $ARG[1]. Received: { "action": "ring"; "subject": "$ARG[0]"; "message": "appointment for $ARG[1]" } I appreciate something like that wouldn't be infallible but it would still go a long way to redacting sensitive or identifiable information and thus a huge step forward for privacy.
- pjc50 7y agoAnother factor here: there aren't so many Flemish speakers, so the probability of a recording being reviewed by someone who can identify the speaker is much higher.
- Jabbles 7y agoIn this case the user had read their address out, the reporters went there and spoke to them.