- Introduction to mobile permissions
- Getting started with iubenda
- Android permissions in particular
- iOS permissions in particular
- App store Integration tips
1. Introduction to mobile permissions
Since iubenda is platform agnostic, the mobile permissions service describes mobile permissions in general and therefore also has permissions coming from the iOS world like HomeKit, Reminder, Motion Sensors etc. This is also useful if you create an app on both platforms.
2. Getting started with iubenda
List the permissions requested by your app
In addition to the other services added above, now’s the time to also enable the clause “Device permissions for Personal Data access”.
3. Android permissions in particular
Android permissions are the ones described in the Android/Google documentation as being “dangerous” permissions. Since requesting sub-permissions like GET_ACCOUNTS is part of the granted group permission like CONTACTS, that’s what our disclosure focuses on.
There is one exception to the rule here: You will find 4 different location disclosures with self-explanatory titles:
- Precise location permission (continuous)
- Precise location permission (non-continuous)
- Approximate location permission (continuous)
- Approximate location permission (non-continuous)
4. iOS permissions in particular
For iOS permissions you can use the same disclosures as above found under 3) Android, in addition to these Apple has certain permissions that aren’t currently part of Android:
- Reminders permission
- HomeKit permission
- Motion sensors permission
- Bluetooth sharing permission
- Social media accounts permission
- add the link to the policy also to the Play Store page and if you have one, to the marketing website.
For further details on privacy policies for Android/iOS apps on the app stores and its requirements, please refer to our guides here: