I propose the following data to be a new case:
| Fields | Data |
|---|---|
| Name | The service collects data from your voice when you communicate with a service verbally |
| Description | The service collects data and recordings of your voice when you communicate with a service verbally and may use them to improve their services or used for commercial purposes. |
| Classification | blocker |
| Topic | Topic Types of Information Collected (ToS;DR Phoenix) |
| Weight | 50 |
Should it be separated from Case 397: Your biometric data is collected?
There arenât many points linked to Case 397, so I think creating a whole new case for this kind of biometric collection will overwhelm the casesâ list and make it harder for reviewers to find the right case to link a quote to.
For me, biometric data is more like fingerprint and facial recognition.
My argument is mainly that big companies make voice assistants available and collect voice data from their users.
Especially for siri, bixby, alexa, google assistant, etc.
And I think itâs important to make the difference between biometric data and voice data which can sometimes be very sensitive.
What do you think about it?
Agree that voice is not biometric data, didnât we also want to move away from the phrase âthe serviceâ?
For me, whether it is âthis serviceâ or âthe serviceâ doesnât change much as I try to change the titles as much as possible by putting the name of the service instead.
The discussion was about moving away from that phrasing to make it cleaner and easier to read.
âData about your voice is collectedâ - Not is it only shorter, itâs much easier to read.
Note: The case names appear in the extension so we donât want to clutter it.
Okey,
I agree with âData about your voice is collectedâ is really much easier to read.
I am raising the subject again with regard to this case.
Do we add it?
Maybe we should wait a few days for other opinions to be expressed.
Voice prints are totally biometric data. However, I get the sense the proposal isnât asking about [re]identification, but rather about âownershipâ of the voice data? Some companies have been caught generating TTS systems using consumer data from collection occurrences they didnât notify people of, for instance.
Voice prints are totally biometric data. However, I get the sense the proposal isnât asking about [re]identification,âŠ
MmmhhhâŠ
Yes, I think that in order to keep a basis for this proposal, we could change the title to
âYour voice data can be used for many purposeâ
To reopen the subject, I found this in the Duolingo privacy policy:
âTo recognize speech your audio may be sent to a third party provider such as Google, Apple, or Amazon Web Services.â
Isnât the main issue that its the serviceâs business model? Assigning a blocker to a language learning service that collects voice data to function doesnât seem right to me.
No, but for me, the user must know that when he speaks, his voice data are processed by google, amazon or apple.
You forgot the important bit in the privacy policy though:
We may ask you to allow Duolingo to collect and analyze your speech data to help us understand the effectiveness of our lessons, and to improve the product.
This is what qualifies it as a blocker. Its all about the context
To add to this, we have case-394 which states âthat it makes sense for the serviceâ and is neutral.
We have to keep that in mind as well. Thats why I think case-400 is wrong too as Google Maps or any geolocation provider would have a worse grade just because they exist
Case 400 is supposed to be only assigned to services that donât rely on geo-location, according to its description:
Unless the service relies on Geo Location, this case is to be assigned to points that donât need your GPS coordinates to function properly.
or we can change the name by " Data from the voice are processed by Third-part" and no blocker but bad .
PS: Duolingo is similar to Quizlet and the speaking part is not at all necessary for learning. So in my opinion, it is important to warn the user that their voice is being processed by web giants known for their unethical practices.
To summarize, this would be the new case proposal:
| Fields | Data |
|---|---|
| Name | Voice data is collected and shared with third-parties |
| Description | The service collects data and recordings of your voice when you communicate with a service verbally and may use and share them with third parties, that may use this data for marketing or advertising. |
| Classification | bad |
| Topic | Topic Types of Information Collected (ToS;DR Phoenix) |
| Weight | 50 |
Iâve updated the description to match with the new title
If there are no other thoughts on this, Iâll add the case!
Edit: The case is now in Phoenix: Case 489: Voice data is collected and shared with third-parties
Yep that sounds great!