Secure your app monetization

If you use any third-party SDKs in your app for marketing, advertising or any other purpose that tracks user behavior or data, the answer is most likely yes. Any processing activity that is not strictly necessary for the functioning of your app requires consent.

For most third-party technologies that collect your users’ data, you need to make sure to collect explicit consent choice from your users and to make sure that these consent choices are correctly passed to the relevant third-party technology. While this principle is straightforward, it is more complex to comply with all the requirements of the various privacy regulations around the world. Usercentrics CMP simplifies this for you and avoids the pain of building and maintaining a complex solution. Reach out to learn more.

Our pricing for apps is based on volume of users. More specifically, Average of Daily Active Users (ADAU) across all of your apps integrating the Usercentrics App CMP. You can integrate our CMP in unlimited apps with no extra cost. Please provide an ADAU estimate to a sales agent for a quote or visit our pricing page.

We define a Daily Active User as a unique user who used an app within a given calendar day. For example:

• A user opens your app once today, they count as 1 DAU today.
• A user opens your app 20 times today, they count as 1 DAU today.
• A user opens your app once today and 3 times tomorrow, they count as 1 DAU today and 1 DAU tomorrow.

For mobile apps, we support the iOS and Android platforms. From a technical perspective, we offer native SDKs for iOS and Android, but also SDKs for cross-platform frameworks: Flutter, React Native, and Unity.

For TV apps, we support tvOS, AndroidTV (and other AndroidTV based platforms, like FireTV), and any web-based platforms, like Samsung TV, LG webOS, Chromecast, PlayStation, Xbox, etc.

Yes, we have a dedicated Unity SDK for mobile games. You can learn more about it in our documentation.

Mobile app consent means getting permission from app users to collect and use their personal data. It respects user privacy by enabling users to control how apps use their data while also meeting international privacy standards. You can obtain consent using a consent management platform set up with legally compliant consent settings, including for cookie consent. Read our best practices for collecting mobile app consent.

Under many privacy laws, prior consent is mandatory before collecting user data for any purpose that’s not essential for the app to work, such as for marketing or advertising. The GDPR requires a lawful basis for processing user data, and consent must be explicit. Users need to opt in to allow the app to collect and use their data. Your app should display a user consent form designed to give users the option to accept or decline whether they share their data. Additionally, any data you collect must comply with your privacy program, including how user data will be protected.

Yes, the GDPR is the data privacy law for the European Union and applies to mobile apps that process data from users in the EU, even if the app developer is not an EU company. Mobile app consent under the GDPR must be explicit. Users need to opt in to allow apps to collect their data, using consent settings the app presents to them before it can collect any data.

The GDPR is designed to protect consumers’ personal data and rights, and require consent for all types of digital users, including those giving mobile app consent. Here are some requirements to ensure your mobile apps comply with the GDPR:

• Before obtaining users’ consent, clearly explain the types of data you want to collect and why, who will use it, how it will be stored, and how it will be used. You must share this information somewhere easily accessible and in a way that the target audience can understand.
• You must inform users why you’re requesting their data and collect only the data you need to fulfill that specific purpose. Users must consent to the specific purpose, and if you need data for a different or additional purpose, you must obtain new consent.
• Users must have a choice whether or not to consent to collection and processing of their data. If they decline, they cannot face negative consequences, such as being denied access to the app.
• Users must actively opt in to consent to their data being collected for consent to be valid. Using pre-ticked boxes or presuming consent if they don’t object aren’t good enough. Consent must be active and explicit.
• Users must be able to change or withdraw their consent at any time, just as easily as they gave it.
• You must document all instances of consent and be able to provide proof if a data protection authority requests it.
• Cookie consent falls under the GDPR, and mobile apps that use cookies to collect user data must comply with GDPR requirements.

If you use cookies to collect user data for marketing, advertising, analytics, or any other purpose not strictly necessary for your app to function, and the users reside in jurisdictions protected by data privacy laws requiring prior consent for data collection, sale, etc., then you need cookie consent for mobile apps. Cookie consent falls under the scope of the GDPR, and mobile apps that use cookies must comply with GDPR regulatory requirements. You can use cookie consent banners on your app to tell users that your app uses cookies and enable them to choose whether or not to share their data.

Many modern data privacy laws apply to any platform that collects user data, and this includes mobile apps. To prioritize user privacy, many international privacy laws require mobile app developers to have a lawful basis for using user data. Regulations such as the GDPR (EU), LGPD (Brazil) and POPIA (South Africa) all require user consent before you can process their data. Some state-level privacy laws in the United States, including the CCPA (California) and VCDPA (Virginia) require you to let users actively opt out of processing their data.

To protect user privacy, your mobile app must include consent settings that meet the requirements of privacy regulations where your users reside, which could mean worldwide. This includes obtaining explicit opt-in consent to meet GDPR requirements. Using a consent management platform like Usercentrics’ helps you collect consent compliantly without disrupting user experience.

Google’s Consent Mode facilitates the acquisition of user consent and seamlessly transmits it to Google. As a result, Google tools automatically adapt their behaviors. Additionally, Google complements this with conversion modeling and behavioral modeling to bridge any gaps, which help you to achieve your marketing goals. For mobile applications, this is vital to ensure the effective operation of Firebase Services. Beginning in March 2024, failing to enable Consent Mode will result in the inability to capture new EEA users within your audiences.To successfully incorporate Google Consent Mode V2 into your mobile application, follow our step-by-step app documentation or games documentation.