QafilaaBack to the ride
LegalPrivacyTermsCookies
SafetyCommunity guidelinesChild safetyReport contentSecurity
Your dataData safetyPermissionsSubprocessorsDelete dataDelete account
HelpSupportContactAccessibility
qafilaa.in/permissions
Every permission we ask for, and the real reason

Permissions

Qafilaa asks for a small number of permissions and each one buys a specific thing. This page says what each is for, what breaks if you refuse it, and how to take it back. The app asks for none of them at install; each is requested in context, the first time it is needed.

Last updated: 20/08/2026
In plain English
  • Location is the only one the app genuinely cannot work without.
  • Background location runs only while a ride is active, and stops when the ride ends.
  • Motion data is read on your phone and never uploaded. Only a resulting alert is.
  • Refusing notifications means a crash alert cannot reach you. Everything else still works.
  • Every one of these can be revoked in your phone's settings, at any time.

Location, while you are using the app

Android
ACCESS_FINE_LOCATION, ACCESS_COARSE_LOCATION
iOS
NSLocationWhenInUseUsageDescription
Why
To put you on the convoy map, measure the gap to the rider ahead, and navigate to the next rally point.
If you refuse
The live map, gap tracking and navigation do not work. Planning a trip still does.

Location, in the background

Android
ACCESS_BACKGROUND_LOCATION, FOREGROUND_SERVICE_LOCATION
iOS
NSLocationAlwaysAndWhenInUseUsageDescription
Why
A rider does not hold their phone. It is in a mount with the screen off, or in a jacket pocket. Without background access your position freezes the moment the screen sleeps, and the crew behind you is riding towards a stale dot.
When it runs
Only while a ride is active. It starts when the ride starts and stops when the ride ends — not when you close the app, and not on a schedule of ours.
If you refuse
You can still ride, but your crew sees your last position from when the screen was last on.

Android shows a persistent notification for the whole time this is running. That notification is not decoration — it is how you can tell, at a glance, that Qafilaa is still publishing your position, and it stops when the ride does.

Battery mode reduces how often your position is published on long straight legs and restores full frequency near passes and rally points, where knowing exactly where the group is matters most.

Motion and fitness

Android
ACTIVITY_RECOGNITION, high-rate sensor access
iOS
NSMotionUsageDescription
Why
Crash detection reads the accelerometer to recognise the signature of a fall. Without it, a fall is just a phone that stopped moving.
Where it is processed
On your device. The samples never leave your phone. Only the resulting alert is sent, and only if the countdown completes.
If you refuse
Automatic crash detection is off. Manual SOS — tap, hold, or flip the phone — still works.

Notifications

Android
POST_NOTIFICATIONS
iOS
User notifications, including critical alerts where granted
Why
An SOS has to reach you on the lock screen, in a mount, at 80 kmph. Rally-point calls, roll-out, and crew signals use the same channel.
If you refuse
You will not be told when another rider needs help. Nothing else changes.

Camera and photos

Android
CAMERA, READ_MEDIA_IMAGES
iOS
NSCameraUsageDescription, NSPhotoLibraryUsageDescription
Why
To set a profile or bike photo, attach a photo to a day note, and scan documents such as your licence, registration, insurance and permits.
What we take
Only the images you pick or capture in that moment. We do not read your photo library, and we do not scan it in the background.
If you refuse
You can use everything else; you just type instead of photographing.

Contacts

Android
READ_CONTACTS
iOS
NSContactsUsageDescription
Why
Only so you can pick an emergency contact from your phonebook instead of typing a number wrong.
What we take
The one contact you choose. We do not upload your address book, and we do not use it to find other riders.
If you refuse
Type the contact in by hand. Nothing else is affected.

An emergency contact is someone else's personal data. Please ask them first — the app makes you confirm that you have. See Privacy Policy, section 4a.

The rest

  • Network and connectivity state — to know whether to send now or queue for later. No prompt; it carries no personal data.
  • Storage — to hold offline maps and your cached trip on the device, so every screen reads from disk first.
  • Wake lock and battery optimisation — so the operating system does not put the ride to sleep under you mid-leg.
  • Boot completed — so an interrupted ride can resume after a phone restart rather than silently ending.

Taking a permission back

Android: Settings → Apps → Qafilaa → Permissions. iOS: Settings → Qafilaa. You can also review what you have granted inside the app, under App permissions, which shows the current state of each and links straight out to the system screen.

Revoking a permission never deletes data we already hold. To remove that, see Delete my data or Delete your account.

What we do not ask for

No microphone, no call log, no SMS, no advertising identifier, no accessibility service, no "all files" access, and no cross-app tracking. There is no advertising or tracking software in Qafilaa at all. If you find a permission in the app that is not on this page, tell us at admin@qafilaa.in and we will either explain it or remove it.

Qafilaa.in · Kolhapur, Maharashtraadmin@qafilaa.in