Snapper Frequently asked questions Required app permissions

Required app permissions

Privacy

Read phone status and identity (READ_PHONE_STATE):

Having permission to read a phone’s status and identity allows the app to read a unique ID (IMEI) associated with the user’s phone. This allows Snapper to block a specific phone from using the Snapper Mobile app if needed.

Approximate location – Network based (ACCESS_COARSE_LOCATION):

*Optional* Add on that allows Snapper to collect analytics of usage of the Snapper app. We aren’t trying to stalk you, but the better we know and understand how you use Snapper and the app the better we can build future releases for you.

Precise location – GPS & Network based (ACCESS_FINE_LOCATION):

[Optional] This add on allows Snapper to collect analytics of usage of the Snapper app. We aren’t trying to stalk you, but the better we know and understand how you use Snapper and the app the better we can build future releases for you.

Read the contents of your USB storage (READ_EXTERNAL_STORAGE):

The app checks your external storage (memory), as our in-app messaging tool has the option to attach a photo to your message.

 

Device Access

Control NFC (NFC):

To access NFC hardware.

Full network access (ACCESS_NETWORK_STATE):

The Snapper Mobile app communicates with Snapper servers through the internet, and data from these servers is needed to read the Snapper card (and to make changes to the card, like topping up).

Org.simalliance.openmobileapi.SMARTCARD (SMARTCARD):

This lets the Snapper app communicate with secure elements, like the Snapper SIM.

View network connections (INTERNET):

To connect to the internet, a user will need to be able to view their network connections (then they will be able to select a network that will allow them to connect to the internet).

Control vibrations (VIBRATE):

The Snapper app uses vibration to notify the user (for example, the app uses vibrations to notify the user that they have increased the top up amount on the top up dial).

Prevent phone from sleeping (WAKE_LOCK):

This keeps the processor from sleeping when a message is received to keep the user aware of events (for example receiving a message from the in-app messaging centre).