GDPR

Introduction

The General Data Protection Regulation (GDPR) was enacted across the European Union on May 25, 2018. These new regulations create a framework to protect personal data about individuals in the EU and must be adhered to by all businesses that collect or process such data. Failure to comply with GDPR can result in strict penalties for non-compliant companies.

As a trusted partner of leading global brands, InMobi is committed to data protection and protecting consumer privacy while creating a safe and transparent marketplace for advertisers and generating value for our publisher partners.

Complying with GDPR

If not already on the current InMobi SDK version (SDK 710 for Android, SDK 711 for iOS) or above, upgrade to the latest version here: SDK. The same applies for Mobile Web <link it with the mobile web> inventory.

If you have already signed and shared Data Protection Rider with InMobi, then no action is required here. Please proceed to Step 3.

Note

  1. All of the following steps are MANDATORY. Publishers failing to comply will not be considered GDPR compliant.
  2. If you have already signed and shared Data Protection Rider with InMobi, then no action is required here. Please proceed to Step 3.

GDPR settings under the “Compliance” Tab

  1. Log in to the InMobi Publisher Dashboard and accept InMobi’s new Terms of Service (TOS). The new InMobi TOS has GDPR-related clauses.
  2. If you have traffic from the EU, navigate to Compliance GDPR Settings within the Publisher Dashboard and click Allow Data Processing. If not applicable to your inventory, select Restrict Data Processing.
  3. If your app falls under the age-gating requirements in GDPR, i.e. your app targets children < 16 years of age, please turn the Children's Privacy Compliance flag on within your app settings. If the app was marked for Children's Privacy Compliance, we would automatically flag the app as compliant - < 13 years for the US and < 16 years for the EU. This is valid:

    • for creating new apps/mobile websites,
    • for updating existing apps/mobile websites.
  4. Upgrade your connection to the latest InMobi SDK version. For mobile web, see our Mobile Web specifications. Please reach out to your InMobi account manager for the latest API specifications.

TCF v2.0

The Transparency and Consent Framework (TCF) is the GDPR consent solution developed by the IAB Europe and industry stakeholders to create an industry standard for collecting, managing, and sharing user consent.

The TCF’s objective is to help all parties in the digital advertising chain ensure that they comply with the EU’s GDPR and ePrivacy Directive when processing personal data or accessing and/or storing information on a user’s device, such as cookies, advertising identifiers, device identifiers, and other tracking technologies.

InMobi supports TCF v2.0, the second iteration of IAB Europe’s Transparency and Consent Framework.

TCF v2.0 enables consumers to grant or withhold consent and exercise their ‘right to object to data being processed. Consumers also gain more control over whether and how vendors may use certain data processing features, for example, precise geolocation.

TCF v2.0 also provides greater control and flexibility to publishers depending upon how it is integrated and collaborated with the technology partners. New publisher functionality includes the ability to restrict the purposes for which ad tech vendors process personal data on a per-vendor basis. To serve personalized ads, we need the following permission from the publisher.

InMobi Vendor id, i.e., 333 in the IAB consent string Standard purposes [1, 3, 4] in the IAB consent string Legitimate interest purposes [2,7,10] in the IAB consent string Publishers implementing TCF v2.0 need to use an approved CMP compliant with the IAB Europe’s CMP Compliance Programme. You can find the list of TCF 2.0-compliant CMPs here:

To serve personalized ads, please note that we need the following permission from publishers:

  • InMobi Vendor id, i.e., 333 in the IAB consent string
  • Standard purposes [1, 3, 4] in the IAB consent string
  • Legitimate interest purposes [2,7,10] in the IAB consent string

Publishers implementing TCF v2.0 need to use an approved CMP compliant with the IAB Europe’s CMP Compliance Programme. For more information, see CMP List.

FAQs

Is InMobi a Data controller, Joint Controller or Data Processor?

InMobi is a Joint Controller with the Publisher.

How will InMobi collect the data?

InMobi does not gather user consent directly and will rely on the publisher to obtain appropriate consent from data subjects and pass that on to InMobi.

What will InMobi do in cases where user consent is not present?

InMobi will never collect or pass user data to an advertiser or a publisher without user consent.

What will InMobi do in cases where user consent is not present?

InMobi will never collect or pass user data to an advertiser or a publisher without user consent.

What happens if the user withdraws the consent?

Publishers must notify InMobi where consent is withdrawn or revoked, and accordingly, InMobi will honor such data subject’s request.

What happens if I am not compliant with InMobi’s GDPR solution?

For all requests originating from users who have not given consent, InMobi will serve non-targeted ads to these users.

To comply with GDPR, upgrade your SDK today.

You can read more about InMobi’s GDPR readiness here.

For any queries or concerns, you can contact your InMobi Account Manager or write us at gdprcompliance-group@inmobi.com.

On This Page

Last Updated on: 27 Oct, 2022