Measuring privacy risk and implied consent in app permissions

• Know the android app permissions better.
• Capability of app permissions → Hidden infrastructure.
• Know the privacy risks from the policies.
• Contribute to the discussion of "quantifying privacy".

• Every application must have an AndroidManifest.xml file in its root directory.
• < uses-permission /> is when your application is seeking the user's permission to use some feature.
• < permission /> is when your application is requiring other apps to seek the user's permission to use some feature of yours.

1. < uses-permission-sdk-23> and < uses-sdk>
2. < path-permission>
3. < permission-group>
4. < permission-tree>
5. < grant-uri-permission>
6. < uses-library>
7. < uses-feature>
8. Many more ……

        npm install google-play-scraper
        
        

       
       #  search.js
        var gplay = require('google-play-scraper');
        gplay.search({term: "facebook",num: 2
        }).then(console.log, console.log);
    

       

       
       #  detail.js
        var gplay = require('google-play-scraper'); 
        gplay.app({appId: 'com.facebook.orca'}).then(console.log);
    

       

       
       #  permission.js 
        var gplay = require('google-play-scraper'); 
        gplay.permissions({appId: "com.facebook.orca"}).then(console.log);
        

    

Just the battery permission.
NO GPS or any ther location permission needed!

What can just the battery statistics reveal?

Solely the list of apps.
and no further information!

What if someone knows which apps you use?

K. Fawaz et.al USENIX 2015, "Anatomization and Protection of Mobile Apps’ Location Privacy Threats"

Activity Time

• Open Settings. ✓
• Click on Apps. ✓
• Choose your favourite app. ✓
• Click on Permissions. ✓
• Tweak the permissions as per your privacy needs. ✓