Introduction
Please note: This article provides information relevant to publishing the branded mobile app on the Apple App Store. For more information about the full process refer to the article Re-signing and Publishing the Branded Mobile App.
When you publish or update your branded mobile app on the Apple App Store, you will need to complete a form about the types of data collected in the app.
The tables below provide the data collection information for the Go.Learn app configuration. You can use these as a general guideline. However check each section because your branded mobile app may differ from Go.Learn. For example:
- If you didn’t connect your app to Firebase, the analytics part does not apply.
More information from Apple App Store Help about app data privacy (opens in a new tab)
Data types
| Contact info |
| Name |
Not collected |
| Email address |
Not collected |
| Phone number |
Not collected |
| Physical address |
Not collected |
| Other user contact info |
Not collected |
| Health and fitness |
| Health |
Not collected |
| Fitness |
Not collected |
| Financial info |
| Payment info |
Not collected |
| Credit info |
Not collected |
| Other financial info |
Not collected |
| Location |
| Precise location |
Step 1:
[X] App functionality
[X] Other Purposes
Step 2:
[X] No, precise location data collected from this app is not linked to the user’s identity
Step 3:
[X] No, we do not use precise location data for tracking purposes
Note:
This data can only be accessed by a navigation app started by Go.Learn when the user actively decides to get driving directions to reach the location of an ILT session.
|
| Course location |
Not collected |
| Sensitive info |
| Sensitive info |
Not collected |
| Contacts |
| Contacts |
Not collected |
| User content |
| Emails or text messages |
Not collected |
| Photos or videos |
Step 1:
[X] App functionality
Step 2:
[X] Yes, photos or videos collected from this app are linked to the user’s identity
Step 3:
[X] No, we do not use photos or videos for tracking purposes
Note:
The gallery can be accessed if the user actively decides to share an image in his/her gallery with other users of the platform.
|
| Audio data |
Not collected |
| Gameplay content |
Not collected |
| Customer support |
Not collected |
| Other user content |
Not collected |
| Browsing history |
| Browsing history |
Not collected |
| Search history |
| Search history |
Not collected |
| Identifiers |
| User ID |
Step 1:
[X] App functionality
Step 2:
[X] Yes, User IDs collected from this app are linked to the user’s identity
Step 3:
[X] No, we do not use User IDs for tracking purposes
Note:
Enabling Google and Firebase analytics does not impact these settings because the analytics tools generate new user/device/instance IDs by themselves which are different from the one used by the application platform
|
| Device ID |
Not collected
Note:
If you have enabled the support for Adjust as MMP: Yes, Adjust collects Device ID data on your behalf.
More info on Adjust KB (opens in a new tab)
|
| Usage data |
| Product interaction |
Step 1:
[X] Analytics
Step 2:
[X] No, Product interaction data collected from this app are linked to the user’s identity
Step 3:
[X] No, we do not use product interaction data for tracking purposes (only if the client has connected the app to Firebase and has enabled the Analytics)
Note:
The standard Go.Learn app is integrated with Firebase Analytics. In the branded mobile app, it’s optional. It can be enabled by any company that owns a branded mobile app.
|
| Advertising data |
Not collected
|
| Other usage data |
Step 1:
[X] Analytics
Step 2:
[X] No, Analytics data collected from this app are linked to the user’s identity
Step 3:
[X] No, we do not use Analytics Data for tracking purposes
(only if the client has connected the app to Firebase and has enabled the Analytics)
Note:
This data is collected by Firebase Analytics (optionally enabled by the client): More information on data collection in the Firebase Help (opens in a new tab)
Note:
If you have enabled the support for Adjust as MMP: Yes, Adjust collects this data on your behalf. Adjust collects session events by default. The other types of “Usage Data” are optional and Adjust can collect them on your behalf if you configure it.
More information on Adjust KB (opens in a new tab)
|
| Diagnostics |
| Crash data |
Step 1:
[X] App functionality
Step 2:
[X] No, Crash data collected from this app are linked to the user’s identity
Step 3:
[X] No, we do not use Crash Data for tracking purposes
Note:
The app supports Crashlytics. It’s enabled by default in Go.Learn and it can be optionally enabled in the branded mobile app.
|
| Performance data |
Not collected |
| Other diagnostic data |
Step 1:
[X] App functionality
Step 2:
[X] No, Other Diagnostic Data collected from this app are linked to the user’s identity
Step 3:
[X] No, we do not use Other Diagnostic Data for tracking purposes
Note:
Only the data collected by Crashlytics (if enabled).
|
| Other data |
| Other data types |
Not collected
Note:
If you have enabled the support for Adjust as MMP: Yes, Adjust collects this data on your behalf. For example: Device metadata, such as OS version and Adjust SDK version.
More information on Adjust KB (opens in a new tab)
|