App privacy in the App Store
As of December 8, 2020, Apple requires mobile app developers to report which data they collect through the app to the App Store.
Data types
Review the list of data types below and compare them with the data collection methods in your app:
Data type | Description | AppMetrica SDK data collection (default configuration) |
---|---|---|
Data type | Description | AppMetrica SDK data collection (default configuration) |
---|---|---|
Contact information | ||
---|---|---|
Name | First or last name. | No |
Email address | Including the hashed email address. | |
Phone number | Including the hashed phone number. | |
Physical address | Home, physical, or postal address. | |
Other user contact information | Any other information that can be used to communicate with the user outside the app. |
Contact information | ||
---|---|---|
Name | First or last name. | No |
Email address | Including the hashed email address. | |
Phone number | Including the hashed phone number. | |
Physical address | Home, physical, or postal address. | |
Other user contact information | Any other information that can be used to communicate with the user outside the app. |
Health and fitness | ||
---|---|---|
Health | Health and medical data. | No |
Fitness | Data on physical condition and exercises. |
Health and fitness | ||
---|---|---|
Health | Health and medical data. | No |
Fitness | Data on physical condition and exercises. |
Financial information | ||
---|---|---|
Payment information | For example, payment method, payment card number, or bank account number. If the app uses a payment service, payment information is entered outside the app and the developer doesn't have access to it. Such information isn't collected and doesn't need to be disclosed. | No |
Loan information | For example, credit rating. | |
Other financial information | For example, income, assets, salary, debts, or any other financial information. |
Financial information | ||
---|---|---|
Payment information | For example, payment method, payment card number, or bank account number. If the app uses a payment service, payment information is entered outside the app and the developer doesn't have access to it. Such information isn't collected and doesn't need to be disclosed. | No |
Loan information | For example, credit rating. | |
Other financial information | For example, income, assets, salary, debts, or any other financial information. |
Geolocation | ||
---|---|---|
Accurate geolocation | Information about the location of a user or device with the same or higher resolution than latitude and longitude, with three or more decimal places. | Yes, if the |
Approximate geolocation | Information about the location of a user or device with a lower granularity than latitude and longitude, with three or more decimal places. For example, approximate location detection services. |
Geolocation | ||
---|---|---|
Accurate geolocation | Information about the location of a user or device with the same or higher resolution than latitude and longitude, with three or more decimal places. | Yes, if the |
Approximate geolocation | Information about the location of a user or device with a lower granularity than latitude and longitude, with three or more decimal places. For example, approximate location detection services. |
Confidential information | ||
---|---|---|
Confidential data | For example, racial or ethnic data, religious or philosophical beliefs, sexual orientation, trade union membership, political beliefs, information about pregnancy or childbirth, disabilities, genetic information, or biometric data. | No |
Confidential information | ||
---|---|---|
Confidential data | For example, racial or ethnic data, religious or philosophical beliefs, sexual orientation, trade union membership, political beliefs, information about pregnancy or childbirth, disabilities, genetic information, or biometric data. | No |
Contacts | ||
---|---|---|
Contacts | For example, a contact list in the user's phone, an address book, or a social network. | No |
Contacts | ||
---|---|---|
Contacts | For example, a contact list in the user's phone, an address book, or a social network. | No |
User-generated content | ||
---|---|---|
Emails or text messages | Including a subject line, sender, recipients, and contents of the email or message. | No |
Photos or videos | User's photos or videos. | |
Audio data | User's voice or sound recordings. | |
Game content | For example, the logic of a multiplayer game or gameplay, saved games, user-generated content in the game. | |
User support service | Data received by the user when making a request to the support service. | |
Other user-generated content | Any other user-generated content. |
User-generated content | ||
---|---|---|
Emails or text messages | Including a subject line, sender, recipients, and contents of the email or message. | No |
Photos or videos | User's photos or videos. | |
Audio data | User's voice or sound recordings. | |
Game content | For example, the logic of a multiplayer game or gameplay, saved games, user-generated content in the game. | |
User support service | Data received by the user when making a request to the support service. | |
Other user-generated content | Any other user-generated content. |
Browsing history | ||
---|---|---|
Browsing history | Information about browsing content that is not part of the app. For example, websites. | No |
Browsing history | ||
---|---|---|
Browsing history | Information about browsing content that is not part of the app. For example, websites. | No |
Search history | ||
---|---|---|
Search history | Information about searching through the app. | No |
Search history | ||
---|---|---|
Search history | Information about searching through the app. | No |
IDs | ||
---|---|---|
User ID | For example, username, alias, account ID, user ID, client number, or another user or account ID that can be used to identify a specific user or account. | No The app developer can configure the transmission of this data. |
Device ID | For example, an advertising ID or another device ID. | Yes, if there is user permission. You need to implement a request for permission on your own. |
IDs | ||
---|---|---|
User ID | For example, username, alias, account ID, user ID, client number, or another user or account ID that can be used to identify a specific user or account. | No The app developer can configure the transmission of this data. |
Device ID | For example, an advertising ID or another device ID. | Yes, if there is user permission. You need to implement a request for permission on your own. |
Purchases | ||
---|---|---|
Purchase history | Purchases or trends of purchases on behalf of an account or an individual user. | Yes, from SDK versions 4.0.0+ The app developer can disable transmission of this data using the revenueAutoTrackingEnabled property. |
Purchases | ||
---|---|---|
Purchase history | Purchases or trends of purchases on behalf of an account or an individual user. | Yes, from SDK versions 4.0.0+ The app developer can disable transmission of this data using the revenueAutoTrackingEnabled property. |
Usage data | ||
---|---|---|
Interaction with the product | For example, information about app launches, taps, and scrolls, data about listening to music and watching videos, save locations for games, videos, or songs, as well as other information about the user's interaction with the app. | Yes, if it is a launch event. In other cases, no. The developer can completely disable |
Ad data | Information about the ads that the user viewed. | No The app developer can configure the transmission of this data. |
Other usage data | Any other data about the user's activity in the app. | No |
Usage data | ||
---|---|---|
Interaction with the product | For example, information about app launches, taps, and scrolls, data about listening to music and watching videos, save locations for games, videos, or songs, as well as other information about the user's interaction with the app. | Yes, if it is a launch event. In other cases, no. The developer can completely disable |
Ad data | Information about the ads that the user viewed. | No The app developer can configure the transmission of this data. |
Other usage data | Any other data about the user's activity in the app. | No |
Troubleshooting | ||
---|---|---|
Crash data | For example, crash logs. | No |
Performance data | For example, startup time, lag frequency, or power consumption. | Yes AppMetrica can collect battery level data for crash analytics. |
Other troubleshooting data | Any other data about technical diagnostics related to the app. | No |
Troubleshooting | ||
---|---|---|
Crash data | For example, crash logs. | No |
Performance data | For example, startup time, lag frequency, or power consumption. | Yes AppMetrica can collect battery level data for crash analytics. |
Other troubleshooting data | Any other data about technical diagnostics related to the app. | No |
Other data | ||
---|---|---|
Other data types | Any other data types not mentioned. | Yes AppMetrica can collect additional data. For example, technical information about the device: operating system version, screen type, and other information. |
Other data | ||
---|---|---|
Other data types | Any other data types not mentioned. | Yes AppMetrica can collect additional data. For example, technical information about the device: operating system version, screen type, and other information. |
Data usage
Select the categories that correspond to the data usage in your app:
Goal | Definition |
---|---|
Third-party ads | Displaying third-party ads in your app or sharing data with organizations that display third-party ads. |
Developer's advertising or marketing | Displaying your ads in the app, sending marketing messages directly to your users, or sharing data with organizations that will display your ads. |
Analytics | Using data to evaluate user behavior, understand the effectiveness of existing product features, plan new features, or measure audience size or characteristics. |
Product personalization | Setting up what the user sees. For example, a list of recommended products, messages, or offers. |
App features | For example, to authenticate a user, enable features, prevent fraud, implement security measures, ensure fault-free server operation, minimize app failures, increase scalability and performance, or support users. |
Other goals | Any other goals not mentioned. |
Goal | Definition |
---|---|
Third-party ads | Displaying third-party ads in your app or sharing data with organizations that display third-party ads. |
Developer's advertising or marketing | Displaying your ads in the app, sending marketing messages directly to your users, or sharing data with organizations that will display your ads. |
Analytics | Using data to evaluate user behavior, understand the effectiveness of existing product features, plan new features, or measure audience size or characteristics. |
Product personalization | Setting up what the user sees. For example, a list of recommended products, messages, or offers. |
App features | For example, to authenticate a user, enable features, prevent fraud, implement security measures, ensure fault-free server operation, minimize app failures, increase scalability and performance, or support users. |
Other goals | Any other goals not mentioned. |
User-related data
Determine whether each data type is associated with a user ID (through their account, device, or other data). Collecting information through the app is often associated with the user's personal data, unless special privacy protection measures are provided:
- Deleting information about any direct IDs, such as the user's ID or name, before collecting data.
- Processing data to break the connection and prevent re-connection with real IDs.
To ensure that the data isn't associated with the identity of a particular user, avoid certain actions after collecting:
- Don't associate the data with the user ID.
- Don't link the data to other datasets that may link it to a specific user ID.
Tracking
Tracking is the comparison of data collected in your app about a specific user or device (for example, user ID, device ID, or profile) with data from third parties for the purpose of advertising or exchanging data.
Tracking examples:
- Targeted ads in your app based on user data collected from apps and websites of other companies.
- Transmitting device location information or email lists to the data broker.
- Granting a third-party advertising network access to a list of emails, advertising IDs, or other IDs for targeted ads or for attracting new users.
- Placing a third-party SDK in your app that combines user data from your app with user data from other developers' apps for targeting or measuring the effectiveness of ads (even if you don't use the SDK for these purposes). For example, when logging in with the SDK, data from your app is used to enable targeted ads in other developers' apps.