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 Axon. 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 Axon.

Best practices:

• Solicit your own legal advice. Nothing in this document should be construed as legal advice.
• Read and understand the Axon Policies for Demand Partners, Axon’s Privacy Policy, and the integration guides offered by Axon.
• List Axon in your privacy policy as a third-party that collects data. Include a link to Axon in your privacy policy.

This framework helps facilitate compliance with:

• 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

When you use the Axon SDK, Axon requires you to correctly set certain consent values and other applicable flags and to send those to Axon. 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.

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 “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 Axon correctly.

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 interest-based advertising. Such users can opt out of both interest-based advertising and the sale or sharing of their personal information for interest-based advertising. 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:

If a user does opt out of interest-based advertising, set the do-not-sell flag this way:

Prohibition on children data or using the services for children or apps exclusively targeted to children

As explained in Axon’s Terms of Use, Policies for Demand Partners, and Policies for Publishers, you may not provide Axon 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 Axon 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 Axon 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 Axon Services at all. Axon does not knowingly collect personal information from children or serve advertisements to children.

You can find more examples in the following table: