Skip to content
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

GDPR Consent Script #13225

Closed
ghost opened this issue Jul 30, 2018 · 6 comments
Closed

GDPR Consent Script #13225

ghost opened this issue Jul 30, 2018 · 6 comments
Labels
wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.

Comments

@ghost
Copy link

ghost commented Jul 30, 2018

Dear Ladies and Gentlemen of the Matomo Team,

Below is a feature request that is certainly beneficial for many users that are concerned with the implementation of new compliance requirements by the GDPR.

In short, the feature is intended to be an extension to the Consent Manager. Currently, there is only one interface for the inclusion of cookie permissions to Matomo, but no "copy / paste" script (as it is available with the opt-out script). Many customers have to obtain the permission of the visitor actively, according to the regulations of the GDPR, where a simple opt-out is no longer enough.

The service provider PIWIK Pro has already solved this very appealingly. Such an option would be very useful for Matomo.

Thank you!

@ghost
Copy link
Author

ghost commented Jul 30, 2018

issue 13225 gdpr consent script screenshot 01 attachment 01

Example

@fdellwing
Copy link
Contributor

Does this 'solution' load any content at all from the backing-up server? If so, you can trash the whole thing because you are not allowed to load ANY content before content is given (if you take the opt-in approach).

@ghost
Copy link
Author

ghost commented Jul 30, 2018

Unfortunately, this is not quite true.
If you insert a script from Matomo asking the user if he wants to be tracked or not (or if his user behavior can be analyzed and evaluated on the website) then that is legitimate and legally correct (but only if before the Website visit no tracking scripts are loaded. But this would't make sense at all.)

@fdellwing
Copy link
Contributor

fdellwing commented Jul 30, 2018

In the moment any request reached the Matomo server, you contacted an external server which might already be a problem. The better solution is to handle the contens yourself and afterwards load the tracking script dynamically.

@ghost
Copy link
Author

ghost commented Jul 30, 2018

But Matomo is hosted on our side, and the whole point of integrating this function is to ask for permission to track users. Tracking without permission is allowed if the data is anonymized (= no personal data can be related to a person)

@mattab
Copy link
Member

mattab commented Jun 18, 2019

Not sure I understand the issue and original user account was deleted. Closing.

@mattab mattab closed this as completed Jun 18, 2019
@mattab mattab added the wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it. label Jun 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.
Projects
None yet
Development

No branches or pull requests

2 participants