You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Matomo tracker we already have a method that can be called that a user has given consent to be tracked. We also already attach a tracking URL parameter consent=1 when consent was given.
I think by default, Matomo should record a raw (unhashed) User ID only if a user consented to it.
This is to protect user privacy. And User ID certainly can be considered personal data and therefore we should require by default our users to ask for consent in order to use this feature.
The text was updated successfully, but these errors were encountered:
I would just keep in mind that for most User ID use cases it doesn't really matter if one stores a hashed or unhashed ID as it can be reversed trivially (e.g. hash e-mail of all registered users)
@voarsh2 Why do you think this shouldn't be the default (not suggesting removing this option)?
I'm genuinely interesting in hearing other peoples opinion in the new ideas for privacy features in Matomo.
In Matomo tracker we already have a method that can be called that a user has given consent to be tracked. We also already attach a tracking URL parameter
consent=1
when consent was given.I think by default, Matomo should record a raw (unhashed) User ID only if a user consented to it.
This is to protect user privacy. And User ID certainly can be considered personal data and therefore we should require by default our users to ask for consent in order to use this feature.
The text was updated successfully, but these errors were encountered: