Privacy Policy for Baqiyat

Last updated: July 18, 2026

The Baqiyat app team (“we,” “us,” or “our”) respects the privacy of users of the Baqiyat application. This policy explains what information the app processes and how it is used and retained.

1. Publisher and contact information

Publisher: the Baqiyat app team
Privacy and support email: qurbahapp@gmail.com

2. Information stored locally

Baqiyat stores only on the user’s device the settings and preferences required for its operation. Depending on the features used, these may include prayer-time and calculation settings, a city or location entered by the user, notification settings, bookmarks, reading position and notes, adhkar progress, the selected reciter, and scheduled reminder times. This information is not sent to our servers, and we do not create a user profile.

Users can delete this information by clearing the app’s data in the device settings or by uninstalling the app.

3. Location

Location is entirely optional. A user can select their city manually from an in-app list without granting any location permission. If the user taps “Use my location,” the app requests location permission, then reads the device coordinates and matches them to the nearest city from a city database bundled inside the app (with no network call), and uses them to compute prayer times and the qibla direction on the device. The user’s coordinates are not sent to our servers or to any third party, and are stored only within the app’s file on the device.

4. Quran audio from EveryAyah and MP3Quran

When a user chooses to play a recitation, the app connects over HTTPS to the audio source to request the selected file: EveryAyah at https://everyayah.com for ayah-by-ayah mushaf recitation, and MP3Quran servers at mp3quran.net for the full-surah listening page. As an inherent part of that network connection, the source server may receive the user’s IP address, the requested file path—which may indicate the selected reciter, surah, or ayah—the time of the request, and ordinary technical connection or device information.

We do not operate these servers and do not receive their logs. The processing and retention of that information are governed by each operator’s practices. Network audio playback is optional, and the app’s local features can be used without it. Baqiyat does not use these requests for advertising, profiling, or selling data.

5. App updates via Expo (EAS Update)

Baqiyat uses Expo’s over-the-air update service (EAS Update) to deliver software improvements without waiting for a full store update. When the app launches, it connects over HTTPS to the update server at https://u.expo.dev to check whether a newer version is available. As an inherent part of that connection, the Expo server receives: the device operating system type and version, the app version and runtime version, a randomly generated installation identifier that the library creates at install time and that is not tied to the user’s identity or account, and ordinary technical connection information such as the IP address. This data is used for a single purpose—selecting the correct update for the device—and is not used for advertising or profiling. Its processing is governed by Expo’s privacy policy at https://expo.dev/privacy.

6. Permissions

• Notifications: to show prayer and adhkar reminders selected by the user.
• Exact alarm scheduling (Android): to deliver selected reminders at the requested time as closely as the system and device settings allow.
• Location (optional): requested only when the user taps “Use my location” instead of picking a city; used on the device to compute prayer times and the qibla, and not sent to any server.
• Internet access: to request recitation files when the user plays audio, and to check for app updates via Expo.

These permissions do not give us access to the user’s accounts, contacts, photos, or messages.

6b. Crash reports (Sentry)

If the app encounters a technical failure, a crash report is sent over HTTPS to the Sentry diagnostics service so we can fix the defect. The report contains technical information only: device model and operating-system version, app version, the error stack trace and time of occurrence, and the IP address as an inherent part of the network connection. It does not contain the user’s name, email, location, or what they read or listen to; we enable no performance tracing, screenshots, or session replay, and no profile is built from it. Processing is governed by Sentry’s privacy policy at https://sentry.io/privacy/.

7. Accounts, advertising, purchases, and analytics

The app does not require an account or sign-in. It does not display advertisements, offer in-app purchases, or sell user data. We do not use analytics, tracking, or advertising SDKs. The only external connections are: streaming recitations from EveryAyah and MP3Quran, checking for updates via Expo, and technical crash reports to Sentry — all described above with their technical limits.

8. Data sharing

We do not operate servers that collect user data to share. The only external connections are with EveryAyah and MP3Quran (when the user plays audio), with Expo (to check for updates), and with Sentry (when a technical failure occurs), each to the technical extent described in its section. We may disclose information if required by law; however, we do not hold server-side app usage data to disclose.

9. Retention and deletion

Local data remains on the user’s device until the user clears the app’s data or uninstalls it. We do not retain a server-side copy. Any request logs that may be created by the audio-source operators or Expo, and crash reports held by Sentry, are subject to each operator’s practices; Sentry deletes crash reports automatically after its stated retention period.

10. Security

The app uses HTTPS for all of its external connections. We minimize requested information and keep core functionality local. Nevertheless, no electronic transmission or storage method can guarantee absolute security.

11. Children

The app is a general religious reference and is not specifically designed for children. We do not intentionally request personal information from children or other users. If the target audience changes or a feature that collects data is added, we will update this policy and the store declarations before releasing that change.

12. Changes to this policy

We may update this policy when app features or applicable requirements change. We will publish the new version at this URL and revise the “Last updated” date.

13. Contact us

For privacy questions, contact us at: qurbahapp@gmail.com.