US
UK
IN[kc_row use_container=”yes” force=”no” column_align=”middle” video_mute=”no” _id=”394113″][kc_column width=”12/12″ video_mute=”no” _id=”862332″][kc_column_text _id=”794351″]
specific implementation policies:
- Ads should not be placed very close to or underneath buttons or any other object such that the
placement of the ad interferes with a user’s typical interaction with the app or ad. - Ads should not be placed in a location that covers up or hides any area that users have interest in
viewing during typical interaction. Ads should not be placed in areas where users will randomly
click or place their fingers on the screen. - Ads should not be placed on a ‘dead end’ screen. There must be a way to exit a screen without
clicking the ad (for example, a ‘back’ or ‘menu’ button). Otherwise, the user should be notified
that the home button will exit the application. - Ads should not be placed in applications that are running in the background of the device or outside
of the app environment. It should be clear to the user which application the ad is associated with
or implemented in. Examples include ads served in widgets; ads launched before the app has opened or
after the app has closed. - Ads should not be placed in a way that prevents viewing the app’s core content. Ads should not be
placed in a way that interferes with navigating or interacting with the app’s core content and
functionality. Examples include: an interstitial ad triggered every time a user clicks within the
app. - Publishers are not permitted to place ads on any non-content-based pages such as thank you, error,
log in, or exit screens. These are the screens that visitors may see upon launching the app, before
potentially leaving the app or after performing a specific action on the screen such as a purchase
or download. Ads that are the main focus on these types of screens can confuse a visitor into
thinking that the ads are actual content, so do not place ads on such screens.
1. Displaying a third-party site in your app
When an app displays someone else’s site within a frame, this is considered framing content. Publishers are
not permitted to frame third party content and monetize it without permission from the owners of that
content.
If a publisher owns the content, it can be framed in their app and monetized. However, if the framed content
is already being monetized by Doceree Ads, the framed content should not contain any additional code for
Doceree inside the version on the mobile app.
2. Sub-syndication and ad network mediation
Publishers may not enter into sub-syndication relationships (i.e., Doceree should have a direct relationship
with the publisher, rather than through an intermediate party).
3. Restricted information sharing
- Metrics: Publishers may not share access to the reporting console (unless with Doceree’s prior
written consent on which metrics to share). - Code: Publishers may not share either source Doceree code or uncompiled Doceree code with any third
party.
4. Personalized advertising
Doceree may use the advertising ID from the device on which the ad is serving to generate interests and
demographics (for example, ‘sports enthusiasts’). Interests, demographics, and other data may be used to
serve better targeted ads to the user. Additionally, your app’s privacy policy may need to be updated to
reflect the use of personalized advertising (formerly known as interest-based advertising) served via the
Doceree. Please take a moment to review your app’s privacy policies and ensure that they are up-to-date.
Because publisher pages and laws vary across countries, we’re unable to suggest specific privacy policy
language.
[/kc_column_text][/kc_column][/kc_row]