Miqat privacy
Effective date: .
Miqat helps you organize the habits you add around prayer times. It does not record whether you perform prayers. You do not need to create a Miqat account to use the app.
This page explains local app data, purchase services, optional usage and error reports, and how to contact us about your data.
Developer, operator and contact
Miqat is developed and operated by Mohamed Hamza. For privacy requests, questions, or support, email miqatappsupport@gmail.com.
Habits, history and settings
Your habits, intentions, notes, completion history, settings and selected location are stored on your device. Miqat does not provide cloud synchronization or its own server backup for this data. Your device's backup settings may apply independently of Miqat's features.
You can erase app data in settings. Restore purchases does not recover deleted habits or history; it concerns Pro ownership only.
Location and reminders
You can select a city manually or allow device location to help select it. Prayer times use your selected location and calculation method. Hijri dates use the Umm al-Qura calendar. Optional reports do not contain your coordinates or location searches.
You choose whether and when each habit should have a reminder. If you decline location permission, manual city selection remains available. Declining notification permission does not prevent habit tracking.
Pro verification and purchase data
Pro on Google Play is a one-time purchase, not a subscription. Before the first connection to the purchase service to show prices, buy, or restore Pro, Miqat presents an explicit connection choice on the Pro screen. No initial request is sent before explicit permission; continuing free, closing, or going back preserves free use and legitimately verified local offline Pro ownership, and connection can be allowed later from the Pro screen. Purchase processing is separate from optional usage and error sharing; turning optional sharing off neither stops nor substitutes for purchase-service permission.
The purchase service receives a random billing identifier and available transaction information and status, such as the product, purchase token and Pro ownership. When enabled, it also processes technical purchase-service data, such as app, billing SDK and operating-system versions, device model and brand, device languages, store country, connection timestamps and whether the app is foregrounded or backgrounded. This data supports ownership verification, purchase-service operation and its reporting. Habit contents and notes are not sent with it. Miqat does not link the billing identifier to the optional analytics identifier.
Country may come from transaction information or, when that is unavailable, be inferred from the connecting IP address used for the purchase service. This is not device-coordinate collection, but it does involve connection information. We do not claim that the connecting IP address is never processed.
RevenueCat processes data for the purchase service in the United States. This does not mean that every provider processes all data exclusively in one country. See RevenueCat's privacy policy. Google Play also processes transaction and payment information under its own policies. Miqat support will not ask for your store password, payment-card details or verification codes.
Purchase records are retained to support ownership verification, restoration and transaction support, under the service's and store's policies. Uninstalling Miqat, erasing its data or disabling analytics does not delete these providers' purchase records or request a refund. Contact us about purchase-service data; we review what can be identified and deleted and explain applicable limitations.
Usage and error sharing — your choice
Sharing is off by default. These reports are sent only after your explicit agreement. You can continue without sharing and change your choice later under Settings → Privacy and support. Declining or disabling sharing does not restrict free features.
If you agree, usage signals are limited to creating a habit, recording a habit, and choosing Update or Later, together with the app build number, the update choice where relevant, and a random installation identifier created after agreement and deleted when sharing is disabled. This identifier does not make the data fully anonymous. Miqat does not create profiles for these signals or link them to purchase data or error reports.
Error reports contain a short, fixed error category, its location in the app's code, the report time, app version and runtime environment. They do not include raw exception messages, variable values, database contents or a trail of navigation steps.
Optional sharing does not include habit names, intentions, descriptions, notes, values or history; location or search text; session recordings or screenshots; or device and account identifiers. It does not collect past events from before agreement. Usage events are not saved for later offline retries, so events may be lost without connectivity.
Disabling sharing stops new collection and sending and discards pending reports without sending them. It does not erase reports previously received by the services or guarantee immediate removal from backups.
Who receives optional reports?
- PostHog — European Union region: processes the limited usage signals above. The retention window is one year, and expired data may remain longer before deletion.
- Sentry — European Union region: processes sanitized error reports. Its retention window is 90 days during the error service's initial trial and 30 days for new reports on its free plan. Moving to the free plan does not automatically shorten retention for older reports.
Network requests also carry connection information providers need to handle them, including the connecting IP address. Excluding location and identifiers from a report payload does not mean that the network or service provider never processes connection information.
Public website and update checks
Miqat's public pages at miqat.mohamedhamza.dev are hosted on Cloudflare. Remote update-policy checking is not enabled or live; if and when enabled, fetching the update policy will send a request to the host. Visiting these pages or fetching the update policy (if and when enabled) sends a request to Cloudflare, which may process connection addresses and technical request information under its settings and policies, with host request-log retention depending on provider settings and policies. This is separate from optional in-app usage and error sharing. Update-policy requests do not contain habit contents.
Support correspondence and data requests
When you email miqatappsupport@gmail.com, the support mailbox processes your address, message and any attachments you choose to provide so we can respond. Messages pass through email providers, including Google for the support mailbox. Opening an email app from Miqat does not automatically send a message or attach your habits.
We keep support correspondence while handling your request, then delete it and its attachments within 90 days of closing it, unless limited information is needed for an ongoing dispute or a specific legal obligation. You can ask for earlier deletion; we explain any constraint that prevents it. This applies to Miqat's support mailbox, not a promise that store purchase records or the email provider's internal copies are deleted on the same schedule. You can ask about access, correction or retention of your data. Limited information may be needed to verify your connection to the data. We explain what could be located or acted on and any limitations; we cannot promise to associate every technical report with an identifiable individual.
Erasing local data, withdrawing agreement to optional reports and requesting deletion of previously received data are different actions. For store or payment records, you may also need to contact Google Play.