-
Notifications
You must be signed in to change notification settings - Fork 160
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
Expand attestations to limit known abuses #266
Comments
Here is an updated version of an attestation to help provide for fair competition among SSPs. By limiting the ability to obfuscate "good ad/bad site" placements in reports, SSPs with a policy of only monetizing legitimate sites will be less likely to be placed at a disadvantage, or pressured into a risky race to the bottom with SSPs who are willing to monetize infringing, embargoed, and other problem sites. Attestation name: ContextReportedToAdvertiser Attestation detail: If this API is used in conjunction with the placement of an advertisement, the caller will make available to the advertiser sufficient information to evaluate the appropriateness of the placement of the advertisement, including at least the full hostname of the site on which the advertisement appears. Related
|
Extend the list of attestations required to use this API to address known undesirable consequences of cross-context transfer of information.
If this API is used to place an ad on a web page, the caller attests that they will take commercially reasonable measures to require that the URL of the web page is reported to the advertiser. Limit the incentives for intermediaries to monetize pages seen as out of policy or brand-unsafe by advertisers, which often drive traffic using deceptive browser extensions, other malware, spam and other methods that present privacy risks to users.
The caller attests that data from this API will not be used in conjunction with data obtained using unintended identification techniques such as browser fingerprinting. Unintended identification techniques, as defined in Mozilla's "Anti tracking policy" are not easily controllable by the user. (see discussion at UX is misleading #265)
The text was updated successfully, but these errors were encountered: