Skip to content

[Feat]: Handling legitimate interests #2

@DorijanH

Description

@DorijanH

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions