Permissions.
Featured
Here is an explanation of the scariest permissions needed on the BackCountry Navigator PRO app.
Scariest Permissions Explained:
READ SENSITIVE LOG DATA: *If* you choose to send us a log to help us diagnose a problem, it will have a rather boring list of errors or debug messages from other apps as well.
MODIFY/DELETE STORAGE CONTENTS: We create modify and delete files under the /bcnav directory on your storage card. We don't erase it.
PREVENT DEVICE FROM SLEEPING: Only when you are recording a track or actively downloading.
READ PHONE STATE AND IDENTITY. We generate a unique id for an installation as required for our timed demo and certain ad networks. We do not care about your phone number or who you call.
NETWORK STATE: Knowing what, if any, internet access you have affects preview
-
There is some confusion about why PRO would need READ_PHONE_STATE when it does not show ads. WE DO NOT HAVE NOR PLAN ANY ADS IN THE PAID VERSION.
PUBLISHER means you put ads in your app that point to other apps.
ADVERTISER means you put ads in other apps that point to your app.
The PRO version is not a PUBLISHER.
Ad networks require us to have the READ_PHONE_STATE permission in order to be an ADVERTISER.
Whether that makes sense or seems fair, that is what the ad networks require.
See one example here:
When another app advertises me, the link goes through the Android Market, and they don't know if the install actually happened unless they verify it inside my app.
I can think of other ways to do what they are doing that does not require this permission, but nonetheless, I am unlikely to change their policies.
0 -
Permissions in Android are more broad than they should be.
In the end it comes down to whether you trust me or the app.
If you don't, my explanations won't help.
0
Please sign in to leave a comment.
Comments
2 comments