Privacy policy

1. About this policy

Prayer Time Reminders lets you create personal reminders linked to prayer times and provides prayer-time calculations, Quran content, a Qibla finder and an Islamic calendar. This policy explains how information is handled by the app and its website.

Developer / data controller: Syed Talha Ali
Privacy contact: prayertimeremindersteam@gmail.com
Effective date: September 18, 2026

The current app does not require you to create a Prayer Time Reminders account. Third-party services may still use installation or purchase identifiers. This policy does not replace the privacy policies of those services.

2. Information we handle

Your reminders and preferences

The app stores reminder titles, reminder text, selected prayers, calculation method, madhab, theme preference and onboarding status on your device. It also keeps local caches and scheduling information so it can calculate prayer times and prepare upcoming notifications. The app does not provide a developer-operated cloud backup or sync feature for reminder text. Your device’s own backup and restore settings may separately affect app data.

Your notes and prayer preferences may reveal personal information, including religious practices. Please avoid including information you would not want displayed in a notification.

Location and direction

With your permission, the app obtains latitude and longitude to calculate prayer times and the Qibla direction. The location accuracy depends on your device and permission choices. Coordinates are cached locally and used for on-device calculations; the app does not send these coordinates to a prayer-time API. The Qibla feature also uses device heading information.

The app requests foreground location access, not continuous background location tracking. Background reminder refresh can use previously saved location data. Advertising services may separately infer approximate location from your IP address.

Notifications

The app asks for permission to display notifications. Personal reminder notifications are scheduled on your device, and their text is supplied to the operating system for display. Depending on your device settings, this text may appear on the lock screen or connected devices.

The app also registers with Expo’s push notification service, which involves a push token and app/device registration information. This is separate from locally scheduled reminders. Push services process registration information and, when a remote push is sent, its notification payload for delivery.

Push notification registration

The app stores an Expo push token and its last-updated timestamp in Google Firebase / Cloud Firestore so remote notifications can be sent to your installation. A locally stored document identifier lets the app update the same registration. The current app does not write background-scheduler diagnostics, reminder text or coordinates to Firestore.

Purchases and support

When Premium is available, the app store processes payment. RevenueCat helps validate purchases, restore subscriptions and determine Premium access using app-user identifiers, transaction information and subscription status. We do not receive your full payment-card details through the app. Settings offers a Copy Support ID button that copies your current RevenueCat App User ID to your device clipboard when you tap it. You can include it when contacting us about purchases or privacy requests; copying does not send a support message. This identifier may change after reinstallation. If you contact us, we receive the contact details and information you choose to include in your message. Support email is handled through Gmail, subject to Google’s privacy policy.

3. External services

Google AdMob

The free experience includes banner advertising through Google Mobile Ads / AdMob. The SDK can collect IP addresses, device or account identifiers, ad and app interactions, and diagnostic data for advertising, measurement and fraud prevention. An IP address can indicate approximate location. The current banner requests non-personalized ads; this does not mean no data is collected or that consent is unnecessary.

Review Google’s privacy policy and how Google uses information from apps that use its services. Premium removes banner ads, but other services described here can still operate. The app waits for a confirmed Free subscription and Google’s consent eligibility before requesting a banner. If subscription status cannot be checked, banners remain disabled.

The Android app uses Google’s User Messaging Platform to check whether an advertising consent message is needed. Where required by the configured regional messages, Free users can consent, refuse consent or manage options. Refusing consent does not prevent access to prayer tools or reminders. When Google requires access to privacy options, Settings includes Advertising privacy > Privacy choices to review or change those choices. This entry can also be available to Premium users. Consent choices are managed by Google’s SDK and checked again when the app starts. The ads available depend on those choices and Google’s eligibility checks.

Before release: verify the implemented Android consent flow, privacy choices and Premium ad gating on a rebuilt device installation. Confirm regional targeting in AdMob. iOS advertising and purchases remain unconfigured.

RevenueCat and app stores

RevenueCat and the store supporting a purchase process subscription information to provide and restore paid features. The current purchase integration is configured for Android. See RevenueCat’s privacy policy and the privacy information provided by your app store.

Firebase and Expo

Google Firebase / Cloud Firestore stores the push notification registration described above, and Expo supports push registration and remote push delivery. Network requests also expose connection information, such as IP addresses, to the receiving services. See Firebase privacy information and Expo’s privacy policy.

Quran content and audio

The app requests Quran text and surah information from Quran API. Recitation audio is loaded from the provider URLs returned by that service when you play it. Content hosts receive network information, including your IP address and the requested content, which may identify the verse or recitation you access. A daily verse is cached locally.

Information may also be disclosed where legally required or necessary to respond to lawful requests and protect rights or security. We do not operate a marketplace for your reminder text. Advertising-related sharing is described above and must be assessed under the laws that apply to the final release.

4. Your choices

• Reminders: edit or delete a reminder in the app. The app updates its upcoming schedule after changes.
• Permissions: change location and notification permissions in your device settings. Disabling permissions may prevent accurate updates or reminder delivery. Revoking location permission does not itself erase an existing local cache.
• Notification privacy: use your device settings to hide lock-screen notification content.
• Subscriptions: manage or cancel through the app store used to subscribe. Deleting the app does not cancel a subscription.
• Advertising identifiers: your device may offer controls to reset, delete or limit use of advertising identifiers. Non-personalized ads can still involve data processing.
• Privacy requests: depending on your location, you may have rights to access, correct, delete or restrict use of personal information, request a copy, object to processing, or withdraw consent where processing relies on it. Contact us using the details below. We may need information to verify and locate a request, and some records may need to be retained for legal reasons. You may also contact your local data-protection authority.

