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

Logging-in does not necessarily mean giving tracking consent #37

Open
michael-oneill opened this issue Oct 11, 2020 · 0 comments
Open

Comments

@michael-oneill
Copy link

While there are good specific reasons for clients to register when a user has logged in, it should not be seen as a proxy for a tracking consent signal.
One can login to a site and still not expect to be tracked, while on some sites wish to be tracked without having to login.
A user can register tracking consent, after being validly informed of the specific ways and purposes they would be tracked on a particular site, by clicking on a browser chrome UI element, or perhaps from a permissions API request (properly frequency limited by the browser). In Europe this is not only legally required but it becoming a well understood facility on many sites.

There still needs to be a browser mediated tracking consent signal, to be considered by browsers independently from the isLoggedIn signal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants