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 GDPR Compatibility
Adcolony
Admob
Amazon
Applovin
Appnext
AppSamurai
ChartBoost
Display IO
Facebook
Flurry
Fyber
Glispa
InMobi
InnerActive
IronSource
LoopMe
Mintegral
Mobfox
Mopub
Nexage
Ogury
Smaato
Startapp
Tapjoy
Unity
Vungle
YouAppi

GDPR Rules

Admost provides you two methods for GDPR compatibility: setSubjectToGDPR() and setUserConsent().

If you can determine whether the user is located in European Union or not, you can use optional setSubjectToGDPR() method to set user's subject to GDPR flag. If you do not use this method, SubjectToGDPR status remains as unknown. In this case, Admost SDK will try to determine whether the user is in EU or not which is totally under the responsibility of you. If the 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 you want to obtain neither user's SubjectToGDPR status nor any negative legal consequences, SubjectToGDPR must set setSubjectToGDPR(true) 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 in overall revenue performance apart from Admost.

If you obtain user's consent and set setUserConsent(true), personalized ads would be shown to the users. Otherwise, you set setUserConsent(false) which would block the personalized ads, unless the user is not subject to GDPR.

If you do not usesetUserConsent(), user consent status remains unknown. In this case, if you provide setSubjectToGDPR(true), the ad networks do not have the ability to serve personalized ads. If you provide setSubjectToGDPR(false), the ad networks have the ability to serve personalized ads.

If you do not provide both setUserConsent() and setSubjectToGDPR(), Admost decides whether the user is located in EU or not which is totally under the responsibility of you.

If you want to obtain neither the user's consent nor any negative legal consequences, you must set setUserConsent(false) 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 you do not provide setSubjectToGDPR(false).