New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Review ePrivacy Regulation draft and how it would affect Matomo Analytics #15425
Comments
See example justification from etracker |
Quick update:
from GDPR Today newsletter https://noyb.eu |
I had posted a question in the Matomo forum. @mattab asked me to publish it here as well (sorry for delay). Let's go: I work as an external data protection officer. Consulting my clients I struggle with Matomo and cookie consent under art. 5 para. 3 ePrivacy DIRECTIVE (of 2009 aka Cookie Directive, https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02009L0136-20091219). Note: This is not the same as the future ePrivacy REGULATION (which will replace the directive one day). I understand (and agree) that under GDPR web analytics as provided by Matomo can be used under legitimate interest and no consent is required for such data processing.But legitimate interest in GDPR is not the same as "strictly necessary" in ePrivacy Directive. What does Matomo know about this issue? I have found a statement by Matomo of 2014 which considers Matomo analytics as strictly necessary - but the statement does not provide any arguments for this finding: https://matomo.org/blog/2014/10/cnil-recommends-piwik-analytics-tool-no-cookie-consent/ I have found talks (in German) touching the issue in the forum but they do not exactly address the core question: https://forum.matomo.org/t/opt-in-implementierung/34402/3 A posting in the forum refers to a statement by eTracker which looks at the issue like I tend to do (https://www.etracker.com/blog/cookie-urteil-des-eugh-auswirkungen-auf-den-einsatz-von-etracker/): No processing consent under GDPR but still cookie consent under ePrivacy Directive. I would be very grateful if you could provide additional arguments on the issue. I would love to tell my clients consent is NOT required BOTH under GDPR and ePrivacy Directive. Thanks a lot! |
In the draft of eprivacy available here: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CONSIL:ST_6087_2021_INIT Article 8 states as below: which reads:
Below they cover a slightly different case: I don't actually understand the difference between Article 8) 1. and Article 8) 2. -> but maybe this would mean that Eprivacy does not restrict web analytics use case and use of 1st party cookies or fingerprint? To be continued |
Article 8 para 1 addresses access to data which is on the device. Article 8 para 2 addresses data which is sent ("emitted") by the device. You could say this refers to signals sent out to detect a WiFi or Bluetooth sender. Article 8 para 1 lit. d is actually the law that addresses analytics as provided by Matomo. If this draft turns into law this would be extremely helpful to promote Matomo. Google Analytics user might call for the same exemption. But there might be arguments to which extent Google Analytics serves the "sole purpose of audience measuring". As soon as an analytics account is connected to additional services like advertising the purpose is bigger than audience measuring. |
Goal of this issue is to review the ePrivacy Regulation draft and see how it affects Matomo tracking, fingerprinting, and any other aspects of our privacy features and how to be compliant with these privacy laws. https://en.wikipedia.org/wiki/EPrivacy_Regulation_(European_Union)
As far as I can see, here is the current latest version of the eprivacy regulation draft: https://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1579563538672&uri=CONSIL:ST_13808_2019_INIT
It seems still to be WIP, in November 2019: https://iapp.org/news/a/eu-member-states-reject-eprivacy-regulation-draft/
-> What is the status of ePrivacy and if the draft text goes ahead, how would it impact Matomo and Matomo users?
The text was updated successfully, but these errors were encountered: