Data information
Apple requires app developers to provide the data usage policy of the app when they submit their app to the App Store. Below are the different categories identified by Apple and the corresponding data type used by the Amplify library.
Contact info
| Data Type | Amplify Category | Purpose | Linked To Identity | Tracking | Provided by developer |
|---|---|---|---|---|---|
| Name | |||||
| Auth | App Functionality | ✅ | ❌ | ✅ | |
| Email Address | |||||
| Auth | App Functionality | ✅ | ❌ | ✅ | |
| Phone Number | |||||
| Auth | App Functionality | ✅ | ❌ | ✅ |
User Content
| Data Type | Amplify Category | Purpose | Linked To Identity | Tracking | Provided by developer |
|---|---|---|---|---|---|
| Photos or Videos | |||||
| Storage | App Functionality | ❌ | ❌ | ✅ | |
| Predictions | App Functionality | ❌ | ❌ | ✅ | |
| Audio Data | |||||
| Predictions | App Functionality | ❌ | ❌ | ✅ |
Identifiers
| Data Type | Amplify Category | Purpose | Linked To Identity | Tracking | Provided by developer |
|---|---|---|---|---|---|
| User ID | |||||
| Auth | App Functionality | ✅ | ❌ | ❌ | |
| Analytics | Analytics | ✅ | ✅ | ❌ | |
| Device ID | |||||
| Auth | App Functionality | ✅ | ❌ | ❌ | |
| Analytics | Analytics | ✅ | ✅ | ❌ |
Other Data
| Data Type | Amplify Category | Purpose | Linked To Identity | Tracking | Provided by developer |
|---|---|---|---|---|---|
| OS Version | |||||
| All categories | Analytics | ❌ | ✅ | ❌ | |
| OS Name | |||||
| All categories | Analytics | ❌ | ✅ | ❌ | |
| Locale Info | |||||
| All categories | Analytics | ❌ | ✅ | ❌ | |
| App Version | |||||
| Auth | App Functionality | ✅ | ❌ | ❌ | |
| Min OS target of the app | |||||
| Auth | App Functionality | ✅ | ❌ | ❌ | |
| Timezone information | |||||
| Auth | App Functionality | ✅ | ❌ | ❌ | |
| Network information | |||||
| Auth | App Functionality | ✅ | ❌ | ❌ | |
| Has SIM card | |||||
| Auth | App Functionality | ✅ | ❌ | ❌ | |
| Cellular Carrier Name | |||||
| Auth | App Functionality | ✅ | ❌ | ❌ | |
| Device Model | |||||
| Auth | App Functionality | ✅ | ❌ | ❌ | |
| Device Name | |||||
| Auth | App Functionality | ✅ | ❌ | ❌ | |
| Device OS Version | |||||
| Auth | App Functionality | ✅ | ❌ | ❌ | |
| Device Height and Width | |||||
| Auth | App Functionality | ✅ | ❌ | ❌ | |
| Device Language | |||||
| Auth | App Functionality | ✅ | ❌ | ❌ | |
| identifierForVendor | |||||
| Auth | App Functionality | ✅ | ❌ | ❌ |
Health and Fitness
No data is collected
Financial Info
No data is collected
Location
No data is collected
Sensitive Info
No data is collected
Contacts
No data is collected
Browsing History
No data is collected
Search History
No data is collected
Diagnostics
No data is collected
Some SDKs such as AWSPinpoint, AWSMobileClient, and AWSKinesis persist data to the local device. Some of that data is automatically removed when a user uninstalls the app from the device.
The AWS SDK for iOS stores auth information in the local system keychain, which does not guarantee any particular behavior around whether data is removed when an app is uninstalled.
Deciding on when to clear this auth information is not something that the SDK can do in a generic way, so App developers should decide when to clear the data by signing out. One strategy for accomplishing this would be to use UserDefaults to detect whether or not the app is launching for the first time, and invoking AWSMobileClient.signOut() if the app has not been launched before.