Summary

MAAB does not require a user account and does not operate a developer-controlled backend that stores your name, worship history, or Quran, adhkar, or memorization progress. Most settings and progress stay locally on your device. Some online features send only the data needed to fulfill a request to the content providers or platform services described below.

Location

After you grant permission, MAAB may access precise location while the app is in use to calculate prayer times, determine Qibla direction, and improve the displayed area name. MAAB does not request background-location permission.

Prayer-time calculation is performed locally in the app. To turn coordinates into a place name, the operating system may pass coordinates to its geocoding/location service or provider depending on the device and platform. MAAB may locally cache the latest coordinates and location label to reduce repeated requests and recalculate when needed.

Photos and sharing

You may choose a photo through the system photo picker to use as the background of an Islamic-event sharing card. MAAB processes the selected image locally and does not upload it to a MAAB-operated server.

The image or generated sharing card leaves your device only when you explicitly choose to share it through another app or service; data you send is then governed by the privacy practices of the destination you chose.

Notifications and alarms

You can enable or disable prayer, Quran, adhkar, hadith, Islamic-event, and custom reminders. Notification preferences are stored locally on your device.

On Android, MAAB may use the system “Alarms & reminders” access to schedule an exact alarm that starts adhan at the calculated prayer time. System, battery, or notification settings may affect delivery timing; MAAB does not send the contents of your notifications to a MAAB-operated server.

Third-party services and search

Some features contact external services when you use them. Quran search sends the search text to AlQuran Cloud to perform the search. Reciter, recitation, and audio resources may be requested from Quran.com and MP3Quran. Islamic-calendar data may be requested from AlAdhan. Some hadith data is loaded from files hosted through jsDelivr.

When these requests are made, the provider may receive your IP address and ordinary network/request metadata, and may receive the search text when you use a search feature. MAAB does not send your optional display name, prayer history, or Quran, memorization, or adhkar progress to these content providers. Third-party processing is governed by each provider’s own privacy practices.

Local data

MAAB may locally store an optional display name, app settings, notification preferences, cached coordinates and location label, prayer-time data, Quran reading progress, bookmarks and statistics, Wird and memorization plans/results, adhkar and hadith progress, prayer tracking, recitation preferences/listening history, and recitation files you choose to download.

This data is used to provide app features on your device. Some temporary data, such as caches and prayer-time data, may be refreshed or replaced automatically. This release does not provide MAAB-operated cloud synchronization.

Advertising and tracking

The current release does not include an advertising network, does not use the advertising identifier for targeting, does not sell personal information, and does not use behavioral tracking across apps or websites.

Data security

MAAB minimizes data transmission to what is needed for the requested feature. The direct API endpoints configured in the app use HTTPS, and local data is kept inside app storage managed by the operating system.

MAAB does not ask for passwords or payment information. We cannot control the retention or security practices of external content providers or platform services, so their own policies apply to data they receive.

Crash reports and diagnostics

Sending crash reports to Sentry is disabled in the current MAAB release unless a future build is configured with a valid service key and the user explicitly opts in.

If this feature is enabled in a future release, it is designed to send only limited technical data such as app version, error category, and sanitized stack traces, excluding name, location, worship history, memorization scores, notification contents, and search queries. We will update this policy and store disclosures if the actual behavior changes.

Retention, deletion, and backup

MAAB does not provide user accounts and does not maintain a centralized personal-data database. You can remove local app data using any deletion controls available in the app, by clearing the app’s data in system settings, or by uninstalling the app.

Depending on your Android or iOS backup/device-transfer settings, the operating system may include some app data in its own backup or transfer services. MAAB does not operate those services and cannot guarantee whether data will be backed up or restored. External providers may retain technical logs under their own policies.

If you contact us by email, we receive your email address and the message and attachments you choose to send. We use them only to respond to support or legal inquiries and retain them only as long as reasonably needed for that purpose or applicable legal obligations.

Children

MAAB does not ask children or other users to create an account or directly submit personal information to the developer inside the app. If the target audience changes, or account features or new services involving children’s data are added, the app, this policy, and store disclosures will be updated before those features are used.

Changes and contact

We may update this policy when features, service providers, or data-handling practices change. The latest revision date appears at the top of this page.

App: MAAB — Quran & Daily Worship (مآب — قرآن، صلاة وأذكار). For privacy or legal-support inquiries: youssifhany2222@gmail.com