Loading page
About this tool
Weigh cab-app safety features against background location, contacts, microphone and call log access.
The Ride Hailing App Permission Audit separates the safety features you chose from the data collection you did not. Sixteen permissions are weighted by sensitivity, with precise location scored as genuinely core and the harder cases — background location, microphone for in-trip audio recording, contacts for emergency contacts and trip sharing — scored as optional, worth keeping only if you actually use them. Call logs, calendar and Bluetooth scanning have no ride-hailing use at all and score as full exposure.
Open Ride Hailing App Permission Audit on AltFTool — it loads instantly in your browser.
Enter the app in App name (for the report), then answer How do you want to enter permissions? with Checklist or Paste list.
Under Permissions and settings this app currently holds, tick what is granted, or start from Typical cab app, Everything granted or Clear all.
Read the Privacy score out of 100 with its Verdict band, then work through Revoke these first, Worth reviewing and Justified - but know what they see.
Audio recording and trip sharing are scored as optional, not condemned — the point is to choose them deliberately.
Platforms route driver calls through a masked number, so CALL_PHONE and call log access earn no credit.
One unnecessary permission holds the headline verdict at 'Low exposure' however clean the rest looks.
Not for booking or for an ongoing trip — those run in the foreground with a live notification, which 'While using the app' covers. Background location only matters if you want trips tracked with the phone locked and the app closed, so it is a deliberate trade, not a requirement.
It is a real safety feature: the recording is encrypted and only opened if you file a report. The cost is a standing microphone grant, so set the permission to 'Ask every time' or turn the feature on per ride rather than leaving it always on.
So you can pick names from a list — but that means granting the whole address book to store two or three numbers. Deny it and type those numbers manually in the safety settings; the feature works the same way afterwards.
No. Driver calls are routed through a masked number by the platform, so the app never needs your call history. READ_CALL_LOG is a Google Play restricted permission and reveals who you speak to and when, which has nothing to do with booking a ride.