# How Islamic prayer-time apps differ on privacy, ads, and openness [ All docs ](/docs) May 10, 2026 # How Islamic prayer-time apps differ on privacy, ads, and openness A category-level comparison of how Muslim prayer-time and athkar apps handle data collection, advertising, paywalls, and source transparency. Where Nedaa fits. --- # How Islamic prayer-time apps differ on privacy, ads, and openness Most discussion of Islamic apps treats them as interchangeable: same prayer times, similar Athan, same Hijri calendar. The differences underneath are what matter: what they do with your data, whether they show ads, what they charge, and whether you can audit any of it. This page lays out the dimensions, explains why each one matters, and shows where Nedaa sits. This is a **category** comparison, not a head-to-head. We don’t list competitors by name. The goal is to give you the right questions to ask of any Islamic app you’re considering, including this one. ## The four dimensions ### 1\. Data collection What an app _collects_ and what an app _needs_ are two different things. A prayer-times app needs your location to compute prayer times. It does not need your phone’s advertising ID, your contacts, your install graph, your detailed location history, or a persistent user profile across devices. Yet many apps in the category collect all of those. **Questions to ask:** * Does the app require an account? For what purpose? * Does it collect a precise location, or is low-accuracy enough? * Does its privacy label disclose tracking SDKs, advertising IDs, or data sold to third parties? * Does it store data in a cloud profile, or only locally on your device? **Where Nedaa sits:** No account. No cloud profile. Low-accuracy location only, used locally. No advertising or third-party tracking SDKs. The full surface of what’s collected lives in the iOS Privacy Manifest and is verifiable in the open-source code. ### 2\. Advertising Advertising in religious apps is a different proposition from advertising in a productivity tool or a game. Two distinct concerns: **What gets shown.** Worship asks for presence; ads are designed to break it. An interstitial between Athkar entries, a banner under the Qibla compass, a video before a Quran reader — each one trades a moment of the user’s attention to the highest bidder. Whether this is acceptable inside a worship surface is, ultimately, an aesthetic and ethical judgment users have to make for themselves. Our judgment is that it is not. **What gets collected.** Ad networks pay better when they can target. Targeting requires behavioural data — and a worship app generates uniquely sensitive signals: when you pray, how often, what you read, where you are. That data leaks observance level, denomination, and identity to a chain of brokers the dev no longer fully controls. This is a structural concern, not a comment on any specific app’s intent. **Questions to ask:** * Does the app show banner, interstitial, or video ads? * Are there ads in worship-adjacent surfaces (Quran reader, Athkar list, Qibla)? * Is “remove ads” the upsell to a paid tier? **Where Nedaa sits:** No ads anywhere. No advertising SDKs are bundled in the app. There is no “remove ads” upsell because there’s nothing to remove. ### 3\. Pricing model The category has fragmented across three patterns — free (often ad-supported), freemium with a “Pro” subscription, and one-time-paid. Each is a legitimate way to fund an app, with different tradeoffs. A transparently priced paid app, where the user pays the developer directly for nice-to-have features, is a clean exchange — and often the more sustainable model long-term. **Questions to ask** (so you know what you’re picking up): * Is the app free at first, then gated behind a subscription for features you’d consider essential rather than nice-to-have? * Does the “Pro” tier include things you’d consider table-stakes (prayer-time accuracy, ad-free Athkar, more reciters), or only nice-to-haves? * What’s the publisher’s incentive over time? Subscription apps tend to expand the paywall; ad-supported apps tend to expand ad load. This isn’t bad faith — it’s what monetisation pressure does. **Where Nedaa sits:** Free, no ads, no paywall, no subscription, no premium tier. Ever. No Pro version is planned, and there will not be one. This is a deliberate choice for _this_ project; it’s not a claim that other models are wrong. ### 4\. Source transparency and openness Islamic apps make consequential choices that the user can’t see: which Quran text, which Hadith collection (if any), which calculation method angles, which dataset for the morning/evening athkar. A user has no way to evaluate any of this without disclosure. **Questions to ask:** * Does the app name its data sources — Quran text, athkar dataset, calculation provider, reciter audio source? * Are the licence terms of those upstream sources respected (e.g. CC-BY attribution for Tanzil)? * Is the app source-code open? Can a knowledgeable user independently audit how data is handled? **Where Nedaa sits:** Sources named publicly. Athkar from **Hisn al-Muslim**. Prayer-time computation is provider-abstracted at the API layer; the **Aladhan API** is currently the only implemented upstream provider. (When the Quran reader ships: text from **Tanzil Project** under CC-BY 3.0 with attribution preserved, audio from **EveryAyah.com**, metadata from the **Quranic Universal Library (QUL) by Tarteel AI**, page imagery from **QCF / King Fahd Quran Complex** font work.) All disclosed in-app and on this site. Source code open at `github.com/NedaaDevs/nedaa`. ## The summary table | Dimension | What to look for | Where Nedaa sits | | ----------------------- | --------------------------------------------------------------------- | ---------------------------------------- | | **Data collection** | No account, no cloud profile, low-accuracy location, no tracking SDKs | All four ✓ | | **Advertising** | No ads in worship surfaces; no ad-removal upsell | No ads anywhere ✓ | | **Pricing model** | Free without ad-supported tradeoff; no creeping paywall | Free, no paywall, no premium tier ever ✓ | | **Source transparency** | Named data sources, licence-compliant attribution, open source | All four ✓ | ## Why this category matters more than feature checklists The feature list of any mature prayer-times app looks the same: Athan notifications, Qibla, Hijri date, a calculation-method picker. The non-feature differences above are where apps differ in ways that compound over time: * An app that collects data today may be acquired tomorrow and have its data-handling rules changed beyond the original team’s control. * An app that runs ads today often runs more ads when growth slows — same code, different load. * A free app that adds a Pro tier next year may move features you currently use behind it. (This is a real pattern, not a moral failing — it’s how the market works.) * An app whose sources are unnamed cannot be evaluated; you’re trusting an implementation you can’t see. These are the dimensions Nedaa was built around. Other dimensions matter to other people; we picked these. ## Get Nedaa * **iOS:** App Store — bundle id `dev.nedaa.app` * **Android (Google Play):** package `dev.nedaa.android` * **Android (Huawei AppGallery):** same package, separate `production-hms` build with no Google dependencies * **Source:** github.com/NedaaDevs/nedaa * **Support:** support \[at\] nedaa.dev --- _Last updated: 2026-05-10_