This Privacy Policy outlines how Neuroxie Lab ("we", "our", or "us") manages personal information and system access inside the IslahBD mobile application (the "App"). We hold consumer privacy in the highest regard, especially within digital tools meant for prayer tracking and spiritual assistance.
To establish explicit transparency under the Google Play Developer Program Policies regarding user transparency, this document details how our app accesses device hardware features. IslahBD is fundamentally architected as a Zero-Data-Collection Application. We do not provision client server instances, and we do not compile behavioral profiling or metadata on our users.
Google Play User Data Policies require explicit declarations of sensitive device permissions. Below is an exhaustive breakdown of the hardware capabilities requested by IslahBD, detailing exactly why they are required and how they are isolated:
| Android Permission / Data Category | Collection Status | Core Purpose & Functional Necessity | Storage / Transfer Protocol |
|---|---|---|---|
| ACCESS_FINE_LOCATION (Precise GPS Coordinates) |
NOT COLLECTED | Required directly to run immediate, local geometric math equations against global geographical grids to compute the precise angular direction of the Qibla (Kaaba compass orientation). | On-Device Transient Memory Only: Processed instantly in volatile runtime RAM. Never written to permanent disk storage; never transmitted over the internet to any remote cloud servers. |
| ACCESS_COARSE_LOCATION (Approximate Network Location) |
NOT COLLECTED | Required to automatically parse regional time zones and city location clusters. This determines accurate astronomical calculations for daily localized Islamic Prayer Times (Salah timelines). | On-Device Isolation: Evaluated inside the client software layer sandbox environment. Completely isolated from external endpoints. |
| POST_NOTIFICATIONS (Push Notification Handling) |
NOT COLLECTED | Required to fire prompt triggers regarding ongoing live bayans, regional islamic alerts, or custom operational schedule notices. | Local Device Triggers: Managed natively via the local system notification registry. No centralized tracking tags attached. |
To maximize security and eliminate compliance liabilities, IslahBD bypasses traditional cloud account generation systems entirely:
Because IslahBD does not store or process your personal data on any server, there is no personal data held in the cloud to delete. This architectural model provides users with ultimate data sovereignty.
Any local configurations or system variables chosen by the user are stored entirely within the device’s private sandbox storage space. To reset, wipe, or request absolute deletion of this local configuration cache, follow the manual clearing protocol below:
IslahBD is engineered as a spiritual and lifestyle utility tailored for general audiences. However, to stay fully aligned with the strict child protection guidelines of global frameworks and the Google Play Families Policy, we enforce clear boundaries:
The App is intentionally designated and targeted for use by individuals aged 16 and older. We do not knowingly solicit or collect data from children under the age of 13. In the event that a child under 13 activates the app, no personal data can be harvested due to our fundamental zero-data-collection infrastructure. If you suspect that local device configurations contain variables you wish to remove, simply execute the data erasure steps listed in Section 4.
We may update this legal document from time to time to accommodate evolving software optimizations, feature sets, or updates to the Google Play Developer Distribution Agreement. Any changes will be marked by an updated "Effective Date" at the top of this page. We highly recommend that our user community inspect this link periodically to stay continuously informed about our absolute data isolation models.
For any clarifying technical questions regarding the software sandboxing process, sensor computation logic, or to confirm policy validation details during Google Play store inspection cycles, please contact our core oversight desk: