6 ms·

Your Code says it uses the browser's speech recognition API. ``` // Start speech recognition using the browser's speech recognition API function CN_StartSpeech

Your Code says it uses the browser's speech recognition API. ``` // Start speech recognition using the browser's speech recognition API function CN_StartSpeechRecognition() { ``` As far as I know, speech recognition in Chrome, unlike on Android phones, is being done online. Means audio is being sent to Google servers. How does this comply with GDPR?

renewiltord 4y ago
Why don't you tell us how it violates GDPR? And then you can make an issue on Github to tell the guy to stop offering his thing in the EU.
jcims 4y ago
Does it claim to be compliant anywhere? I would assume it isn’t.
- itcrowd 4y ago
  Gdpr compliance is not optional for services offered in the EU
  - deleted 4y ago
    [deleted]
  - shagie 4y ago
    Does every client side javascript project someone builds on GitHub for fun need to be verified if it is GDPR compliant? And what if the source someone shares is using APIs that aren't GDPR complaint? That you can download, compile it, run it on your machine and then say that it was offered to you and so must be GDPR compliant. I'm not in the EU and not familiar with the particulars of GDPR but that feels like it is stretching for a reason to complain.
deleted 4y ago
[deleted]
wizzwizz4 4y ago
> As far as I know, speech recognition in Chrome, unlike on Android phones, is being done online. I'm no expert, but I would imagine this is Google's problem. The website is calling an API that no reasonable person would expect to leak data to Google – in fact, Google has an implementation that doesn't – yet personal data is being leaked, without the user's consent. At no point does the operator of this website act as controller for the voice data.
jlaporte 4y ago
There are a lot of admirable things about the EU, and this is by no means intended as EU bashing. But could there be a more on the nose example of why the EU lags in tech innovation and entrepreneurship? An solo maker builds a cool little tool as a personal project, open sources it on github, and is immediately attacked for the effort by cosplay compliance regulators. It defies parody. The commenters also have a cartoon understanding of the GDPR - the author of the Chrome extension is neither a data controller nor a data processor. I'd ask the commenters that jump on a project like this to introspect a bit and try to understand why their first impulse on seeing someone's effort like this is to try to take it down.
- iamjackg 4y ago
  You raise a very valid point, but one could make an argument that it's _okay_ for innovation and entrepreneurship to slow down, if it's done to protect people's rights and ensure that companies do things "properly." It seems to be an eternal cyclical process: people come up with something that either sidesteps or has no regulation whatsoever, you get massive growth and innovation, which turns to exploitation, which leads to regulation. We've seen it in all fields, from tech to pharmaceuticals to big box retail. Is it an acceptable compromise in society to "let things happen" for a while before regulating? Or should we all slow down and think about the consequences before pushing forward?
- de6u99er 4y ago
  The author should at least make users aware that data is being sent to Google servers. I don't see GDPR as preventing innovation. Quite on the contrary, it has enabled European companies, which host their data by default in the EU, to create competitive products. That being said, I think in Europe there's, compared to the US, more old money controlled by people who don't like to share or lose their wealth.
iamjackg 4y ago
Hm, this is actually a very interesting case. If the extension is (I'm assuming) literally just leveraging the API and not storing anything at all, would it be sufficient to let people know it's doing so in order to be compliant with GDPR? Does this even count as something that would be covered by GDPR? Is it because the data collection is tangential to the "service" being offered? Chrome's Privacy page [1] doesn't say anything about the API. Other people have also been wondering about the privacy implications of using the Speech API. What an interesting rabbit hole! 1: https://www.google.com/intl/en/chrome/privacy/ https://www.google.com/intl/en/chrome/privacy/

renewiltord 4y ago

Why don't you tell us how it violates GDPR? And then you can make an issue on Github to tell the guy to stop offering his thing in the EU.

jcims 4y ago

Does it claim to be compliant anywhere? I would assume it isn’t.

itcrowd 4y ago
Gdpr compliance is not optional for services offered in the EU
- deleted 4y ago
  [deleted]
- shagie 4y ago
  Does every client side javascript project someone builds on GitHub for fun need to be verified if it is GDPR compliant? And what if the source someone shares is using APIs that aren't GDPR complaint? That you can download, compile it, run it on your machine and then say that it was offered to you and so must be GDPR compliant. I'm not in the EU and not familiar with the particulars of GDPR but that feels like it is stretching for a reason to complain.

deleted 4y ago

[deleted]

wizzwizz4 4y ago

> As far as I know, speech recognition in Chrome, unlike on Android phones, is being done online. I'm no expert, but I would imagine this is Google's problem. The website is calling an API that no reasonable person would expect to leak data to Google – in fact, Google has an implementation that doesn't – yet personal data is being leaked, without the user's consent. At no point does the operator of this website act as controller for the voice data.

jlaporte 4y ago

There are a lot of admirable things about the EU, and this is by no means intended as EU bashing. But could there be a more on the nose example of why the EU lags in tech innovation and entrepreneurship? An solo maker builds a cool little tool as a personal project, open sources it on github, and is immediately attacked for the effort by cosplay compliance regulators. It defies parody. The commenters also have a cartoon understanding of the GDPR - the author of the Chrome extension is neither a data controller nor a data processor. I'd ask the commenters that jump on a project like this to introspect a bit and try to understand why their first impulse on seeing someone's effort like this is to try to take it down.

iamjackg 4y ago
You raise a very valid point, but one could make an argument that it's _okay_ for innovation and entrepreneurship to slow down, if it's done to protect people's rights and ensure that companies do things "properly." It seems to be an eternal cyclical process: people come up with something that either sidesteps or has no regulation whatsoever, you get massive growth and innovation, which turns to exploitation, which leads to regulation. We've seen it in all fields, from tech to pharmaceuticals to big box retail. Is it an acceptable compromise in society to "let things happen" for a while before regulating? Or should we all slow down and think about the consequences before pushing forward?
de6u99er 4y ago
The author should at least make users aware that data is being sent to Google servers. I don't see GDPR as preventing innovation. Quite on the contrary, it has enabled European companies, which host their data by default in the EU, to create competitive products. That being said, I think in Europe there's, compared to the US, more old money controlled by people who don't like to share or lose their wealth.

iamjackg 4y ago

Hm, this is actually a very interesting case. If the extension is (I'm assuming) literally just leveraging the API and not storing anything at all, would it be sufficient to let people know it's doing so in order to be compliant with GDPR? Does this even count as something that would be covered by GDPR? Is it because the data collection is tangential to the "service" being offered? Chrome's Privacy page [1] doesn't say anything about the API. Other people have also been wondering about the privacy implications of using the Speech API. What an interesting rabbit hole! 1: https://www.google.com/intl/en/chrome/privacy/ https://www.google.com/intl/en/chrome/privacy/