How to make a privacy request

Email prayertimeremindersteam@gmail.com and describe what you would like us to do. For example, you can ask what personal information we hold about you, request a copy or correction, ask us to delete support correspondence or your RevenueCat customer record, or ask for help understanding your advertising consent choices. You do not need to create an app account to make a request.

For a request about previous support messages, use the email address you used to contact us where possible. For purchase-related requests, you can include your current Support ID from Settings > Support > Copy Support ID. This helps us locate a RevenueCat record, but the Support ID alone is not proof of ownership. You can still contact us if you cannot access it.

Before disclosing or deleting personal information, we may ask for only the additional information reasonably needed to locate the records and verify that you are entitled to make the request. Please do not send passwords, full payment-card details or unrelated sensitive information. We will explain any verification information we need.

We will review your request and respond within the time limits required by applicable law. If we cannot locate a record, cannot verify the request, or must retain certain information for legal reasons, we will explain the outcome and any available next steps, except where the law prevents us from doing so. Where a permitted extension is needed, we will notify you as required by law. You may raise concerns with us or your local data-protection authority.

Requests cover information we hold or control. Reminder text stored only on your device must be managed through the app or your device settings; we cannot remotely access or erase it. Deleting a RevenueCat record does not cancel your subscription or erase records independently held by Google Play or Apple. See Retention and deletion for these limits and our support-message retention period.

Before release: confirm applicable regional disclosures, legal bases and any required opt-out mechanisms against the countries where the app will be offered.

5. Retention and deletion

Local reminder data remains on the device until it is deleted or app storage is cleared. Uninstalling the app normally removes its local storage, subject to operating-system backup and restore behaviour. Cached data may be replaced when refreshed; a cache becoming too old to use does not necessarily erase it immediately.

Deleting a local reminder does not delete purchase records or push notification registrations held by external services. Provider retention and legal obligations may apply independently. There is no user-account deletion flow because the app does not currently offer account creation.

To request deletion of information we can identify, contact prayertimeremindersteam@gmail.com. Please describe the request without sending passwords or full payment details. Push registrations are associated with an app installation rather than an email account, so additional information may be needed to locate a registration.

The app replaces a stored token when it refreshes and attempts to remove the registration when it detects notification permission is no longer granted. Removal requires a successful connection to Firestore. Uninstalling the app does not itself delete this server record; stale registrations are automatically cleaned up after 90 days without an update. Deletion runs through a background cleanup process rather than immediately at the 90-day mark.

For purchase-related privacy requests, contact prayertimeremindersteam@gmail.com. After verifying the request and identifying the relevant customer record, we use RevenueCat’s customer-deletion process to remove the record we manage, subject to applicable legal obligations. Deleting a RevenueCat customer does not cancel a Google Play or Apple App Store subscription or erase records independently held by the store. Subscription cancellation is handled separately through the store. RevenueCat’s own retention practices are described in its policy linked below.

Support messages are handled in Gmail. We retain support correspondence while an issue is open and delete it 12 months after resolution, unless specific messages must be retained longer for an ongoing dispute or a legal obligation. Any such messages are deleted when that need ends. See Google’s explanation of Gmail message deletion. Firebase processing is described in Firebase’s privacy and security information; our stale-token cleanup period is 90 days without an update. RevenueCat describes its retention and deletion practices in its official privacy policy, including retention needed for legal obligations, disputes and agreements. These provider policies do not specify all of our own retention and deletion practices.

6. Security and international processing

No app, device or internet service can guarantee absolute security. Protect access to your device and consider whether reminder text is suitable for display in notifications. The local app storage is not presented as an encrypted vault.

Service providers may process information outside your country. Their policies explain their processing locations and safeguards. [CONFIRM APPLICABLE CROSS-BORDER SAFEGUARDS AND DEVELOPER SECURITY PRACTICES BEFORE PUBLICATION].

7. Children

Prayer Time Reminders is intended for teenagers and adults and is not specifically designed for children. Younger children are not the intended audience.

The app does not ask users to provide their age or date of birth. It does not use an age-verification flow to identify whether a user is a child.

[VERIFY STORE AGE-GROUP DECLARATIONS AND REGIONAL REQUIREMENTS FOR TEEN USERS BEFORE PUBLICATION]. Align this section with the store’s target-audience declaration and the advertising configuration. Do not assume the app is child-directed or excludes children solely because it is a prayer app.

If you believe a child has provided personal information that should not have been collected, contact prayertimeremindersteam@gmail.com so the request can be reviewed.

8. This website

The landing page’s interactive reminder preview runs in your browser’s memory. It does not save your text, send it to us, request notification permission or create an actual reminder. The page does not include analytics, advertising scripts, third-party fonts or a mailing-list form.

This website is hosted by Cloudflare, Inc. using Cloudflare Workers. Cloudflare processes connection and request information, which may include your IP address, traffic routing information and other technical information, to deliver and protect the website. Workers Observability is disabled for this website deployment. We do not enable stored Workers Logs through that feature or configure separate exports of website logs to other services. Cloudflare may still process operational and security information to provide its services. See Cloudflare’s privacy policy for its processing, international transfers and retention practices. Cloudflare describes retention based on the purposes of processing and legal obligations rather than one fixed period for all data. Followed external links are subject to the destination service’s practices.

9. Policy updates

This policy may be updated when features, providers or data practices change. The effective date will identify the published version. Material changes will be communicated as required by applicable law. The effective date entered in this draft is September 18, 2026. This document remains a draft pending completion and review.