Android Permissions Explained: What Raksha Needs and Why
When you install Raksha, Android asks for several permissions before the app can protect your family. Here is a plain-language explanation of what every permission does — and why it is genuinely needed.
June 1, 2025 · 5 min read
The 6 permissions Raksha requests
Every permission has a single, documented purpose. Here is the full picture at a glance:
Tracks your device even when the app is closed. The core feature.
Takes a silent snapshot when Lost Mode is triggered by you or your family.
Shows the recovery screen on top of the lock screen so finders can contact you.
Sends SOS alerts to your family circle and keeps the background service alive.
Schedules precise health checks so the service doesn't drift or get killed.
Prevents Xiaomi, Samsung, Realme etc. from killing Raksha in the background.
📍 Background Location
Why it's needed: Without background location, Raksha can only update your position while you actively have the app open. The moment you switch to WhatsApp or lock the screen, tracking stops — which defeats the purpose of a safety app.
How it works: Raksha uses a tiered strategy. In normal conditions, it refreshes every few minutes (low battery impact). During an active SOS or Lost Mode, it switches to high-frequency GPS. Your position is only shared with family members you have explicitly added.
📷 Camera
Why it's needed: Raksha's anti-theft snapshot feature silently captures a photo of whoever is holding your stolen phone using the front camera. This is sent to your family circle as evidence.
When it activates: Only when a family member explicitly triggers a snapshot command, or when a configured theft trigger fires (e.g., three failed unlock attempts). It never records video, never streams, and never activates without your family's command.
🖥️ Draw Over Other Apps (Overlay)
Why it's needed: When Lost Mode is active, Raksha shows a recovery screen on top of the lock screen — something like "This phone is lost. Please call +91 98765 43210." Anyone who finds your phone sees it immediately, without unlocking it.
Also used for the SOS confirmation dialog to prevent accidental triggers while your phone is in your pocket.
🔔 Notifications
Why it's needed: Two reasons. First, Android requires any app running a persistent background service to show a foreground notification — without it, Android kills the service. Second, you need to receive SOS alerts, device-offline warnings, and ring/lock confirmations in real time.
You can customise or mute specific notification channels: Settings → Apps → Raksha → Notifications.
⏱️ Exact Alarm (Android 12+)
Why it's needed: Without this, Android can delay Raksha's background checks by up to 15 minutes — meaning your location may stop updating reliably when the screen is off. On Android 11 and below this is granted automatically.
🔋 Battery Optimization Exemption
Why it's needed: This is the single most important setting on Indian phones. Brands like Xiaomi, Motorola, Realme, and Samsung add their own aggressive battery-saving layers that shut down background apps beyond what Android normally allows. Without this exemption, tracking stops after 10–15 minutes of the screen being off.
Granting this does not mean Raksha drains your battery. It means Raksha's small service is allowed to stay alive instead of being force-killed.
What Raksha does NOT access
If a future version of Raksha ever needs a new permission, it will be documented here with the same level of detail. You are always in control.