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: When consent has been given by a user, set &consent=1 in the Tracking API URL #12834

Closed
mattab opened this issue May 7, 2018 · 5 comments
Assignees
Labels
c: Privacy For issues that impact or improve the privacy. Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
Milestone

Comments

@mattab
Copy link
Member

mattab commented May 7, 2018

Current behavior

When a user has given their consent, and if the user has already opted-out (via our opt-out iframe), then the requests that were consented are currently not tracked (because of opt-out).

EDIT: We will keep this behavior but we want to make it clear which requests were consented. Then someone could write a plugin or we could add a setting, to change and ignore the opt-out when consent is given (we'll keep it privacy by default in core).

Maybe a solution for this is to

  1. add a &consent=1 to all Tracking API requests that were consented (for the apache logs). Should be done in JS tracker.
  2. Then when checking if user is opted-out, also check that &consent=1 was not set.

(refs #12600 #12767 #12599)

@mattab mattab added the c: Privacy For issues that impact or improve the privacy. label May 7, 2018
@mattab mattab added this to the 3.6.0 milestone May 7, 2018
@tsteur
Copy link
Member

tsteur commented May 7, 2018

This makes only sense though when Matomo users are aware to not embed the opt out iframe when using the consent feature. If the Matomo user / website owner is not aware that they are mutually exclusive, then an opted out user would not expect to be tracked.

The safe solution that respects the privacy of users more be to never track when the user has opted out. (This is the current implementation).

@sgiehl
Copy link
Member

sgiehl commented Jun 25, 2018

So should that be changed or not? Or should we make that configurable maybe?

@mattab
Copy link
Member Author

mattab commented Jun 25, 2018

I think we at least need to know when a request was consented (eg. add &consent=1), this would be useful to prove that the request had indeed consent enabled.

Regarding whether to track users who have given consent + User opted-out earlier. I'd be fine keeping current behavior as this should be a rare case and therefore not very important either way.

@mattab
Copy link
Member Author

mattab commented Jun 25, 2018

Or should we make that configurable maybe?

Possibly, can you think of a practical way to make it customisable?

@mattab mattab changed the title GDPR: When consent has been given by a user, then we should track the requests, even if this user has previously opted-out GDPR: When consent has been given by a user, set &consent=1 in the Tracking API URL Jun 28, 2018
@mattab
Copy link
Member Author

mattab commented Jun 28, 2018

edited the title and description:

We will keep this behavior but we want to make it clear which requests were consented. Then someone could write a plugin or we could add a setting, to change and ignore the opt-out when consent is given (we'll keep it privacy by default in core).

@diosmosis diosmosis self-assigned this Jul 31, 2018
@mattab mattab added the Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc. label Aug 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: Privacy For issues that impact or improve the privacy. Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
Projects
None yet
Development

No branches or pull requests

4 participants