1. At a glance
You do not need an account or have to provide your name, email address or phone number to use the app. Prayer records, Tasbih counts, package information and preferences are stored on your device. However, the app includes Google advertising and Firebase services, which send some information off your device. Android backup may also apply.
This policy describes Al-Muslim: Daily Essentials’s current data practices. Information used by advertising and Firebase services is separate from the records the app stores locally. The following sections explain both.
2. Data stored on your device
The app stores the following information in its private device storage:
- Selected district: the identifier of the district you choose, used for prayer times, Ramadan timings and Qibla direction.
- Prayer records: the date, prayer name and whether you mark it as prayed or not prayed. Selecting “unmarked” removes the stored record for that prayer. These records may reveal information about your religious practice.
- Tasbih: your current count, so you can continue from it later.
- Preferences and reminders: your theme, occasion reminders, selected prayers and reminder intervals.
- Credits and package information: your credit balance, package start and expiry times, whether a package has previously been activated, and the latest time seen by the app to prevent extending a package by moving the device clock backwards. These are not payment details.
- Calendar data: downloaded Hijri corrections, occasion information and the time of the last successful update.
We do not provide our own account synchronisation or prayer-record upload service. Prayer records are stored in a local Room database, preferences and package information in Jetpack DataStore, and calendar data in a local file.
Android backup
The app permits Android backup. Depending on your device, Android version and backup settings, eligible local files and databases may be backed up through Google or your device’s backup service and restored after reinstallation or on another device. This is separate from an app-operated cloud sync service. Use your device and backup provider’s settings to manage or delete backups. Learn about Android backup.
3. Location and compass sensors
When you tap the location button in the district picker, the app requests permission to access your approximate location. It uses one location reading from Google Play services’ Fused Location Provider to find the nearest district on your device. The app does not write these coordinates to its own files or send them to our own servers. Only the selected district is saved. The app does not continuously track your location or request background location access.
You can select a district manually without granting location permission. Google Play services’ own location processing is governed by Google’s policies and your device settings.
The Qibla compass temporarily uses heading and accuracy readings from your device’s rotation or geomagnetic sensors. The app does not store or upload these sensor readings.
This is separate from location inferred by advertising services: even without location permission, advertising and Analytics services may infer your general region from your IP address.
4. Advertising and Firebase services
Advertising helps support the app. Native ads appear on the Home screen, and you can choose to watch rewarded ads to earn credits. An active package does not remove Home-screen ads. The app includes the following Google services:
On smaller screens, scroll the table sideways to read all columns.
| Service | Information used | Purpose |
|---|---|---|
| Google Mobile Ads / AdMob | IP address and inferred region; available advertising and app-set identifiers; ad impressions, taps and video views; and SDK and app diagnostic information. The information processed may vary with configuration and Google’s controls. | Ad delivery, measurement, analytics and fraud prevention. |
| Google UMP | Whether regional consent is required, and advertising privacy or consent choices and status. | Displaying a consent form where applicable and determining whether ads may be requested. |
| Google Analytics for Firebase | App-instance ID, available advertising ID, sessions, app lifecycle and screen-view events, and approximate region derived from IP addresses. | Understanding app usage and operation. The app does not attach names, email addresses or our own account user IDs to custom Analytics events. |
| Firebase Crashlytics | Crash stack traces, relevant app and device state, installation identifiers and available Analytics breadcrumbs. | Identifying and fixing crashes. Collection is enabled in the release app. |
| Firebase Performance Monitoring | App startup and network request timings, performance and device metadata, IP addresses, and installation or session identifiers. Supporting Firebase Installations, Sessions and Remote Config services also operate. | Understanding performance problems and managing reporting samples. |
| Firebase Cloud Messaging | Messaging registration tokens or installation identifiers, necessary app metadata, and notification interaction events through Analytics. | Delivering app announcements. There is no separate developer-operated token upload backend; Firebase itself processes messaging identifiers. |
This information is sent to Google or Firebase services. Google may act as our service provider for some processing, while advertising data is also handled under Google’s applicable terms and policies. Google Play’s Data safety definitions distinguish qualifying service-provider transfers from other third-party “sharing”; this policy identifies the actual recipients.
Read more: Google Privacy Policy, Google’s use of information for advertising, Firebase privacy and retention, and How Google uses information from partner apps.
5. Other network connections
The app downloads a publicly accessible JSON file hosted on GitHub over HTTPS to obtain Hijri corrections and Islamic occasion information. Updates are scheduled daily, with an additional attempt after startup when the last successful update is old. When offline, the app uses the previous download or bundled data.
The app does not add prayer records, Tasbih counts, your selected district or location coordinates to this request. As part of the connection, GitHub and its delivery infrastructure receive your IP address, requested URL and ordinary request metadata, which they may process under their own policies. See the GitHub Privacy Statement. Where the app is distributed through Google Play, Google’s policies apply to Google Play’s own processing.
6. Device permissions
- Approximate location: to find a district when you request it. Manual district selection does not require this permission.
- Notifications: to show enabled reminders and announcements. You can disable notifications in Android settings.
- Exact alarms and boot events: to deliver scheduled reminders and reschedule them after a device restart or time change.
- Internet and network state: for central data updates, Google advertising, consent and Firebase services.
- Supporting SDK permissions: advertising ID, advertising attribution or topics, messaging, install-referrer and wake-lock permissions are included through Google and Android dependencies.
The app does not request permission to read your contacts, photos, microphone, camera or personal device calendar. Disabling a permission may limit the related feature.
7. Data retention
Device data: preferences and prayer records remain until you change the relevant information or clear the app’s storage. You can reset the Tasbih count. Package expiry does not automatically delete prayer history. The app does not apply a separate automatic, time-based deletion period to these local records.
Backups: Android or manufacturer backup copies may remain under the backup service’s settings and retention rules. Uninstalling the app alone does not guarantee deletion of every backup copy.
Google and Firebase: information is retained under the applicable service policies and account or property settings. Firebase’s published retention guidance states that Crashlytics retains crash information and associated identifiers for 90 days before starting removal from live and backup systems. Performance Monitoring retains IP-associated events for 30 days, and installation-associated and de-identified performance data for 60 days, before starting removal. Messaging installation identifiers require the relevant deletion process. Analytics user and event retention depends on the period configured for the property; advertising retention follows Google’s applicable policies. See Firebase’s current privacy guidance and Analytics data retention.
Hosting and correspondence: GitHub and Cloudflare retain request and security information under their policies. If you contact us, correspondence may be kept for as long as needed to resolve the matter and meet applicable obligations.
8. Your choices and rights
- Select your district manually without location access, or revoke location permission later in Android settings.
- Manage reminders and notifications in the app’s Settings and Android settings.
- Reset your Tasbih count. With an active package, you can edit prayer records or mark them as “unmarked”. You can clear all local app storage through Android even without an active package.
- Delete local records, preferences and credits using Android Settings → Apps → select this app → Storage → Clear storage / Clear data. Menu names vary by device. This may also remove credits and package information.
- Use Android’s advertising ID and advertising privacy controls. A Google UMP consent form may appear in applicable regions. The app currently has no separate Analytics or Performance opt-out switch and no permanently visible button for reopening advertising consent choices.
- Manage or delete backups through the relevant backup account or device settings.
Clearing storage or uninstalling the app does not immediately delete all information previously sent to Google, Firebase or other services. We do not hold an online copy of your local prayer database, so we cannot retrieve or delete that database by email. Contact us below with questions or deletion requests concerning provider-held data; relevant verification and provider processes may be required.
Depending on your location, you may have rights to access, correct or delete information, restrict or object to processing, receive portable data, or withdraw consent. Where consent is required, it must be valid; reading this policy is not consent. Where applicable, processing may also rely on legitimate interests in providing, securing and maintaining the app, or another lawful basis. Contact us to exercise your rights. You may also complain to your local data protection authority where applicable.
9. Children’s privacy
Al-Muslim: Daily Essentials is intended for users aged 10 and above, so its audience may include children. The app does not ask for an account, date of birth or age. Advertising, Analytics and other SDK processing is described in section 4; processing children’s information is also subject to applicable law and Google Play’s age-related requirements.
Children should use the app and its location, notification and advertising choices with a parent or guardian’s guidance. Where applicable law requires parental consent, a child’s information should not be processed without it. Parents or guardians with concerns or deletion requests should contact us. We will address verifiable requests as required by applicable law and the relevant service-provider processes.
10. Security and international processing
The central data URL uses HTTPS. Google’s SDK documentation states that transmitted user information is protected in transit using TLS. Local records are held in Android’s app-private storage. No device, backup, network or online service can be guaranteed completely secure.
Google, GitHub, Cloudflare and their infrastructure may process information outside your country. Where applicable, their data-processing terms, contractual safeguards and lawful transfer arrangements apply. This does not remove your rights under applicable local law.
11. This website and contacting us
This static website has no analytics scripts operated by us, advertising, accounts, cookie-based tracking or forms. Fonts and images are served from this site. Cloudflare Pages hosts the website and may process IP addresses, browser or request metadata and related technical information for security and delivery. See the Cloudflare Privacy Policy.
If you follow a Google Play or other external link, the destination service’s policies apply. If you email us, we use your email address, message and information you provide to respond. Please avoid sending prayer records or other sensitive information unless necessary.
For questions about this policy, your rights or data-deletion requests, contact:
Weblywork
Email: info@weblywork.com
12. Changes to this policy
We may update this policy when the app’s behaviour, service providers or applicable requirements change. Updates will be published on this page with an effective date. Where required, significant changes may need additional notice or consent.