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

Update GDPR support for Purpose 4 #10161

Closed
bretg opened this issue Jun 28, 2023 · 0 comments · Fixed by #10199
Closed

Update GDPR support for Purpose 4 #10161

bretg opened this issue Jun 28, 2023 · 0 comments · Fixed by #10199
Assignees

Comments

@bretg
Copy link
Collaborator

bretg commented Jun 28, 2023

Type of issue

Enhancement

Description

In reviewing privacy policies in light of the recent MSPA/USNat changes, it was recognizes that we could tighten Prebid GDPR support by allowing publishers to anonymize first party data.

The Prebid GDPR doc has been updated:

  1. Define Purpose 4 behavior. It's the same algorithm for determining consent as for P2 and P7, but the impact of not having consent is new: remove UFPD as defined in the doc.
  2. Flowchart updated

It should be discussed in committee how the addition of this purpose is phased-in. If it's considered a "breaking" change, it could be added as not-enforced-by-default and switched in future major release.

Here's the proposed config for P4:

 pbjs.setConfig({
   consentManagement: {
     gdpr: {
       cmpApi: 'iab',   // activates the enforcement module
       defaultGdprScope: true,
       rules: [{ 
         ...
       },{
         purpose: "personalizedAds",
         enforcePurpose: true,
         enforceVendor: true
       }]
     }
   }
 });
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging a pull request may close this issue.

2 participants