Privacy Policy
1. Introduction
SA Mobile Labs ("we," "our," or "us") operates the Salat mobile application for Android (the "App"). This Privacy Policy explains how information is collected, used, stored, and disclosed when you install and use the App, as well as the choices and privacy rights available to you under applicable data protection laws, including the EU/UK General Data Protection Regulation (GDPR), the California Consumer Privacy Act (CCPA/CPRA), and Google Play Developer Program Policies.
By downloading or using the App, you agree to the practices described in this Privacy Policy.
2. Information We Collect and How We Use It
Salat does not require you to register an account, log in, or provide your email address, phone number, or real identity to use any feature of the App.
2.1 Information Stored Locally on Your Device
The following preferences and usage records are stored locally within your Android device's private application storage (using Android Jetpack DataStore and local SQLite databases) and are never transmitted to any server operated by SA Mobile Labs:
- Display Name: An optional first or display name you may enter during onboarding to personalize your in-app greeting.
- Prayer Calculation Settings: Your selected calculation authority (e.g., Muslim World League, ISNA, Umm al-Qura), juristic method (Shafi'i or Hanafi), high-latitude rule, and Hijri calendar adjustment.
- Prayer Logs and Notification Preferences: Daily prayer tracking records and per-prayer Azan/notification alarm toggles.
- Quran and Hadith Activity: Your last-read Surah and Ayah, preferred Quran audio reciter, and selected Hadith translation language.
2.2 Location Information (ACCESS_FINE_LOCATION & ACCESS_COARSE_LOCATION)
Islamic prayer times and Qibla direction depend on geographic coordinates. When you grant location permission to the App, your device's latitude and longitude are used strictly for the following purposes:
- Prayer Time Calculation & Qibla Direction: Coordinates are processed locally on your device using an offline astronomical calculation library to compute daily prayer times (Fajr, Sunrise, Dhuhr, Asr, Maghrib, and Isha) and the compass bearing toward the Kaaba in Makkah.
- City & Country Display: Coordinates are passed to the Android system geocoder to display your current city and country name on the home screen.
- Nearby Mosques Search: When you open the Sacred Places (Mosques) feature, your coordinates are sent over an encrypted HTTPS connection to query nearby mosques in your area via Google Places API and OpenStreetMap Overpass API.
- Daily Alarm Scheduling: Your most recent coordinates are saved locally on your device so background tasks can recalculate the next day's prayer times and schedule alarms automatically at midnight.
We do not maintain any proprietary server that tracks, stores, or profiles your location history. You can revoke location access at any time through your Android device settings (Settings → Apps → Salat → Permissions → Location).
2.3 Device Permissions and Hardware Sensors
- Motion & Compass Sensors (Magnetometer and Accelerometer): Used in real time only while viewing the Qibla Compass screen to orient the compass needle and detect magnetic interference. Sensor data is never recorded or transmitted off your device.
- Notifications & Exact Alarms (
POST_NOTIFICATIONS,SCHEDULE_EXACT_ALARM,RECEIVE_BOOT_COMPLETED,REQUEST_IGNORE_BATTERY_OPTIMIZATIONS): Used solely to deliver timely prayer notifications and re-arm scheduled alarms after a device reboot or app update. - Storage Permission on Older Android Versions (
WRITE_EXTERNAL_STORAGE, API 28 and below): On Android 8.0 to 9.0, storage permission is requested only when you tap the "Save" button to save a shareable Hadith image card into your device'sPictures/Salatfolder. On Android 10 and above, images are saved without storage permission using Android Scoped Storage (MediaStore). The App never reads or accesses your personal photos or files.
3. Third-Party Services and SDKs
The App integrates third-party Software Development Kits (SDKs) and content APIs to provide core functionality, diagnose crashes, and display advertisements. These third-party providers may collect and process limited device information as governed by their respective privacy policies:
| Service / SDK | Provider | Data Collected / Processed | Purpose | Privacy Policy |
|---|---|---|---|---|
| Google AdMob & User Messaging Platform (UMP) | Google LLC | Advertising ID (AAID), IP address (coarse location), device information, ad interaction data, consent status | Displaying Banner, Native, Interstitial, and App Open ads; frequency capping; managing GDPR/CCPA consent | Google Privacy Policy |
| Firebase Crashlytics | Google LLC | Crash stack traces, device model, OS version, Crashlytics Installation UUID | Detecting and fixing application crashes and stability issues | Firebase Privacy |
| Firebase Analytics & Remote Config | Google LLC | App instance ID, aggregated screen views, feature interaction events, app version | Understanding aggregated app usage and delivering remote configuration parameters | Firebase Privacy |
| Google Play Services Location & Places API | Google LLC | Geographic coordinates, GPS/network signals | Resolving device location and finding nearby mosques | Google Privacy Policy |
| OpenStreetMap Overpass API & Content CDNs | OpenStreetMap Foundation / Islamic Network / jsDelivr | Standard HTTP request headers, IP address, search coordinates | Querying nearby mosques, streaming Quran audio recitations, and fetching Hadith translations | OSMF Privacy Policy |
4. Google Play Data Safety Disclosure
In accordance with Google Play Store requirements, the table below summarizes the data types collected and shared through the App and its integrated SDKs:
| Data Category | Collected | Shared with Third Parties | Purpose & Handling |
|---|---|---|---|
| Precise & Approximate Location | Yes | Yes (Places / Overpass API lookup) | Encrypted in transit. Used strictly for App Functionality (Prayer Times, Qibla Compass, Nearby Mosques). |
| Crash Logs & Diagnostics | Yes | Yes (Firebase Crashlytics) | Encrypted in transit. Used for Analytics and App Stability. |
| App Interactions | Yes | Yes (Firebase Analytics) | Encrypted in transit. Used for aggregated Analytics. |
| Device or Other IDs (Advertising ID) | Yes | Yes (Google AdMob & Firebase) | Encrypted in transit. Used for Advertising/Marketing, Analytics, and Fraud Prevention. |
| Personal Identifiers (Name, Email, Phone, Contacts) | No | No | Not collected or shared. Any optional display name entered in the App remains exclusively on your device. |
5. Advertising and Your Choices
We use Google AdMob to display advertisements within the App. For users in the European Economic Area (EEA), the United Kingdom, and Switzerland, we use Google's User Messaging Platform (UMP) SDK to request your consent prior to serving personalized ads.
You can opt out of personalized advertising or delete your Google Advertising ID at any time in your Android device settings by navigating to Settings → Google → All services → Ads and selecting Delete advertising ID or Opt out of Ads Personalization.
6. Legal Bases for Processing (EEA / UK Users)
If you reside in the European Economic Area or the United Kingdom, we process your information under the following legal bases under the GDPR:
- Performance of a Service (Article 6(1)(b)): Processing your device location (when granted) to compute prayer times, Qibla direction, and nearby mosques.
- Consent (Article 6(1)(a)): Accessing optional runtime device permissions (Location, Notifications) and serving personalized advertisements via the Google UMP consent dialog. You may withdraw your consent at any time.
- Legitimate Interests (Article 6(1)(f)): Monitoring application stability and crash diagnostics via Firebase Crashlytics, analyzing aggregated usage metrics, and displaying non-personalized advertisements.
7. Data Retention and Deletion Rights (GDPR & CCPA/CPRA)
- Deleting On-Device Data: Because we do not maintain user accounts or store personal profiles on external servers, all personal settings and prayer logs reside locally on your device. You can permanently delete all local data at any time by going to Android Settings → Apps → Salat → Storage & cache → Clear storage, or by uninstalling the App.
- Third-Party Diagnostic & Analytics Data: Crash logs and analytics identifiers collected by Google Firebase are retained according to Google's standard retention policies (typically 90 days for Crashlytics data and up to 14 months for Analytics data) and then automatically deleted.
- California Privacy Rights (CCPA/CPRA): We do not sell your personal information. To opt out of the sharing of device advertising identifiers with Google AdMob for cross-context behavioral advertising, you may delete or reset your Advertising ID in your Android settings as described in Section 5.
8. Data Security
All network communications between the App and external endpoints (including Google AdMob, Firebase, Google Places API, Hadith API, and Quran Audio CDNs) are encrypted in transit using HTTPS / Transport Layer Security (TLS).
9. Children's Privacy
The App is intended for general audiences aged 13 and older (or the applicable minimum age of digital consent in your country). We do not knowingly collect personal information from children under the age of 13. If you are a parent or guardian and believe a child under 13 has provided personal information to us, please contact us at the email address below so we can take appropriate action.
10. Changes to This Privacy Policy
We may update this Privacy Policy from time to time to reflect changes in the App or applicable laws. Any updates will be posted on this page with an updated "Last Updated" date.
11. Contact Us
If you have any questions, concerns, or requests regarding this Privacy Policy or our data practices, please contact us at:
Developer / Publisher: SA Mobile Labs
Application: Salat
Email: samobilelabs@gmail.com