Privacy Policy

Wazaif & Dhikr Counter respects your privacy and is committed to protecting the information entrusted to us when you use our application and related services.

Wazaif & Dhikr Counter is a religious and technological initiative developed through an official collaborative partnership between Eagle Alliance Technology and Iqra Rauza Tul Atfal & School.

This Privacy Policy explains what information may be collected, how that information is used, stored, synchronized, protected, and disclosed, and the choices available to you when using Wazaif & Dhikr Counter.

By using Wazaif & Dhikr Counter, you acknowledge that you have read and understood this Privacy Policy.

1. Scope of This Privacy Policy

This Privacy Policy applies to information processed through:

• The Wazaif & Dhikr Counter Android application;
• User accounts and authentication functionality;
• Wazaif, Zikr and recitation-counter features;
• Quran reading and progress features;
• Khatam-e-Quran and Para progress features;
• Reports, statistics and history features;
• Madrasa, group and related organizational features where applicable;
• User-created memos or other content where applicable;
• Backup and synchronization functionality;
• Notifications and reminders;
• Application settings and preferences.

This Policy does not apply to third-party websites, applications, services or platforms that may be accessed through or used alongside Wazaif & Dhikr Counter. Those services are governed by their own privacy policies.

2. Information We May Collect

We collect or process only information that is reasonably necessary to provide, maintain, secure and improve the application's functionality.

The categories of information may include the following.

2.1 Account and Profile Information

When you create or maintain an account, the application may process information such as:

• Name or contact person's name;
• Madrasa or organization name;
• Madrasa or organization name in Urdu, where provided;
• Email address;
• Phone number;
• User role;
• Location information entered by you in your profile;
• Preferred application language;
• Account creation and update timestamps;
• Account-related settings and statistics.

3. Wazaif, Zikr and Recitation Activity Data

When you use the application's counting and recitation functionality, the application may process information associated with your activity, including:

• Wazaif or Zikr entries;
• Current counter values;
• Target values;
• Counter history;
• Recitation activity;
• Count changes;
• Dates and timestamps associated with activity;
• Daily, weekly, monthly and lifetime statistics;
• Streak information;
• User-defined targets;
• Group or assigned Wazaif activity where applicable.

This information is used to provide counting, history, statistics, reporting, synchronization and related application functionality.

4. Quran Reading and Progress Information

Wazaif & Dhikr Counter includes Quran reading functionality.

When you use Quran-related features, the application may process information such as:

• Quran reading activity;
• Reading position;
• Para/Juz progress;
• Khatam-e-Quran progress;
• Completed Khatam records;
• Quran-related statistics;
• Reading history or progress timestamps;
• User preferences related to Quran reading.

The Quran content itself is application content and is separate from your personal account information.

The application architecture includes a dedicated Quran engine containing the Quran text and associated indexes. The documented Quran engine verifies 114 Surahs, 6,236 Ayahs, 30 Paras and 604 pages.

Reading progress and activity may be stored locally on the device and, where synchronization is enabled and applicable, synchronized with the application's remote services.

5. Account Authentication and Security Information

To authenticate and protect user accounts, the application may process security-related information required for authentication and account recovery.

This may include:

• Authentication identifiers;
• Authentication/session information;
• Security preferences;
• Recovery-related information;
• Cryptographically processed security values such as recovery-code or passcode hashes and salts, where applicable;
• Security-related timestamps and status information.

Passwords are not intended to be stored in plaintext.

Sensitive authentication information is designed to be protected using the application's secure-storage mechanisms. The documented architecture specifies Android KeyStore and AES-256 encrypted preferences for sensitive authentication tokens and user PINs.

6. Biometric Authentication

Wazaif & Dhikr Counter may support biometric authentication using compatible device capabilities, such as fingerprint or facial authentication, where supported by the device and operating system.

Biometric verification is performed through the device's operating-system biometric framework.

Wazaif & Dhikr Counter does not receive or store your fingerprint or facial biometric template as part of ordinary biometric authentication.

The application may retain the necessary authentication preference or security state indicating that biometric authentication has been enabled, but the underlying biometric information remains managed by the device's operating system.

7. Application Permissions

Wazaif & Dhikr Counter may request certain Android permissions when required for specific functionality.

These may include:

Internet Access

Used for:

• Account-related communication;
• Cloud synchronization;
• Remote data synchronization;
• Other online application services.

Network State

Used to determine whether the device is online or offline and to support the application's offline-first synchronization behavior.

Notifications

Used for:

• User-enabled reminders;
• Wazaif reminders;
• Prayer-related reminders where applicable;
• Other application notifications.

