Privacy
When you use the Axon SDK as an advertiser, you are responsible for complying with applicable privacy regulations. If you collect and/or transmit personally identifiable information, you are responsible for protecting and managing that data.
You are fully responsible for correctly collecting consent values and other applicable flags and for passing those to AppLovin. This is true whether you use your own consent mechanism or a third-party API. The Axon SDK provides APIs with which you pass consent and other applicable flags to AppLovin.
Best practices:
- Solicit your own legal advice. Nothing in this document should be construed as legal advice.
- Read and understand the AppLovin Policies for Demand Partners, Privacy Policy, Data Sharing Requirements, and the integration guides offered by AppLovin.
- List AppLovin in your privacy policy as a third-party that collects data. Include a link to AppLovin in your privacy policy.
This framework helps facilitate compliance with:
- The General Data Protection Regulation (“GDPR”) and laws of similar effect
- Certain U.S. multi-state privacy requirements
- Data restrictions under COPPA and App Store policies
Consent and privacy requirements may extend beyond these. Apply them accordingly, based on the jurisdiction(s) of your users.
Consent and other applicable flags in GDPR and other regions
When you use the Axon SDK, AppLovin requires you to correctly set certain consent values and other applicable flags and to send those to AppLovin. You are fully responsible for correctly collecting and sending these values and flags. This is true whether you use your own consent mechanism or a third-party API.
Some of these flags indicate whether users from certain locations provided opt-in consent to collect and use their personal data for personalized data processing. These locations include the European Union, European Economic Area, the United Kingdom, and Switzerland.
Another flag indicates whether users from certain U.S. states opted out of the sale of their information.
When you initialize the Axon SDK, the SDK records the values that you set in the “Privacy States” fields to the log. These fields include “Has User Consent” and “Do Not Sell”.
Because the Axon SDK records the values of these fields when the SDK initializes, you must set these values before you initialize the Axon SDK. This ensures that the fields are set and passed to AppLovin correctly.
Forwarding Consent to Axon SDK
Using Google UMP (TCF v2 consent)
If you use Google’s CMP (UMP), the Axon SDK leverages Google UMP’s Additional Consent (AC) Mode, and automatically processes the consent states in the AC string.
Using a non-certified CMP
If you use a different CMP, contact your CMP provider to learn how to extract the consent states, so that you can forward them to the Axon SDK.
If the user consents to personalized data processing, set the user consent flag accordingly, then initialize the Axon SDK, to begin tracking conversions and in-app activity. After you set the consent value for a particular user, AppLovin respects that value for the lifetime of your application or until the user revokes consent to personalized data processing.
PrivacySettings.setHasUserConsent(true)[ALPrivacySettings setHasUserConsent: YES];
If the user does not consent to personalized data processing, set the user consent flag accordingly. After you set the consent value for a user, AppLovin respects that value for the lifetime of your application or until the user consents to personalized data processing.
PrivacySettings.setHasUserConsent(false)[ALPrivacySettings setHasUserConsent: NO];
Multi-State consumer privacy laws
State laws in the United States may require you to display a “Do Not Sell or Share My Personal Information” link to users in those states, or to provide other options through which those users can opt out of personalized data processing. Such users can opt out of both personalized data processing and the sale or sharing of their personal information for personalized data processing. You must set a flag for users from those states that indicates whether those users opt out in this way. If a user does not opt out in these ways, set the do-not-sell flag this way before initializing or using the Axon SDK:
PrivacySettings.setDoNotSell(false)[ALPrivacySettings setDoNotSell: NO];
If a user does opt out of interest-based advertising, set the do-not-sell flag this way:
ALPrivacySettings.setDoNotSell(true)[ALPrivacySettings setDoNotSell: YES];
Prohibition on children data or using the services for children or apps exclusively targeted to children
As explained in AppLovin’s Terms of Use, Policies for Demand Partners, and Policies for Publishers, you may not provide AppLovin with children data or cause that information to be provided via a third party. You may not initialize or use the Axon SDK in any way or otherwise use the AppLovin Services in connection with a “child” as defined under applicable laws. For example, in mixed-audience apps or “everyone” apps—i.e., apps whose users may include children—if a particular user of your app qualifies as a “child,” do not initialize or use the Axon SDK in any way.
You cannot use AppLovin Services in apps exclusively designed for, or exclusively directed to, children. For example, iOS Apps in the “Kids” category and Google Play apps that target children and must follow Families Ads & Monetization Policy requirements may not use the AppLovin Services at all. AppLovin does not knowingly collect personal information from children or serve advertisements to children.
You can find more examples in the following table:
| App category | Required actions |
|---|---|
| Apps directed to “children,” such as iOS apps in the “kids” categories | You may not use the AppLovin Services at all. |
| Apps directed to mixed audiences, including “children” | You may not initialize the Axon SDK or use the AppLovin Services in connection with any user who qualifies as a “child” under applicable law. |
| Apps directed to a general audience | You may not initialize the Axon SDK or use the AppLovin Services in connection with any user who qualifies as a “child” under applicable law. |
