App Privacy Details
With iOS 14, Apple has created an App Privacy page to help app users understand how each app uses the data it collects. App Store Connect requires Account Holders/Admins to identify the types of data collected by their app, including data collected by third-party integrations, such as the MoPub SDK. To assist with this process, we have provided the below chart indicating the types of data that the MoPub SDK may collect.
This information is provided only for your convenience. The precise data types collected, and how you can use that data, will depend on your specific configuration and implementation of the MoPub SDK.
You should compare the below list of data types collected by the MoPub SDK against your specific configuration and data handling practices when determining the data types collected by your app and how they are used.
Types of data
The below chart indicates the types of data that the MoPub SDK may collect. Except where specifically noted, the chart only includes information about data types that the MoPub SDK collects by default.
|APPLE DATA TYPES||DESCRIPTION||MOPUB COLLECTS||DATA USE|
|Name||Such as first or last name|
|Email Address||Including but not limited to a hashed email address|
|Phone Number||Including but not limited to a hashed phone number|
|Physical Address||Such as home address, physical address, or mailing address|
|Other User Contact Info||Any other infomation that can be used to contact the user outside the app|
|Health and Fitness|
|Health||Health and medical data, including but not limited to data from the Clinical Health Records API, HealthKit API, MovementDisorder APIs, or health-related human subject research or any other user provided health or medical data|
|Fitness||Fitness and exercise data, including but not limited to the Motion and Fitness API|
|Payment Info||Such as form of payment, payment card number, or bank account number. If your app uses a payment service, the payment information is entered outside your app, and you as the developer never have access to the payment information, it is not collected and does not need to be disclosed.|
|Credit Info||Such as credit score|
|Other Financial Info||Such as salary, income, assets, debts, or any other financial information|
|Precise Location||Information that describes the location of a user or device with the same or greater resolution as a latitude and longitude with three or more decimal places||Uses: Third party advertising, analytics
The MoPub SDK may collect coarse and precise location data if your app and configuration of the MoPub SDK enables such collection and the user has provided consent. Location data collection processes vary depending on the iOS and MoPub SDK versions being used.
For further details see, https://developers.mopub.com/publishers/ios/data-passing/#passing-location
|Coarse Location||Information that describes the location of a user or device with lower resolution than a latitude and longitude with three or more decimal places, such as Approimate Location Services|
|Sensitive Info||Such as racial or ethnic data, sexual orientation, pregnancy or childbirth information, disability, religious or philosophical beliefs, trade union membership, political opinion, genetic information, or biometric data|
|Contacts||Such as a list of contacts in the user’s phone, address book, or social graph|
|Emails or Text Messages||Including subject line, sender, recipients, and contents of the email or message|
|Photos or Videos||The user’s photos or videos|
|Audio Data||The user’s voice or sound recordings|
|Gameplay Content||Such as user-generated content in-game|
|Customer Support||Data generated by the user during a customer support request|
|Other User Content||Any other user-generated content|
|Browsing History||Information about content the user has viewed that is not part of the app, such as websites|
|Search History||Information about searches performed in the app|
|User ID||Such as screen name, handle, account ID, assigned user ID, customer number, or other user- or account- level ID that can be used to identify a particular user or account|
|Device ID||Such as the device’s advertising identifier, or other device-level ID||Uses: Third party advertising, analytics
Identifier For Advertisers collected where available. Identifier for Vendors collected where available. Proprietary ID for that app/device combination where available.
|Purchase History||An account’s or individual’s purchases or purchase tendencies|
|Product Interaction||Such as app launches, taps, clicks, scrolling views, saved place in a game, video, or song, or other information about how the user interacts with the app||Uses: Third party advertising, analytics
MoPub may collect SDK launch timestamps.
|Advertising Data||Such as information about the advertisements the user has seen||Uses: Third party advertising, analytics
MoPub may collect data on ad interactions, including view time, click behaviour.
|Other Usage Data||Any other data about user activity in the app|
|Crash Data||Such as crash logs|
|Performance Data||Such as launch time, hang rate, or energy use|
|Other Diagnostic Data||Any other data collected for the purposes of measuring technical diagnostics related to the app|
|Other Data Types||Any other data types not mentioned||Uses: Third party advertising, analytics
MoPub collects device make and model data as well as cell carrier data where available.
Publishers may also configure the service to collect additional data types that are not collected by default. For further details see, https://developers.mopub.com/publishers/ios/data-passing/#passing-location
Last updated December 03, 2020
TWITTER, MOPUB, and the Bird logo are trademarks of Twitter, Inc. or its affiliates. All third party logos and trademarks included are the property of their respective owners.
© 2020 MoPub (a division of Twitter, Inc.)