Notification permission is subject to the Android operating system's permission controls.

Vibration

Used for counter haptic feedback and related interaction feedback.

Biometric Authentication

Used to allow supported device biometric authentication.

Wake Lock

Used where required to support relevant application operations, including appropriate long-running Quran-reading or application activities.

8. Information We Do Not Intentionally Collect Through Required Permissions

Wazaif & Dhikr Counter does not require the following categories of permissions for its ordinary functionality:

• Camera access;
• Microphone/audio recording;
• Contacts;
• SMS;
• Call logs;
• Continuous or precise GPS location;
• Broad external storage access.

If future versions introduce functionality requiring additional permissions, this Privacy Policy may be updated accordingly.

9. Local Storage and Offline Operation

Wazaif & Dhikr Counter is designed with an offline-first architecture.

Certain information may be stored locally on your device so that core functionality can continue to operate without an active internet connection.

The documented architecture uses a local Room SQLite database as a local data source and uses caching for frequently accessed information.

Local data may include, depending on the features you use:

• Wazaif and counter information;
• Counter history;
• Quran-related information and progress;
• Application settings;
• Cached application information;
• Other locally required application state.

When an internet connection becomes available, information eligible for synchronization may be synchronized with the application's remote services.

10. Cloud Synchronization

Wazaif & Dhikr Counter may synchronize applicable account information and activity data with remote services so that supported features can operate across sessions and provide backup/synchronization functionality.

The documented architecture uses Firebase Firestore as the default remote synchronization implementation, behind an application-level synchronization abstraction.

Information that may be synchronized can include:

• Account/profile information;
• Wazaif and counter information;
• Daily activity records;
• Counter history;
• Quran/Khatam-related progress;
• Para progress;
• Memos or related user-generated information;
• Group or organizational information where applicable;
• Application statistics and related timestamps.

Synchronization may not occur immediately when the device is offline. Local information may remain on the device until a connection becomes available and the synchronization process can operate.

11. Third-Party Service Providers

Wazaif & Dhikr Counter may rely on third-party infrastructure providers to provide certain technical services.

The documented application architecture identifies Firebase/Google Firebase services as the default remote synchronization infrastructure.

These service providers may process information on behalf of or in connection with the application according to the services they provide and their applicable terms and privacy policies.

Third-party infrastructure may be used for purposes such as:

• Cloud data synchronization;
• Secure application infrastructure;
• Remote data storage;
• Authentication-related infrastructure where applicable;
• Application reliability and technical operations.

We do not authorize third-party service providers to use your personal information for purposes unrelated to the services they provide to the application, except where permitted or required by applicable law.

12. How We Use Information

Information processed through Wazaif & Dhikr Counter may be used for the following purposes:

Providing Core Functionality

To:

• Operate the application;
• Maintain user accounts;
• Provide Wazaif and Zikr counting;
• Maintain recitation history;
• Provide Quran reading features;
• Track Para and Khatam progress;
• Provide reports and statistics;
• Provide group or madrasa functionality where applicable.

Synchronization and Backup

To:

• Synchronize supported information;
• Maintain cloud copies of applicable user information;
• Restore supported account information;
• Maintain consistency between local and remote application data.

Security

To:

• Authenticate users;
• Protect accounts;
• Maintain sessions;
• Support account recovery;
• Detect or mitigate suspicious or unauthorized activity;
• Protect application infrastructure.

Notifications and Reminders

To provide reminders and notifications that are enabled or authorized by the user.

Reliability and Maintenance

To:

• Diagnose technical problems;
• Handle application errors;
• Maintain application functionality;
• Improve reliability;
• Protect the integrity of application data.

Legal Compliance

To comply with applicable legal obligations, respond to lawful requests, and protect our rights, users and services where reasonably necessary.

13. Analytics, Statistics and Reports

Wazaif & Dhikr Counter provides statistics and reports based on activity recorded through the application's features.

These may include:

• Daily totals;
• Weekly totals;
• Monthly totals;
• Lifetime totals;
• Recitation history;
• Streaks;
• Wazaif statistics;
• Quran/Khatam statistics;
• Group or madrasa statistics where applicable.

The documented architecture includes an aggregated analytics engine for daily, weekly, monthly and lifetime calculations.

These statistics are generated from application activity and are intended to provide users and authorized organizational users with relevant insights.

14. Madrasa, Group and Organizational Data

Where Wazaif & Dhikr Counter provides madrasa, group, assignment or organizational functionality, additional information may be processed to support those features.

This may include:

• Madrasa or organization identifiers;
• Group information;
• Assigned Wazaif;
• User roles;
• Group participation;
• Organizational statistics;
• Activity associated with an assigned group or organization.

Access to organizational information is intended to be based on the user's applicable role and permissions.

Users are responsible for ensuring that information they provide about other individuals or organizations is submitted only where they have appropriate authority to do so.

15. User-Generated Content

Certain features may allow users to create or submit information such as:

• Memos;
• Wazaif names or custom entries;
• Targets;
• Group-related information;
• Other information entered into supported application fields.

Such information is processed to provide the feature for which it was submitted.

Users should not submit unnecessary sensitive personal information into free-text fields.

16. Data Security

We take reasonable technical and organizational measures to protect information processed through Wazaif & Dhikr Counter.

The documented architecture includes:

• Secure storage mechanisms;
• Android KeyStore;
• AES-256 encrypted preferences for sensitive authentication-related information;
• Authentication and session security mechanisms;
• Offline-first local data architecture;
• Remote synchronization abstraction;
• Application security controls;
• Error-handling mechanisms;
• Data-layer separation and controlled repository access.

The documented security architecture specifically identifies Android KeyStore and AES-256 encrypted preferences for sensitive authentication tokens and user PINs.

However, no method of electronic storage or transmission can be guaranteed to be completely secure. Accordingly, we cannot guarantee absolute security of information under every possible circumstance.

17. Account Isolation and Access Control

Wazaif & Dhikr Counter is designed to associate account-related information with the applicable user, role, organization and/or ownership boundary.

The application's architecture uses separated data layers and repository contracts to control access between application features and storage mechanisms.

Access to organizational or administrative information may depend on the authenticated user's role and authorization.

Because software systems can contain implementation defects, we do not represent that unauthorized access is mathematically impossible. Security and account-isolation controls are subject to ongoing testing, maintenance and improvement.

18. Data Retention

We retain information for as long as reasonably necessary to:

• Provide the requested application functionality;
• Maintain your account;
• Maintain applicable synchronization and history;
• Fulfill legitimate operational purposes;
• Resolve disputes;
• Maintain security;
• Comply with applicable legal obligations.

The exact retention period may vary depending on the type of information, the feature involved, account status, technical requirements and applicable law.

Where a specific deletion mechanism is available within the application, users may use that mechanism to request or perform deletion of applicable information.

Some information may need to be retained for a limited period where required for security, fraud prevention, legal compliance, dispute resolution, or legitimate technical purposes.

19. Account and Data Deletion

Where account deletion functionality is provided, you may request deletion of your account and associated information through the available application or support mechanism.

Deletion may not necessarily result in immediate removal from all systems where:

• Information is required to comply with legal obligations;
• Security or fraud-prevention records must be retained;
• Information is included in technical backups that are subject to normal backup-retention cycles;
• The information is required to resolve an ongoing dispute;
• The information has been lawfully aggregated or otherwise processed in a manner that no longer identifies you.

Where deletion is requested, reasonable steps will be taken to process the request according to applicable technical and legal requirements.

20. Backups and Synchronization Limitations

Although Wazaif & Dhikr Counter may provide synchronization and supported backup functionality, users should not assume that cloud synchronization is an unlimited or infallible substitute for independent backups.

Synchronization may be affected by:

• Lack of internet connectivity;
• Device problems;
• Account authentication issues;
• Service outages;
• Software errors;
• Interrupted synchronization;
• Data corruption;
• Changes to third-party infrastructure.

Users should maintain appropriate independent records of information that is particularly important to them.

21. Notifications and Reminders

Wazaif & Dhikr Counter may provide reminders and notifications for supported features.

Depending on your Android version and settings, notification permission may be required.

You can generally control notification permissions through your device settings and, where available, through application settings.

The application may use Android background scheduling mechanisms to support reminders and scheduled notifications. The documented architecture identifies Android AlarmManager/WorkManager abstractions for background notification scheduling.

22. Children's Privacy

Wazaif & Dhikr Counter is not intended to knowingly collect unnecessary personal information from children.

Where the application is used in a madrasa, school, educational or organizational environment involving minors, the organization, parent, guardian or responsible administrator should ensure that appropriate consent, authorization and applicable legal requirements are satisfied before entering personal information about a minor into the application.

We do not intentionally request unnecessary sensitive information from children.

If you believe that personal information relating to a child has been submitted improperly, please contact us so that the matter can be reviewed.

23. Sharing and Disclosure of Information

We do not sell your personal information.

Information may be disclosed only where reasonably necessary for purposes described in this Privacy Policy, including:

Service Providers

To infrastructure and technology providers that help operate the application and its services.

Authorized Organizational Users

Where organizational features are used, information may be visible to authorized administrators or users according to applicable roles and permissions.

Legal Requirements

Where disclosure is required by applicable law, court order, governmental authority, or other lawful process.

Protection of Rights and Security

Where reasonably necessary to:

• Protect users;
• Protect the application;
• Prevent fraud or abuse;
• Investigate security incidents;
• Protect legal rights;
• Address threats to safety or infrastructure.

Business Changes

If the application, its assets or relevant operations are involved in a merger, acquisition, restructuring, transfer or similar business transaction, information may be transferred as part of that transaction subject to applicable law and appropriate privacy protections.

24. We Do Not Sell Personal Information

Wazaif & Dhikr Counter does not sell personal information to third parties.

We also do not use your religious or recitation activity information as a product for sale to advertisers.

If future functionality materially changes how personal information is used, this Privacy Policy will be updated where required.

25. Religious and Spiritual Activity Information

Wazaif & Dhikr Counter is designed around Islamic religious and spiritual practices, including Wazaif, Zikr, Quran reading and related activities.

Information generated through these features may reveal aspects of how a user interacts with religious content.

We therefore treat such information as user-related application data and process it only for legitimate application, synchronization, security, organizational and service purposes described in this Policy.

Users should avoid entering sensitive personal information into custom fields unless it is necessary for the relevant feature.

26. Data Accuracy

You are responsible for ensuring that information you provide to Wazaif & Dhikr Counter is accurate and up to date.

The application may calculate statistics and reports based on information recorded through its functionality.

Because these calculations depend on user activity, device state, synchronization and application operation, displayed statistics should be understood as application-generated records rather than an independent verification of real-world activity.

27. International and Cross-Border Processing

Depending on the location of our service providers and infrastructure, information may be processed or stored in countries other than the country in which you reside.

Where required, appropriate measures will be taken in accordance with applicable data-protection requirements.

The specific geographic location of every infrastructure component may change as service providers and infrastructure evolve.

28. Data Breach and Security Incidents

If we become aware of a security incident involving personal information that requires notification under applicable law, we will take reasonable steps to investigate, contain and address the incident and provide notifications where legally required.

Users are also encouraged to protect their account credentials and device security and to notify us of suspected unauthorized access.

29. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect:

• Changes to the application;
• New features;
• Changes to data processing;
• Changes to third-party services;
• Security improvements;
• Legal or regulatory requirements.

When material changes are made, the updated Policy will be published through an appropriate application or website channel.

The Last Updated date at the beginning of this Policy indicates when the current version became effective.

30. Your Privacy Choices and Rights

Depending on your location and applicable law, you may have rights concerning your personal information, which may include:

• Requesting access to information associated with your account;
• Requesting correction of inaccurate information;
• Requesting deletion of applicable information;
• Requesting information about how your data is processed;
• Withdrawing permissions that are controlled at the device level;
• Disabling notifications;
• Requesting assistance regarding your account information.

Certain requests may be subject to identity verification, legal limitations, technical limitations or legitimate retention requirements.

To exercise a privacy-related right or request assistance, contact us using the information provided below.

31. Third-Party Links and Services

Wazaif & Dhikr Counter may in the future provide links, integrations or references to third-party services.

We are not responsible for the privacy practices, security practices or content of independent third-party services.

You should review the privacy policy of any third-party service before providing information to that service.

32. Security Responsibility of the User

You are responsible for taking reasonable steps to protect access to your device and account.

You should:

• Use a secure password;
• Keep authentication information confidential;
• Avoid sharing recovery information;
• Use device security features;
• Log out when using a shared device where appropriate;
• Keep the application and operating system updated;
• Notify us if you suspect unauthorized account activity.

We will not ask you to disclose your password through an unsolicited message.

33. No Absolute Security Guarantee

Although we implement reasonable security controls, no application, database, network or electronic transmission can be guaranteed to be completely secure.

Accordingly, Wazaif & Dhikr Counter cannot guarantee that information will never be accessed, altered, disclosed or destroyed through circumstances beyond reasonable control.

Our security measures are intended to reduce risk, not eliminate every possible security threat.

34. Contact Us

For privacy-related questions, requests, concerns or complaints, please contact:

Wazaif & Dhikr Counter

Official Contact Email:
info@wazaifcounter.com

You may contact us regarding:

• Privacy questions;
• Data-access requests;
• Data-correction requests;
• Account-related privacy concerns;
• Data-deletion requests;
• Security concerns;
• Questions about this Privacy Policy.

35. Effective Date

This Privacy Policy is effective from: 10 September 2026, and applies to Wazaif & Dhikr Counter from that date onward, subject to subsequent updates published in accordance with this Policy.