1. Scope
This policy covers QAZA E UMRI, a prayer and Qaza tracking and planning app, and its informational website at qazaeumri.app. Contact the QAZA E UMRI developer at support@qazaeumri.app.
The app is being prepared for release. This policy reflects the current local-first app implementation reviewed on September 11, 2026. It will be reviewed again against the signed release build before publication.
2. Information stored in the app
The app stores the information you enter on your device. This can include prayer and Qaza records, historical estimates, daily status, Qaza history and audit entries, plan revisions, goals, preferences, reminder settings, and optional menstrual or excused-day dates. It also records dates and times needed to show your history and progress.
This information is used only to provide the app’s tracking, planning, calendar, progress, reminder, backup, and restore features. Prayer records and optional menstrual-day entries can be sensitive. The app has no developer account system, advertising, analytics, or cloud sync, and the current implementation does not transmit these records to us.
3. Optional menstrual and excused-day entries
You may choose to mark menstrual or excused days to keep missed-prayer calculations aligned with the days you mark. This feature is optional, can be hidden, and is used only for prayer-record accuracy.
The app stores these dates locally with your other records, including relevant history and recovery information. They are not used for cycle prediction, fertility tracking, health diagnosis, medical assessment, advertising, or profiling. Removing a calendar mark corrects the record but may leave the earlier change in local audit or recovery history; the full reset control clears the app’s stored history.
4. Local storage, backups, and exports
On iOS and Android, the app stores its state in a local database. The web build uses browser storage. The current app database and exported JSON backups are not encrypted by QAZA E UMRI, so protect your device and any exported files.
The app can create a JSON backup containing prayer records, optional menstrual-day entries, settings, history, and recovery information. Export uses your device’s sharing interface, and import uses the system document picker. You choose where a backup is sent or stored. A selected storage, sharing, or backup provider then handles that copy under its own terms and privacy policy; QAZA E UMRI does not receive it.
Your operating system or device-transfer service may also include app data in device backups, depending on the final app configuration and your device settings. Those backups are separate from QAZA E UMRI and are controlled through your device or backup provider.
5. Reminders and permissions
If you enable daily or Qaza-goal reminders, the app asks for notification permission and schedules reminders locally on your device. The current app does not use remote push messaging. Notification text may be visible on your lock screen depending on your device settings.
Prayer-time reminder calculation, location access, and cloud-based notifications are not part of the current implementation. If they are added later, this policy and any required in-app disclosure will be updated before the feature is enabled.
6. Website visits
This website contains no analytics scripts, advertising trackers, contact forms, embedded third-party media, or cookies set by our site code. Fonts and page assets are served with the website.
This website is hosted through GitHub Pages, a service provided by GitHub, Inc. GitHub may process ordinary request information such as IP address, browser information, requested page, and request time to deliver and secure the site. GitHub describes its handling of personal data in the GitHub General Privacy Statement. Website hosting does not give QAZA E UMRI or GitHub access to app records stored on your device.
7. Contacting support
If you email us, we receive your email address, message, and any attachments you choose to send. Email providers process that correspondence to deliver it. We use it to respond to your request, not for marketing.
Please do not send prayer histories, menstrual dates, backup files, passwords, or other sensitive information. Remove personal details from screenshots and include only what is needed to explain the issue.
8. Retention and deletion
Local records remain on your device until you edit them, use the app’s full reset control, clear the app’s storage, or remove the app. Individual prayer and Qaza history entries can be edited or deleted, while some changes are retained locally in audit or recovery history so that recalculation and restoration do not silently destroy records. Full reset clears the active database, recovery snapshot, and migrated legacy state on that device.
We cannot access or remotely erase records stored only on your device. Copies in exported files, device backups, or third-party storage must be deleted through the place where you saved them. For support correspondence, request deletion by emailing us. We keep it only as long as needed to address the request and meet applicable legal requirements, subject to the email provider’s backup retention.
9. Sharing, sale, and security
We do not sell personal data. The current app does not send prayer records or optional menstrual-day entries to us or to third parties. Information leaves the app only when you deliberately export or share a backup, or when your operating system or device service creates a backup or transfer copy under your settings. Website and email providers process only the limited information described above. Information may also need to be disclosed when legally required.
Use a device screen lock, review lock-screen notification settings, keep the device updated, and protect exported files. No storage method can be guaranteed completely secure.
10. Future cloud sync and policy changes
Google or Apple account sync is only a future design interface in the current code; it is not active. Any future sync will be off by default and require an explicit choice after we explain what is sent, why, where it is stored, how it is protected, and how it can be deleted. Local records will not be silently enrolled.
We will update this page when practices change and revise its date. New collection or sharing of sensitive information will be explained before it takes effect, with consent where required.