Privacy Policy

TL;DR

• We don't collect personal data. No accounts. No tracking.
• A few things happen locally on your device (your settings, custom Athkar, fasting Qada counter).
• The only data that leaves your device is: anonymized crash reports from your app store (automatic, like every app), opt-in Sentry crash details (off by default), in-app log files you choose to send for support, and prayer-time API requests (no IPs, headers, or bodies retained).
• If you want your data gone: delete the app. There is nothing on a server to delete.

What information we collect, how, and why

On your device only (we never see it)

• Your settings, custom Athkar, and fasting Qada counter. Stored locally so the app works between sessions.
• Your location (only if you grant the permission). Used to compute your prayer times. Low-precision. Never transmitted off your device.

What may reach us — and only under these conditions

• App-store crash reports. When the app crashes, your platform (Apple or Google) sends us anonymized crash counts and stack traces. This is the same as every app; it is handled by the store, not by us.
• Sentry crash details (opt-in). If you turn on Sentry reporting in Nedaa's settings, we receive crash details that help us fix bugs. This is off by default. You can turn it off at any time.
• In-app log files (user-sent). If you contact support and choose to attach app log files, we receive whatever you sent. Logs may contain device/OS info and a record of what the app did before the issue. We use them solely to help you.
• Prayer-time API requests. Our API is a proxy that forwards requests to a prayer-time provider — currently Aladhan, which is open source. Nedaa requests times roughly once a year per area, plus an extra request whenever you change a setting that requires a refetch (e.g., calculation method or madhab); the rest of the year, timings are read from local storage on your device. At our proxy, your coordinates are rounded to a coarse grid before forwarding — only the area bucket is passed downstream to the provider. The exact coordinates, IPs, request headers, and request bodies are not retained.

What we never collect

• No accounts, sign-ups, emails, or passwords.
• No advertising SDKs.
• No analytics SDKs that profile, segment, or fingerprint individuals.
• No location data sent off your device — ever.
• No third-party data brokers.
• No cookies, no cross-site tracking.

How we use what we receive

• Crash data is used to diagnose and fix bugs. We do not sell, share, or use it for any other purpose.
• Log files you send are used only to answer your support request.
• Prayer-time requests are served and discarded; nothing about who requested them is retained.

Sharing and third parties

Nedaa uses a small number of third parties strictly to operate. No data is sold or shared with advertisers.

• Your app store (Apple App Store, Google Play, Huawei AppGallery) — distributes the app, reports anonymized crash counts.
• Sentry (only if you opted in) — receives crash details. Sentry's own privacy policy applies to data they process on our behalf.
• The Nedaa API — operated by us; a proxy that forwards bucketed prayer-time requests to a provider. No retention as described above.
• Aladhan — current open-source provider behind our proxy. Receives only the bucketed area, never your exact location or device identifiers.

We do not work with advertising networks, analytics ad networks, or data brokers.

Data retention

• Crash reports received via Sentry are retained for as long as needed to diagnose bugs, then deleted.
• Support emails and attached logs are retained for as long as the support thread is active, then deleted.
• API request logs: aggregate counts only; no identifying data is retained.

Your rights

Because Nedaa does not maintain user accounts or personal data on a server, traditional data-subject requests (access, deletion, portability) are mostly moot — there is nothing on our side to access, delete, or port.

• To remove all data: delete the app. Local data is removed with it.
• To opt out of Sentry: turn it off in Nedaa's settings.
• For any other privacy question: email ••••••@nedaa.dev . We respond within five working days.

International transfers

Nedaa is available globally. Crash data sent to Sentry may be processed in regions outside your country. If you do not wish for any data to leave your device, do not enable Sentry; everything else operates locally or stays anonymized.

Children

Nedaa is suitable for users of all ages. We do not knowingly collect personal information from anyone — adult or child.

Security

We follow standard practices to protect what little data we receive:

• HTTPS in transit for all network calls.
• Crash data accessed only by maintainers.
• No system is perfectly secure; we'll notify users promptly if a breach affecting them ever occurs.

Changes to this policy

If we change this policy in a material way, we'll show a one-time, dismissible notice in the app — not a wall of text you must accept to continue praying. Non-material clarifications may be posted to this page without notice. The effective date at the top reflects the latest version.

Contact

For any privacy-related question or concern, email ••••••@nedaa.dev .

Nedaa is open source. Our source code, including everything that handles your data, is at github.com/NedaaDevs/nedaa.

Read our privacy stance →