Privacy Policy
This Privacy Policy describes how Awdah (“Awdah”, “we”, “us”, or “our”) collects, uses, stores, shares, and protects information when you use the Awdah mobile applications for iOS and Android, the public marketing and legal website at https://awdah.online/, and related services that support your spiritual habit journey. We wrote this policy to be clear and thorough because Awdah handles sensitive personal choices — when you wake for Tahajjud, what you reflect on, who you encourage in Family Hub, and what duas you share in community spaces.
By downloading, installing, accessing, or using Awdah, you acknowledge that you have read and understood this Privacy Policy. If you do not agree with this policy, please do not use the app or website. Where local law requires a separate legal basis or consent for specific processing, we will seek that consent or provide an alternative as required.
1. Introduction & data controller
Awdah is an Islamic habits and spiritual growth application published under the Awdah brand. The app helps Muslims build sincere night-prayer routines, complete guided journeys, stay connected with family encouragement, participate in dua communities, and read Quran content through a controlled in-app experience. Our public-facing website is https://awdah.online/, where you can learn about the app, read legal documents, and contact support.
For the purposes of applicable data protection laws (including, where relevant, the EU/UK General Data Protection Regulation and similar frameworks), the entity responsible for deciding how your personal data is processed in connection with Awdah is the publisher of the Awdah application. You can reach us at mytadhkira@gmail.com for privacy-related questions, requests, or complaints.
This policy applies to information we process as a controller. Some third parties — such as Apple, Google, Firebase, authentication providers, and the Quran ebook host — may also process information about you under their own privacy policies when you interact with their services through Awdah. We explain those relationships in Section 10.
Awdah is designed as a habit companion, not a financial product. We do not operate in-app wallets, payment processing, cryptocurrency features, or subscription billing inside the core Awdah experience described in this policy. If that ever changes in a future version, we will update this document before launching such features.
2. Scope of this policy
This Privacy Policy covers the following surfaces:
- Awdah for iOS — distributed via the Apple App Store.
- Awdah for Android — distributed via Google Play (package name
com.oxilios.tadhkira). - The awdah.online website — including the home page, Privacy Policy, Terms of Use, Support page, and Disclaimer.
- Backend and API services — account synchronization, community features, configuration checks, and push notification delivery. Our application programming interface and related backend infrastructure are hosted at awadah.online (WordPress-based services). The public marketing site remains awdah.online; both domains are operated for Awdah-related purposes, and data processed through the app may transit awadah.online even when you discover the product on awdah.online.
This policy does not govern:
- Third-party websites or services you reach outside Awdah’s allowlisted flows (for example, arbitrary links opened in your device browser).
- The internal analytics, cookies, or logging practices of ebooks.qamarapps.com, which hosts the 13 Line Quran ebook loaded inside Awdah’s WebView. That host operates under its own policies when pages load.
- Apple App Store, Google Play, or social sign-in providers’ independent processing — though we summarize how Awdah integrates with them.
If you use Awdah without creating an account, certain features that require authentication (Family Hub, Dua Circle, cloud sync of journeys, and similar) will not be available, and less account-linked data will be processed. Local-only features such as scheduling a Tahajjud alarm may still interact with your device operating system.
3. What the Awdah app does (feature inventory)
Understanding what the app does helps explain what data we need. Awdah is organized around night prayer, daily remembrance, family encouragement, and community dua. The major feature areas include:
3.1 Home hub
The Home screen is your daily starting point. It surfaces a remembrance card, streak and progress indicators, days completed in active journeys, and shortcuts to Tahajjud, Family Hub, challenges, and the 13 Line Quran reader. Home may display personalized summaries derived from your app activity (for example, how many nights you logged this week or which journey day is active).
3.2 Tahajjud alarms, tracking, and weekly heart
Tahajjud is central to Awdah. You can schedule a local alarm for a time you choose in the last third of the night, log nights when you prayed, view streak history, and fill a weekly “heart” progress visualization (nights out of seven). On Android, ringing alarms may use exact alarm scheduling, a full-screen intent (FSI) to present the alarm UI when the device is locked, and a foreground service with media playback (FGS) so alarm audio continues reliably. These capabilities exist solely to deliver user-scheduled Tahajjud reminders — not for advertising or background tracking.
3.3 Guided journeys (e.g., Heart of Shukr)
Journeys are multi-day guided paths with ordered tasks, reflection screens with Arabic text and translations, and progress states (done, start, locked). Themes catalog additional journeys and describe who each path is for. Progress is stored so you can resume across sessions and devices when signed in.
3.4 Family Hub
Family Hub lets you create or join a private family circle, set weekly goals, track member participation, and send encouragement, dua, or thanks actions within your group. Data you share here is visible to members of your hub as designed — it is not a public social network.
3.5 Dua Circle
Dua Circle is a community space where you can post a dua request and others can respond with “Ameen.” Posts you submit may be visible to other Awdah users participating in the feature, subject to product rules and moderation.
3.6 Tahajjud challenges
Challenges invite individuals or groups to rise for Tahajjud together over a defined period. You can explore public challenges, join with an invite code, or create your own. Participation data (join status, progress) is processed to operate the challenge experience.
3.7 Daily Duas library
Awdah includes a browsable library of Sunnah duas organized by category (morning, evening, eating, drinking, and more). Search and category filters help you find supplications for everyday moments. This content is largely static within the app; we may log which categories you open for product improvement in aggregate or pseudonymous form, but we do not treat dua recitation as a commercial profiling signal.
3.8 13 Line Quran reader (in-app WebView)
From Home, you can open a 13 Line Quran ebook inside an in-app WebView. Pages load over HTTPS from ebooks.qamarapps.com only. Awdah maintains an allowlist of permitted hosts for this feature; URLs that do not match the allowlist are blocked. This design prevents the Quran reader from being repurposed as a general browser to arbitrary websites.
3.9 Push notifications (FCM / APNs)
With your permission, Awdah may register your device for push notifications through Firebase Cloud Messaging (Android and cross-platform infrastructure) and Apple Push Notification service (APNs) on iOS. Push may be used for habit reminders, journey nudges, family or challenge activity, and important service announcements you enable.
3.10 Sign-in (email and social providers)
You may create and access an account using email-based authentication and, where enabled, social sign-in providers (such as Apple or Google). Authentication tokens and profile basics from those providers are used to identify your account and sync your progress.
3.11 Force update to official stores only
Awdah may check a minimum required app version from our servers. If your installed version is below the minimum, the app can block continued use until you update via the official Apple App Store or Google Play listing only. Update links are allowlisted to store domains — Awdah does not redirect you to third-party APK sites or arbitrary download pages.
3.12 Account deletion
You may delete your account from within the app via Profile → Delete account (wording may vary slightly by version). Deletion initiates removal of account-linked data from our active systems, subject to retention limits described in Section 12.
4. Categories of personal data we collect
We collect only what we need to provide Awdah’s features, keep the service secure, and comply with law. The table below summarizes major categories. Examples are illustrative; exact fields may evolve as we improve the app.
| Data category | Examples | Purpose | Typical legal basis (where GDPR-style law applies) |
|---|---|---|---|
| Account & identity | Email address, display name, internal user ID, authentication provider identifiers (Apple/Google subject IDs), password hash if email sign-up is used | Create and secure your account; sync progress across devices; respond to support and deletion requests | Performance of contract; legitimate interests in security |
| Profile information | Profile photo you upload, optional bio or preferences shown in Family Hub | Personalize your profile; display your identity to family or community features you join | Performance of contract; consent where required for optional fields |
| App activity & spiritual logs | Tahajjud night logs, streaks, weekly heart counts, journey task completion, reflections you enter, challenge join/progress, Family Hub actions, Dua Circle posts | Operate core habit, journey, family, and community features; show you accurate history and progress | Performance of contract |
| User preferences | Tahajjud alarm time, reminder toggles, notification settings, theme or onboarding choices | Honor your chosen schedule and settings; reduce unwanted notifications | Performance of contract; consent for notifications where required |
| Push & device tokens | FCM registration token, APNs device token, platform type (iOS/Android) | Deliver push notifications you enable; retire invalid tokens | Consent (where required); legitimate interests in service delivery |
| Device & app metadata | App version, OS version, device model, language/locale, timezone | Force-update checks, compatibility, debugging, aggregated analytics, abuse prevention | Legitimate interests; performance of contract for version enforcement |
| Diagnostics & security logs | Crash reports, error codes, API request timestamps, IP address in server logs, authentication events | Keep the service reliable and secure; investigate outages and misuse | Legitimate interests; legal obligation where applicable |
| Support communications | Emails you send to mytadhkira@gmail.com, optional screenshots or descriptions you provide | Answer questions; resolve bugs; handle deletion or rights requests | Legitimate interests; performance of contract; legal obligation |
| Website technical data | Standard server logs for awdah.online (IP, user agent, pages requested, referrer) | Operate and secure the static marketing site; understand aggregate traffic | Legitimate interests |
We do not require you to provide more data than necessary for a given feature. If you decline optional permissions (such as notifications), core local features may still work while cloud or push-dependent features may be limited.
5. Data we do not collect
We believe privacy includes restraint. Unless you explicitly choose to share content through a feature (such as typing a dua in Dua Circle), Awdah does not:
- Access or upload your device contacts address book for friend-finding or marketing. Family Hub and challenges use codes, invites, and in-app relationships — not a scraped contacts list.
- Collect continuous GPS or precise location tracking in the background. Awdah is not a location-based habit tracker; prayer logging does not depend on knowing where you are.
- Sell your personal information to data brokers or advertising exchanges. We do not monetize your spiritual logs or dua content through sale of personal data.
- Record microphone or camera for Tahajjud alarms, Quran reading, or journeys. Alarm audio playback uses bundled or streamed media files — not live microphone surveillance.
- Operate in-app payments or wallet balances as part of the current Awdah product described here.
- Read your SMS, call log, or browsing history outside the allowlisted Quran WebView host.
If future features require new data types, we will update this policy and, where required, request permission or consent before collection.
6. How major features process data
6.1 Tahajjud alarms & tracking
When you set a Tahajjud reminder, the alarm time and enable/disable state are stored locally on your device and, if you are signed in, may sync to our backend at awadah.online so your settings restore on a new device. When the alarm fires, the operating system — not a remote server — triggers the local notification or full-screen alarm UI. Logging a completed night creates an activity record tied to your account (if signed in) or stored locally until you sign in. Streak and weekly heart calculations derive from these logs. We do not infer your location or movement from alarm usage.
6.2 Journeys (Heart of Shukr and others)
Journey progress includes which journey is active, completed tasks, locked/upcoming days, and reflections you submit. This data is stored on our servers when you are authenticated so you can continue across reinstalls. Sacred text displayed in journeys is largely static content bundled or fetched as part of the journey definition; your personal reflections are treated as user-generated content linked to your account.
6.3 Family Hub
Creating or joining a hub processes hub membership, display names, profile photos, weekly goals, and interaction events (encourage, dua, thanks). Members of the same hub can see shared hub content according to product design. Hub data is stored on awadah.online-backed services. You should only invite people you trust, as family-visible data is shared within the hub.
6.4 Dua Circle
Posts you submit to Dua Circle are stored and displayed to other participants. Do not include sensitive personal information (medical details, phone numbers, home addresses) unless you accept that other users may see it. We may remove content that violates our Terms or community standards. Moderation and reporting data may be retained in security logs.
6.5 Challenges
Challenge participation stores challenge ID, join date, invite codes you use, progress metrics, and public metadata needed for leaderboards or explore views where applicable. Creating a challenge processes the title, schedule, and visibility options you configure.
6.6 Daily Duas
Browsing duas generally does not create a public profile. We may collect aggregate usage (popular categories) to improve ordering and content. Your individual dua browsing is not sold to advertisers.
6.7 13 Line Quran WebView & third-party cookies
When you open the Quran reader, Awdah loads HTTPS pages from ebooks.qamarapps.com inside a sandboxed WebView with host allowlisting. The ebook provider may set cookies, local storage, or server logs on its domain to deliver pages, remember reading position, or measure performance. Those practices are governed by the host’s policies, not this website’s cookie section alone. Awdah blocks navigation to non-allowlisted domains from this WebView. We do not use the Quran reader to inject arbitrary third-party advertising scripts beyond what the ebook host serves.
6.8 Authentication & account sync
Sign-in exchanges tokens with our backend at awadah.online and, when you use social login, with Apple or Google. We receive identifiers and basic profile fields permitted by the provider (such as name and email). Passwords, if used, are handled through secure authentication flows rather than stored in plain text on your device by Awdah.
6.9 Force update checks
The app may send its version number and platform to our configuration endpoint. If an update is required, you are directed to the official store listing. These checks do not transmit your spiritual logs or dua content.
7. Notifications & alarm permissions explained
Awdah uses several complementary mechanisms to help you wake for Tahajjud:
- Local notifications and alarms — scheduled on your device for the time you pick. They can fire even when the app is not open, subject to OS rules.
- Push notifications (optional) — delivered via FCM/APNs when enabled, useful for reminders, journey prompts, or family/challenge activity.
- Full-screen alarm UI (Android) — when permitted, presents a dismiss/snooze interface over the lock screen for scheduled Tahajjud alarms.
- Foreground audio (Android) — keeps alarm audio playing during the ringing period when required by the OS.
You control many of these through in-app toggles and through iOS Settings or Android system settings. Denying notification permission may limit push reminders but does not necessarily disable locally scheduled alarms you explicitly configure — though OEM battery optimizations can affect reliability, which is outside our direct control.
We do not use notification permissions to send unrelated commercial spam. Message content relates to Awdah features you use or enable.
8. Android-specific permissions
The Android app may request permissions that sound sensitive because Tahajjud alarms must work when the phone is locked and quiet hours are enabled. Each permission below is used in a limited, purpose-bound way:
8.1 USE_EXACT_ALARM
Allows scheduling alarms at an exact time you choose. Without exact alarm capability (or the user-granted equivalent on newer Android versions), a Tahajjud reminder scheduled for 4:15 a.m. might drift by minutes or be batched with other notifications, which defeats the purpose of a night prayer alarm. We use exact alarms only for user-scheduled Tahajjud and related habit reminders — not for background analytics or silent polling.
8.2 USE_FULL_SCREEN_INTENT (FSI)
Allows presenting the alarm activity full-screen when the device is locked, similar to an incoming call UI. This helps you see dismiss and snooze controls immediately when the Tahajjud alarm rings. We do not use full-screen intents for advertisements or unsolicited promotions.
8.3 FOREGROUND_SERVICE_MEDIA_PLAYBACK (FGS)
Allows a foreground service typed for media playback while alarm audio plays, reducing the chance that the system kills audio during a ringing alarm. The service runs in connection with an active user-scheduled alarm session — not as a persistent background tracker.
8.4 Other common Android permissions
Depending on version, you may also see requests for POST_NOTIFICATIONS (Android 13+), INTERNET (sync, Quran WebView, push registration), RECEIVE_BOOT_COMPLETED (reschedule alarms after reboot), and WAKE_LOCK (keep the CPU awake briefly during alarm delivery). Each supports reliability of features you enable.
You can review and revoke permissions in Android Settings; revoking exact alarm or notification permissions may impair Tahajjud reliability, which we will disclose in-app where practical.
9. iOS notifications & alarms
On iOS, Tahajjud reminders rely on local notifications and, where supported by the operating system version and our implementation, alarm APIs such as notification-based alarms or future AlarmKit integration if enabled in a given release. iOS does not expose the same full-screen intent model as Android; instead, time-sensitive notifications, Critical Alerts (if ever granted by Apple for this use case), and user attention settings affect whether an alarm breaks through Focus modes.
When you grant notification permission, APNs registration tokens may be stored on our backend to deliver remote pushes you opt into. Local alarm schedules are stored on-device in iOS notification centers. Disabling notifications in iOS Settings will block pushes and may affect local notification delivery depending on how you configured reminders.
Apple’s App Store privacy nutrition labels summarize categories of data linked to you; this policy provides additional detail beyond those labels.
10. Third-party services & processors
We use trusted providers to operate Awdah. They process data on our instructions or under their own terms when you interact with them directly:
- Firebase / Google (FCM) — push notification delivery and related infrastructure on Android and potentially cross-platform messaging metadata.
- Apple (APNs, App Store, Sign in with Apple) — push on iOS, app distribution, and optional authentication.
- Google Play — Android app distribution and optional Google sign-in.
- Authentication providers — verify identity when you choose social login; we receive limited profile fields.
- ebooks.qamarapps.com — hosts 13 Line Quran ebook HTML/content loaded in the allowlisted WebView.
- Hosting providers — serve awdah.online static pages and awadah.online backend/API infrastructure (including WordPress-related hosting where applicable).
- Email — support correspondence sent to mytadhkira@gmail.com may be processed by your and our email providers.
We require processors to protect personal data under contractual or statutory obligations where applicable. We do not authorize providers to sell your Awdah spiritual logs for their independent advertising products.
Community content you post may be visible to other users — those users are not “processors,” but you should treat Dua Circle and public challenge views as shared spaces.
11. International data transfers
Awdah is available internationally. Our servers, support team, and third-party providers may be located in countries other than your own, including countries that may not provide the same level of data protection as your jurisdiction. Where required, we implement appropriate safeguards for cross-border transfers, such as standard contractual clauses, adequacy decisions, or equivalent mechanisms recognized under applicable law.
By using Awdah, you understand that your information may be processed in jurisdictions where privacy laws differ. You may contact us at mytadhkira@gmail.com to request more information about safeguards relevant to your region.
12. Data retention
We retain personal data only as long as necessary for the purposes described in this policy:
- Active accounts — account, profile, and activity data are kept while your account remains open so features continue to work.
- Deleted accounts — when you use Profile → Delete account, we delete or anonymize account-linked data from active production systems within a reasonable period, typically within 30 days, unless a longer period is required for legal compliance, dispute resolution, or security (for example, backup tapes or aggregated logs with no direct identifiers).
- Push tokens — removed or invalidated when you disable notifications, uninstall the app, or delete your account.
- Server and security logs — retained for a limited rolling window (often 30–90 days) unless extended for incident investigation.
- Support emails — retained as long as needed to resolve your request and maintain a reasonable support history.
- Legal holds — if we must preserve data due to litigation or regulatory request, we will retain only what is necessary.
Aggregated or de-identified statistics that cannot reasonably re-identify you may be kept longer for product analytics.
13. Security measures
We take security seriously, especially for spiritual and community content. Measures include, at a high level:
- HTTPS/TLS encryption for data in transit between the app and awadah.online services, and for Quran pages loaded from ebooks.qamarapps.com.
- Access controls limiting employee and contractor access to production data on a need-to-know basis.
- Authentication protections for account sign-in, including industry-standard handling of credentials and tokens.
- Allowlisting for sensitive WebView navigation and store update URLs to reduce open-redirect and unwanted content risks.
- Monitoring for abnormal API activity and crash spikes that may indicate abuse or instability.
No method of transmission or storage is 100% secure. If we become aware of a breach affecting your personal data, we will notify you and regulators as required by applicable law.
14. Children’s privacy
Awdah is a general-audience spiritual habit app. We do not knowingly collect personal information from children under 13 (or under 16 in certain jurisdictions) without appropriate parental consent where required by law. If you believe a child has provided us personal data without consent, contact mytadhkira@gmail.com and we will take steps to delete the information.
Parents and guardians should supervise minors using community features (Dua Circle, public challenges) to ensure they do not share personal contact information publicly.
15. Your privacy rights
Depending on where you live, you may have rights regarding your personal data, including:
- Access — request a copy of personal data we hold about you.
- Correction — ask us to fix inaccurate account or profile information.
- Deletion — delete your account in-app via Profile → Delete account, or email us to confirm deletion if you cannot access the app.
- Restriction or objection — object to certain processing based on legitimate interests, where applicable.
- Portability — receive certain data in a structured, machine-readable format where technically feasible.
- Withdraw consent — where processing is based on consent (such as optional marketing pushes if ever offered separately), withdraw consent without affecting prior lawful processing.
- Complaint — lodge a complaint with your local supervisory authority.
To exercise rights, email mytadhkira@gmail.com with the subject line “Privacy Request” and enough information to verify your account (such as the email used to sign up). We respond within the timeframe required by applicable law (often 30 days). We may need to retain certain data to complete deletion cascades or comply with legal obligations.
California residents may have additional rights under the CCPA/CPRA (know, delete, correct, opt out of sale/share). As stated, we do not sell personal information. Authorized agent requests will be handled as required by law.
16. Cookies on awdah.online
The awdah.online marketing website is primarily static HTML with minimal cookie use. Our site CSS and fonts may be loaded from Google Fonts; Google may process connection metadata under its policies. We do not operate a heavy analytics or advertising cookie layer on awdah.online itself.
When you follow links from awdah.online to the App Store or Google Play, those platforms set their own cookies and tracking under their policies. The in-app Quran WebView on ebooks.qamarapps.com may set cookies on that third-party domain as described in Section 6.7 — those cookies are not controlled by awdah.online’s static pages.
You can manage cookies through your browser settings. Blocking all cookies may not affect reading this policy but may affect third-party embeds if we add them in the future; we will update this section if we introduce new tracking technologies on the website.
17. Changes to this policy
We may update this Privacy Policy when we add features, change providers, or respond to legal developments. When we make material changes, we will update the “Last updated” date at the top of this page and, where appropriate, provide additional notice in the app or via email. Continued use of Awdah after the effective date of an updated policy constitutes acceptance of the revised terms, except where further consent is required by law.
We encourage you to review this page periodically. Prior versions may be available upon request to mytadhkira@gmail.com.
18. Contact us
If you have questions, concerns, or requests about this Privacy Policy or how Awdah handles information, contact us:
- Email: mytadhkira@gmail.com
- Website: https://awdah.online/
- Support page: awdah.online/support.html
For account deletion, use Profile → Delete account in the app when available, or email us from your registered address so we can verify ownership before processing deletion.
Related documents: Terms of Use · Disclaimer