-
Notifications
You must be signed in to change notification settings - Fork 3
Privacy Regulations
⚡ Before you start
Make sure you have correctly configure SDK.
- Prohibition on Personal Information from Children
- Consent Flags in GDPR and Other Regions
- California Consumer Privacy Act (CCPA)
- Unity User Consent module
When you use the CAS SDK, CleverAdsSolutions requires you to correctly set flags that indicate whether users located in certain geographic areas, including in the European Union, European Economic Area, United Kingdom, and Switzerland (collectively, the "European Countries"), have provided opt-in consent for the collection and use of personal data for interest-based advertising. CAS also requires you to set flags indicating whether users are in an age-restricted category or if California users have opted out of sale of their information.
A detailed article on the use of user data can be found in the Privacy Policy.
⚠️ We recommend to set Privacy Settings before initializing CAS SDK.
Publishers may designate all inventory within their applications as being child-directed or as COPPA-applicable though our UI. Publishers who have knowledge of specific individuals as being COPPA-applicable should make use of the API discussed below to inform CAS and all downstream consumers of this information.
❕Read more about Children’s Online Privacy Protection Act (COPPA)
❕Please remember that CAS tools are designed to facilitate compliance and do not relieve any particular publisher of its obligations under the law.
If you know that the user falls within an age-restricted category (i.e., under the age of 16), you must set the Children audience flag:
CAS.MobileAds.settings.taggedAudience = Audience.Children;It also allows application to comply with the Google Play Families Policy requirements:
- Ads displayed to those users do not involve interest-based advertising or remarketing;
- Ads displayed to those users present content that is appropriate for children;
- Ads displayed to those users follow the Families ad format requirements;
- Compliance with all applicable legal regulations and industry standards relating to advertising to children.
If you know that the user does not fall within an age-restricted category, you must set the NotChildren audience flag:
CAS.MobileAds.settings.taggedAudience = Audience.NotChildren;The user's age has not been determined.
CAS.MobileAds.settings.taggedAudience = Audience.Mixed;If your app's target age groups include both children and older audiences, any ads that may be shown to children must comply with Google Play's Families Ads Program.
A neutral age screen must be implemented so that any ads not suitable for children are only shown to older audiences.
A neutral age screen is a mechanism to verify a user's age in a way that doesn't encourage them to falsify their age and gain access to areas of your app that aren't designed for children, for example, an age gate.
The following instructions apply if you are using your own or a third-party party consent mechanism.
If the user consents to interest-based advertising, set the user consent Accepted flag:
CAS.MobileAds.settings.userConsent = ConsentStatus.Accepted;If the user does NOT consent to interest-based advertising, set the user consent Denied flag:
CAS.MobileAds.settings.userConsent = ConsentStatus.Denied;Once you set the consent value, CAS will continue to respect that value for the lifetime of your application or until the user consents to interest-based advertising.
California law may require you to display a “Do Not Sell My Personal Information” link or provide other options to users located in the State of California. If so, you must set a flag that indicates whether a California-based user has opted out of interest-based advertising.
If a user does NOT opt out of interest-based advertising, set the OptInSale flag:
CAS.MobileAds.settings.userCCPAStatus = CCPAStatus.OptInSale;If a user does opt out of interest-based advertising, set the OptOutSale flag:
CAS.MobileAds.settings.userCCPAStatus = CCPAStatus.OptOutSale;You do not need to set this flag for users who are outside California. If you do set this flag for such users, this will not impact how ads are served to them.
CAS supports your handling of CCPA opt-out values on behalf of supported mediation partners. CAS shares these set consent values via adapters.
For those networks on whose behalf CAS does not support your handling of CCPA opt-out values, you must work directly with the network to determine any support those networks may provide for purposes of your obligations for CCPA compliance.
To learn how to implement Meta Audience Network’s “Limited Data Use” flag, read the Additional Meta AudienceNetwork steps.
Every application, except for children, must make certain disclosures to users in the European Economic Area (EEA) along with the UK and obtain their consent to use cookies or other local storage, where legally required, and to use personal data (such as AdID) to serve ads. This policy reflects the requirements of the EU ePrivacy Directive and the General Data Protection Regulation (GDPR).
The CAS Unity Consent provides tools for publishers to request consent for personalized ads as well as to handle Apple's App Tracking Transparency (ATT) requirements. Publishers can use the SDK to handle either or both of these requests by showing a single a form, as all of the configuration happens in the unity inspector.
🔗 Done! What’s Next?
- Initialize CAS before using ad formats using UnityEditor or Script C#
Important
We've moved!
Visit the updated CAS.AI docs.
- Project Setup
- Configuring SDK
- Include Android
- Include iOS
- Additional mediation steps
- App-ads.txt🔗