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

updated the PBM mobile privacy page #2250

Merged
merged 4 commits into from
Aug 27, 2020
Merged

updated the PBM mobile privacy page #2250

merged 4 commits into from
Aug 27, 2020

Conversation

MartianTribe
Copy link
Collaborator

No description provided.

*
* @param A valid Binary String: The '0' or '1' at position n – where n's indexing begins at 0 – indicates the consent status for purpose ID n+1; false and true respectively. eg. '1' at index 0 is consent true for purpose ID 1
*/
TargetingParams.setPurposeConsents("101010001");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The getDeviceAccessConsent is not present in the Android example

- Set the [IAB Europe](https://www.iabeurope.eu/) (IAB) consent string

This information will be persisted by Prebid Mobile and will be added to each ad call. Publishers/Consent Management Platforms (CMPs) are free to store these values in an `NSUserDefaults/SharedPreferences` interface (as defined by [Mobile In-App CMP API v1.0: Transparency & Consent Framework](https://github.com/InteractiveAdvertisingBureau/GDPR-Transparency-and-Consent-Framework/blob/master/Mobile%20In-App%20Consent%20APIs%20v1.0%20Final.md)) instead of passing them via the new APIs, and Prebid Mobile will read the values as a fallback.
This information will be persisted by Prebid Mobile and will be added to each ad call to the demand partners. Publishers/Consent Management Platforms (CMPs) are free to store these values in an `NSUserDefaults/SharedPreferences` interface (as defined by [Mobile In-App CMP API v1.0: Transparency & Consent Framework](https://github.com/InteractiveAdvertisingBureau/GDPR-Transparency-and-Consent-Framework/blob/master/Mobile%20In-App%20Consent%20APIs%20v1.0%20Final.md)) instead of passing them via the new APIs, and Prebid Mobile will read the values as a fallback.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are missing references to the TCF2.0 framework per the draft document we have under review: https://docs.google.com/document/d/1glzKEDlrRPq1JBKX33vyRjk_Unx2rfu2ZYne8piLkp8/edit#

@MartianTribe MartianTribe merged commit c8c35a5 into master Aug 27, 2020
sbrosinski added a commit to smaato/prebid.github.io that referenced this pull request Aug 31, 2020
* origin/master: (402 commits)
  Updates for CMP Functionality Best Practices (prebid#2284)
  cross-linking TCF/CMP docs (prebid#2283)
  Restored zoneId parameter in criteo bid adapter doc (prebid#2275)
  Add sspBC adapter  (prebid#2157)
  Update cmp-best-practices.md
  Update cmp-best-practices.md
  Add supported modules table for GDPR Enforcement module. (prebid#2271)
  New Adapter: Concert (prebid#2033)
  ID+ submodule (prebid#2260)
  Cmp best practices (prebid#2282)
  creative declaration
  fixing creative pages, adding GAM declaration (prebid#2281)
  adding gvl_id to metadata (prebid#2279)
  removed syntax.css (prebid#2278)
  updated the PBM mobile privacy page (prebid#2250)
  Added TCF v2.0 support to the documentation (prebid#2276)
  Add smartx.md markdown for docs (prebid#2272)
  1.Change ironsource to be lower case all over (prebid#2265)
  Update show-outstream-video-ads.md for backupOnly renderers (prebid#2259)
  adform.md docs updated (prebid#2262)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants