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

Prebid Server COPPA Support #929

Closed
bretg opened this issue Jun 7, 2019 · 8 comments
Closed

Prebid Server COPPA Support #929

bretg opened this issue Jun 7, 2019 · 8 comments
Assignees
Labels
feature request Intent to implement An issue describing a plan for a major feature. These are intended for community feedback

Comments

@bretg
Copy link
Contributor

bretg commented Jun 7, 2019

Copy of prebid/Prebid.js#3852 - Prebid Server would implement #5 below

Type of Issue

Feature

Description

Several bidders have ways for prebid users to pass the COPPA flag, but Prebid.js hasn't specified a standard way to specify it such that all bid adapters can access it.

Proposal

This doesn't fit into the First Party Data context framework because the COPPA flag is always public and should be known to all adapters, while other first party data might be limited to a certain set of bidders.

So the proposal is

  1. Declare a configuration convention for the publisher to signal PBJS about COPPA content:
pbjs.setConfig({coppa: true});
  1. PBJS Core gets updated to set the COPPA flag on the bid request object

  2. Each adapter supporting COPPA would then be updated to check for the bid request object

  3. The Prebid Server Bid Adapter will be updated to pass this value to PBS as regs.coppa=1 when true.

  4. Prebid Server will pass regs.coppa (0 or 1) to adapters and will always (not configurable) cause the PBS core to enforce COPPA rounding of IP address and removal of ID as suggested in the OpenRTB standard:

  • device.ifa, device.macsha1, device.macmd5, device.dpidsha1, device.dpidmd5, device.didsha1, device.didmd5
  • Truncate ip field - remove lowest 8 bits.
  • Truncate ipv6 field - remove lowest 32 bits.
  • Remove geo.lat, geo.lon. geo.metro, geo.city, and geo.zip
  • Remove user.id, user.buyeruid, user.yob, and user.gender
  1. Update prebid.org with a page that dynamically lists the COPPA-supporting adapters based on the .md file similar to what we do for GDPR.

  2. Define how COPPA flag gets sent in the SDK and then added to the OpenRTB as regs.coppa.

@bretg bretg added feature request Intent to implement An issue describing a plan for a major feature. These are intended for community feedback labels Jun 7, 2019
@mansinahar
Copy link
Contributor

@bretg in the openrtb spec I see the recommendation to remove Device.DIDMD5 and Device.DIDSHA1 but I see a couple more fields to be removed from the Device object recommended here. Curious to know why we wanna remove those additional fields also

@bretg
Copy link
Contributor Author

bretg commented Jul 22, 2019

Hi @mansinahar - yeah, after discussing with Prebid.org legal counsel, we decided to remove all IDs. The OpenRTB reference was just a recommendation.

@mansinahar
Copy link
Contributor

I see! Thank you @bretg

@bretg
Copy link
Contributor Author

bretg commented Jul 28, 2019

FYI - this is done for PBS-Java

@mansinahar
Copy link
Contributor

PRs created for this: #973 and prebid/prebid.github.io#1413

@stale
Copy link

stale bot commented Aug 8, 2019

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 stale and removed stale labels Aug 8, 2019
@mansinahar
Copy link
Contributor

I believe this can be closed now. Any objections @bretg ?

@mansinahar mansinahar self-assigned this Aug 14, 2019
@bretg
Copy link
Contributor Author

bretg commented Aug 14, 2019

Implemented on both PBS-Go and PBS-Java. Closing.

@bretg bretg closed this as completed Aug 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Intent to implement An issue describing a plan for a major feature. These are intended for community feedback
Projects
None yet
Development

No branches or pull requests

2 participants