-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Comments
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. |
After discussions last week, here's the proposed path-forward for Prebid and TCF: Prebid.js
Prebid Server
Prebid SDK
|
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. |
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. |
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.
The text was updated successfully, but these errors were encountered: