GDPR

We specified your responsibilities for obtaining consent from end-users of your apps in our updated Privacy Policy. By updating GDPR compatible SDK you agree that you’re responsible for inform the end-users and take their consent. Please note that the consent collection applies only to users located in the European Economic Area, the United Kingdom, and Switzerland. As data controller you should take consent of end-users by preparing consent window, you can find samples below. When you take end-user consent, the response will be passed to Admost SDK. You can find the implementation here

consent

Network GDPR Complience

Ad Network Android IOS
AdColony

AdMob

Adtiming
Amazon

AppLovin

Appnext

Appsamurai
ChartBoost

Criteo

Facebook

Flurry

Fyber

HyprMX

InMobi

Inneractive
IronSource

LeadBolt
LoopMe

Mobfox

Mopub

MyTarget
Nexage

Ogury

Pollfish
Smaato

StartApp

Tapjoy

TapResearch
TikTok
UnityAds

Vungle

YandexAds
YouAppi

GDPR Rules

Admost provides two methods for GDPR compatibility: config.SubjectToGDPR and config.UserConsent.

Publisher have to set config.SubjectToGDPR = "1" if the user is located in European Union. Otherwise, publisher have to set config.SubjectToGDPR = "0" . If publisher does not use this method, SubjectToGDPR status remains as unknown. In this case, Admost SDK automatically determines whether the user is in EU or not which is totally under responsibility of the publisher. If user is in EU, networks are not allowed to show personalized ads. If the user is not located in EU, the ad networks are allowed to show personalized ads.

On condition that, the publisher obtains neither user's SubjectToGDPR status nor any negative legal consequences, SubjectToGDPR must set config.SubjectToGDPR = "1" for each user. In this case, Admost considers all users as subject to GDPR and if the consent is not allowed, Admost blocks ad networks to collect data from users. Which may cause a decrease on overall revenue performance apart from Admost.

If the publisher obtains user's consent and sets config.UserConsent = "1", personalized ads would be shown to the users. Otherwise, the publisher sets config.UserConsent = "0" which would block the personalized ads, unless the user is not subject to GDPR.

If the publisher does not use config.UserConsent method , userConsent status remains unknown. In this case, if the publisher provides config.SubjectToGDPR = "1", the ad networks do not have ability to serve personalized ads.If the publisher provides config.SubjectToGDPR = "0", the ad networks have ability to serve personalized ads.

If the publisher does not provide both config.UserConsent and config.SubjectToGDPR, Admost decides whether the user is located in EU or not which is totally under responsibility of the publisher.

If the publisher wants to obtain neither the user's consent nor any negative legal consequences, the publisher must set config.UserConsent = "0" for every user. In this case, Admost considers the user has no consent, the ad networks are not allowed to serve personalized ads, except only the publisher does not provide config.SubjectToGDPR = "0" .