Privacy Policy

1. Controller & Contact

This policy applies to My Prayer Times (“we”, “us”).

2. Data We Process

Depending on what features you use, we may process:

2.1 Location Data

We collect your device's location information to provide core app functionality:

• Precise Location (GPS): Used to calculate accurate prayer times based on your geographical coordinates and to determine the Qibla direction.
• Background Location: If you enable the "Travelling Prayer" feature, we access your location even when the app is closed or not in use to detect when you are travelling and automatically play the travel prayer (Dua-e-Safar).
• Altitude/Elevation: Used to improve prayer time accuracy for users at high elevations.

How we use it: Location data is processed locally on your device and used solely for calculating prayer times, Qibla direction, and detecting travel. We do not sell, share, or transmit your precise location to third parties for advertising or tracking purposes.

Storage: Your last known location is cached locally on your device to provide faster loading of prayer times. It is not transmitted to our servers unless you explicitly enable cloud sync of preferences (which includes your selected city/coordinates, not your real-time GPS).

2.2 Other Data

• Account data: email address, UID, sign-in timestamps (Firebase Authentication)
• Religious tracking data: Qaza counts/history, Tasbeeh/Dhikr counts and stats, reading progress/bookmarks (Quran/Dalail), settings/preferences
• AI chat content: messages you send/receive in the assistant
• Device/app diagnostics: crash reports (see section 5)

We do not sell personal data and we do not run ads.

3. Local Storage vs Cloud Sync

Local-first: by default, your app data is stored locally on your device.

Cloud sync (optional): if you sign in, selected data may be synced to Firebase (Google Cloud) to enable backup and multi-device use.

4. AI Features

If you use the AI assistant, your messages may be sent to a third-party AI provider (currently OpenAI) to generate responses.

If you are signed in, AI chat history may also be stored in Firebase under your account for sync/backup.

5. Crash Reporting

We use Sentry for serious crash/error reporting to improve stability. Crash reports may include technical diagnostics (e.g., device/app version and error details). We do not intentionally include your religious data in crash reports.

6. Bug Reports

If you submit a bug report, it may be stored in Firebase. Please avoid including sensitive personal information in bug report text.

7. Third Parties

• Firebase (Google Cloud): authentication and optional cloud sync/backup
• OpenAI: processing AI assistant messages (if you use AI features)
• Sentry: crash/error reporting

When you visit this website, your device may fetch resources from third-party hosts (e.g., Google Fonts), which may receive your IP address as part of delivering that content.

8. Legal Bases (GDPR)

• Contract (Art. 6(1)(b)): providing the service you request (e.g., account sync/backup)
• Consent (Art. 6(1)(a)): where required for optional features
• Legitimate interests (Art. 6(1)(f)): basic security, fraud prevention, and crash diagnostics

9. Retention

• Local data: stays on your device until you remove it (e.g., uninstall/clear storage)
• Cloud data: stored while your account is active and deleted when you delete your account (subject to limited exceptions such as legal/security logs)

10. Your Rights

You can exercise GDPR rights (access, deletion, portability) via the Account Management page:

• Export: downloads a JSON copy of your cloud data
• Delete: deletes your cloud data and account

For help, contact general@myprayertimes.org.

11. Security

We use access controls and encryption provided by our infrastructure providers (e.g., Firebase) and apply least-access principles to user data.

12. Children

If you are a parent/guardian and believe a child has provided personal information, contact us at general@myprayertimes.org.

13. Changes

We may update this policy from time to time. We will update the effective date above and publish the revised version here.