Sota Permissions Explanation

Last updated: May 21, 2026

This document explains why Sota requests sensitive Android permissions. It can be used as source material for Google Play declarations, support answers, and in-app explanations.

Location

Permissions:

Sota uses location for:

Sota does not use GPS for background tracking as part of mesh discovery. Mesh discovery uses nearby radio technologies such as Bluetooth, BLE, Wi-Fi Direct, and Wi-Fi Aware.

Suggested disclosure:

Sota needs Location permission to find nearby devices for offline communication over Bluetooth/Wi-Fi and to let you send your location when you choose that feature. Sota does not use this permission for background GPS tracking.

Bluetooth and Nearby Wi-Fi

Permissions:

Sota uses these permissions for nearby communication, peer discovery, mesh routing, offline messaging, nearby voice paths, and media transfer when internet access is unavailable or unreliable.

This is core Sota functionality. Without nearby device discovery, Sota cannot reliably provide its offline messenger purpose.

Camera

Permission:

Sota uses camera access for:

Microphone

Permission:

Sota uses microphone access for:

Media and Files

Sota uses Android system pickers, the photo picker, document picker, MediaStore write APIs, and user-granted URI access so users can select, preview, send, receive, save, and manage photos, videos, audio, documents, voice messages, stories, and backups.

The Google Play release is intended to avoid broad media-library permissions such as READ_MEDIA_IMAGES, READ_MEDIA_VIDEO, READ_MEDIA_AUDIO, and READ_EXTERNAL_STORAGE. If a future release needs broad media access, the Play Console declaration must tie that access to a verified core messenger media workflow.

Notifications

Permission:

Sota uses notifications for incoming messages, incoming calls, active calls, foreground services, live location sharing, and ongoing communication status.

Full-Screen Intent

Permission:

Sota uses full-screen intent only for incoming voice or video calls so the recipient can answer or decline immediately, including when the phone is locked.

Suggested declaration:

Sota uses full-screen intent only for incoming voice and video calls. Calls are a core communication feature of the app. Without full-screen call UI, users may miss time-sensitive incoming calls when the device is locked or another app is open.

Foreground Services

Permissions:

Sota uses foreground services for user-visible communication features:

These services show notifications and are necessary for real-time communication reliability.

Boot Completed

Permission:

Sota may use this to restore communication readiness after device restart, depending on user settings and Android restrictions.

Wake Lock

Permission:

Sota may briefly wake or keep the device responsive for incoming calls, urgent call UI, active communication, and notification behavior.

Biometrics

Permissions:

Sota uses biometrics for optional app lock, recovery phrase viewing, and security-sensitive settings.