Privacy Policy for AvaSOS
Package: com.avasos.app · Last updated: 15 October 2026
At a Glance
AvaSOS is built around a single unwavering principle: your safety should never compromise your privacy. We do not sell data, do not display advertisements, do not track you in secret, and store your emergency contacts exclusively on your physical device. Location data is only accessed when an active safety feature (Commute Shield, Safe Journey, or Emergency SOS) is intentionally engaged by you.
1. Introduction & Developer Identity
This Privacy Policy governs your use of the mobile application AvaSOS (“the Application”, “the App”), developed and maintained by Md Minaruzzaman Shovon (“we”, “us”, or “our”).
AvaSOS is an offline-ready personal safety companion that enables users to quickly dispatch emergency SOS alerts, share real-time GPS locations with trusted contacts, protect commutes with hands-free shake detection, and monitor safe arrivals via timed watchdog journeys.
By downloading, installing, or using AvaSOS, you agree to the collection, processing, and handling of information as described in this policy. If you do not agree, please do not install or use the Application.
2. Sensitive Android Permissions & Justifications
To deliver emergency lifesaving features, AvaSOS requests specific sensitive Android permissions. Each permission is strictly bounded to its safety utility:
Why we need it: To capture your precise GPS coordinates at the exact moment of an SOS trigger, or while tracking a Safe Journey / Commute session, and generate a clickable Google Maps link (https://maps.google.com/?q=lat,lng) dispatched to your emergency contacts.
Scope: Location is never recorded continuously in the background without an active session. It is only accessed when an alert is running or when you explicitly start Commute Shield or a Journey timer.
Why we need it: Required by Android to run persistent background services (such as CommuteService and LiveShareService). This ensures that shake detection, timed countdowns, and live location updates remain active even when your screen is locked or another app is open.
Transparency: Whenever a foreground service is running, Android displays an ongoing, persistent notification in your notification tray with quick actions (such as “I'm Safe” or “Extend”).
Why we need it: To send emergency SMS distress messages containing your custom alert text and live GPS coordinates directly to your chosen trusted emergency contacts during an emergency SOS or when an unconfirmed journey expires.
Offline-ready: SMS operates directly over cellular networks and functions even when mobile data or internet connections are completely unavailable. SMS carrier fees apply according to your standard mobile plan.
Why we need it: To initiate an automatic or one-tap emergency call to your primary emergency contact or local emergency hotline (e.g. 999 or 911) once the SOS countdown finishes.
Why we need it: Used exclusively to allow you to select emergency contacts directly from your device address book instead of manually typing phone numbers.
Zero Uploads: Selected contacts are stored solely in your local on-device SQLite database (Room). Your address book is never synced to any remote server or third party.
Why we need it: Enables dual-SIM detection on multi-SIM phones so you can designate which SIM card sends the emergency SOS SMS. We do not read or collect your IMSI, IMEI, or call history.
Why we need it: Prevents aggressive Android Doze mode and manufacturer battery savers from putting the safety watchdog service to sleep while you are traveling alone or in transit.
3. Information We Collect and Process
We classify all information handled by AvaSOS into two categories:
A. On-Device Data (Never Leaves Your Phone Without SOS Action)
- Emergency Contacts: Names, phone numbers, and priority ranks of the contacts you choose. Stored strictly in local Room database.
- Custom Alert Messages: The pre-composed text message you choose to send when triggering SOS.
- Journey Watchdog Settings: Destination names, estimated travel durations, check-in reminders, and timer states.
- Commute Preferences: Shake detection sensitivity thresholds and preferred SIM card slot.
B. Transmitted Data (During User-Triggered Emergencies)
- Emergency SOS SMS: Sent directly through your phone's SIM card to your selected emergency contacts.
- Optional Telegram Alert Relay: If you configure AvaSOS to broadcast alerts to a Telegram chat, an encrypted HTTPS request containing your alert message and GPS coordinates is dispatched through our secure Cloudflare Worker server relay (
avasos-server) to the Telegram Bot API. The server does not persist or log your personal identifiable info or message history.
4. Diagnostics, Telemetry & Advertising
AvaSOS is completely ad-free. We do not use Google AdMob, Unity, AppLovin, or any advertising SDKs.
For application stability, we utilize Google Firebase Crashlytics and Firebase Analytics with the following strict privacy constraints:
google_analytics_adid_collection_enabled = false: We explicitly disable collection of Google Advertising ID (Ad ID).google_analytics_ssaid_collection_enabled = false: Android SSAID collection is disabled.- Zero Emergency Tracking: Actual emergency triggers, distress messages, coordinates, contact names, and phone numbers are never sent to analytics.
- Crash Reports: Crashlytics receives anonymized stack traces and device hardware specs (e.g., Android version, device model) solely to troubleshoot bugs and crashes.
5. Data Retention, Security & User Control
Local Storage: Because all sensitive user data resides in local sandbox storage on your Android device, you maintain 100% control over it at all times.
- You can edit or delete emergency contacts directly in the app at any time.
- Clearing app data via Android Settings (
Settings > Apps > AvaSOS > Storage > Clear Storage) permanently deletes all saved contacts and configurations. - Uninstalling AvaSOS permanently purges all local databases and preferences from your device.
Security: All network communications with external endpoints (such as the optional Telegram alert relay) utilize industry-standard Transport Layer Security (TLS 1.3 / HTTPS encryption).
6. Children's Privacy
AvaSOS is designed for general audiences seeking personal safety tools. We do not knowingly collect, harvest, or solicit any personal information from children under the age of 13. If you believe a child has provided personal information to any third party through our application without parental consent, please contact us immediately so we can investigate and assist.
7. Changes to this Privacy Policy
We may revise this Privacy Policy periodically to reflect enhancements in the application, updates in Android OS permission requirements, or regulatory changes. Any modifications will be posted to this page with an updated “Last updated” timestamp. We encourage you to review this page periodically.
8. Contact Information
If you have questions, feedback, or concerns regarding this Privacy Policy or AvaSOS's handling of your data, please contact the developer: