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

Documentation of GDPR-compliant adapters and behavior? #2519

Closed
kmjennison opened this issue May 10, 2018 · 2 comments
Closed

Documentation of GDPR-compliant adapters and behavior? #2519

kmjennison opened this issue May 10, 2018 · 2 comments
Labels

Comments

@kmjennison
Copy link
Contributor

Is there documentation on how each adapter will handle GDPR? (Related: the GDPR consentManagement module, #2213.)

In particular, it would be nice to know:

  1. Which adapters are supporting the consentManagement module?
    • If they're not already, will they be updated by May 25?
    • I believe this info is only currently available by looking at release notes or module source code
  2. What are the bidders' behaviors if gdprConsent.gdprApplies is not defined (and allowAuctionWithoutConsent is true) or the consentManagement module isn't being used? Possible bidder behaviors are:
    • never return bids (globally)
    • return non-personalized ad bids (globally)
    • return personalized ad bids (globally) -- this is probably most concerning to publishers seeking compliance
    • bidder detects EU traffic, and if EU, never return bids
    • bidder detects EU traffic, and if EU, return non-personalized ad bids

I'd understand if you consider this out of scope of core Prebid (particularly no. 2). However, I'd guess many publishers are uncertain how partners are handling consent, and Prebid seems like a good place to centralize the knowledge.

@hdjvieira
Copy link
Contributor

On the Prebid.js consentManagement docs page, there is a list of GDPR compliant adapters at the end.

@stale
Copy link

stale bot commented Jun 1, 2018

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 Jun 1, 2018
@stale stale bot closed this as completed Jun 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants