-
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
Multiple modules: USP data deletion event handling #9116
Conversation
93047ed
to
b127fc4
Compare
b127fc4
to
90db169
Compare
Jeff and Soujanya your committee's feedback would be appreciated |
Can we add the method to the Sharedid sub adapter and add an integration test to see if it works? THat way we get 1) sharedid into compliance, and 2) proof it works, aside from the CMP to adapter piece. |
@jdwieland8282, what should the method do? stored IDs are already removed for all adapters, and there are test cases for it. The method is to allow adapters to "propagate" the request to their endpoint / do anything else that needs to be done, I'm not sure what that would be for sharedId. |
ok, I misunderstood, I though each sub adapter would need to have that method and call it when the the delete me signal occurred. It sounds like you are saying is that the modified USP module will blow those ids away. Since sharedid has no endpoint to propagate the signal to nothing else needs to happen. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This is a problem
When users ask to be forgotten then expect to only need to do that once, and that this preference will persist. In addition to removing the users uids, we should also set a |
@jdwieland8282, shouldn't the consent string change after opt-out? From https://github.com/InteractiveAdvertisingBureau/USPrivacy/blob/master/CCPA/US%20Privacy%20String.md , my understanding is that the "Opt-out sale" flag should change to |
I'll add this to the Identity PMC meeting today. Will follow up this afternoon. |
@dgirardi this looks ready to merge pending a docs pull |
Unless anyone objects by 10/28/22, the USP data deletion event handling will do the following.
|
@jdwieland8282 (or @AramZS), what should be the guidance given to adapters for what do to in
|
delete all locally stored data (or just PII), and propagate the signal downstream We don't have such a reference we only have the reg itself. This site is a good place to start. We don't want to give legal advice, bid adapters should form their own opinion about what to do when they receive a delete me signal. |
Docs pr: prebid/prebid.github.io#4114 |
* Multiple modules: USP data deletion event handling * Add `onDataDeletionRequest` to RTD submodule spec Co-authored-by: Patrick McCann <patmmccann@gmail.com>
* Multiple modules: USP data deletion event handling * Add `onDataDeletionRequest` to RTD submodule spec Co-authored-by: Patrick McCann <patmmccann@gmail.com>
Type of change
Description of change
This defines an interface for handling USP opt out events:
onDataDeletionRequest(config, idValue)
spec.onDataDeletionRequest(bidderRequests)
onDataDeletionRequest()
Note that:
Other information
Resolves #9081
Documentation TBD