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

Enforcing TCF2.0 #4867

Closed
bretg opened this issue Feb 15, 2020 · 4 comments
Closed

Enforcing TCF2.0 #4867

bretg opened this issue Feb 15, 2020 · 4 comments

Comments

@bretg
Copy link
Collaborator

bretg commented Feb 15, 2020

Description

Related to #4801 and #4747

Prebid.org is neither data controller nor data processor, but we supply software to both types of entities. Therefore, our software should provide all the controls necessary for both types of entities to run their businesses.

Would like to try a new way of reviewing large documents like this. Here's a link to the Google Doc that anyone can make comments on:
https://docs.google.com/document/d/1fBRaodKifv1pYsWY3ia-9K96VHUjd8kKvxZlOsozm8E/edit#

Basically, this is a pretty significant change to Prebid.js -- it offers publishers the option to enforce GDPR in a robustly configurable way.

@pm-harshad-mane
Copy link
Contributor

I think considering the deadline, we should support TCF2 as we supported TCF1 in the first phase and later in the next phase we can discuss and implement #4747 if needed.

@bretg
Copy link
Collaborator Author

bretg commented Feb 24, 2020

After discussions last week, here's the proposed path-forward for Prebid and TCF:

Prebid.js

  1. We will build a deviceAccess flag (Proposal for Prebid.js Enforcement of Device Access #4747 ) that can be used by publishers as an interim way to initially enforce Purpose 1.
  2. Read the TCF strings from the new API (TCF 2.0 Tech Spec #4801)
  3. Implement 'basic' Purpose 1 enforcement as described in the doc.
  4. Implement the remainder of the purposes as described in the doc.

Prebid Server

  1. Both PBS-Go and PBS-Java will build towards the 'full' enforcement as described in the doc.
  2. Either or both teams may decide to phase in the functionality, e.g. at first only supporting Purpose 1 and/or 'basic' enforcement.

Prebid SDK

  1. The SDK will accept a new parameter as described in the doc allowing the app developer to instruct Prebid whether it's ok to read the IDFA. Other than that, it's a passthrough.

@stale
Copy link

stale bot commented Mar 9, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Mar 9, 2020
@bretg bretg added in progress and removed stale labels Mar 14, 2020
@stale
Copy link

stale bot commented Mar 28, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Mar 28, 2020
@stale stale bot closed this as completed Apr 4, 2020
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

2 participants