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

[Feat]: Handling legitimate interests #2

Open
DorijanH opened this issue Jun 5, 2024 · 0 comments
Open

[Feat]: Handling legitimate interests #2

DorijanH opened this issue Jun 5, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@DorijanH
Copy link
Member

DorijanH commented Jun 5, 2024

Description

Few of the CMP validator (chrome extension) checks talk about giving the user an option to object to purposes that vendors can have legitimate interests for.

Those are the purposes that the vendors have a legitimate right to process and are enabled by default.
This in itself is confusing because in the case of the Stack Overflow's CMP all legitimate interests are permitted even if the user did not express consent for any of the vendors or has explicitly denied all of them 😕

When working on the TCF compliance PR, I was mostly using the Spotify's CMP as a reference and there are no options for the user to object to such legitimate interests because they treat it like the user objected to all of those by default.

This was a simpler way of doing things so that's how it's currently implemented.

Proposed solution

No response

Additional details

No response

@DorijanH DorijanH added the enhancement New feature or request label Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant