Privacy Policy

Prayer Time Offline (Namoz Vaqti) · last updated 21 October 2026

The app has no account to sign into and no advertising. Prayer times are still worked out entirely on your phone. Since version 1.1 the app does send crash reports and a small amount of anonymous usage information — and never your location. This page says exactly what that means.

What changed in version 1.1

Versions 1.0 and earlier sent nothing at all. That had a cost we only discovered after release: two mistakes in the prayer-time calculation — one in Andijan, one in Riyadh — were found only because users noticed the app disagreed with the adhan and took the trouble to write in. Every other user affected by the same mistake simply had wrong times and no way for us to know.

Version 1.1 adds crash reporting and a small number of specific measurements so that the next such mistake is visible to us without anyone having to report it. We used the narrowest form of this we could build, and the rest of this page is the detail.

Your location never leaves the device

Prayer times and the qibla direction are geometry: both are calculated from your latitude and longitude and the position of the sun, entirely on your device. Your coordinates are stored only on the phone, in the app's own storage.

Your coordinates and your city are never included in anything the app sends. This is enforced in the code, not just promised here: the functions that send information accept only fixed values — a calculation method, a school, yes or no — and have no way to carry a place name.

One honest exception, because it would be easy to leave unsaid: anything that connects to the internet reveals an IP address, and Google derives an approximate location from it before discarding the IP. We never send it, and we cannot prevent it while crash reporting exists at all. This page used to say that location was kept at country level. That was wrong: by default Google Analytics keeps the nearest city, and it did so for this app until 6 October 2026, when we switched that off. Since then only the country is kept. The same switch also stopped Analytics recording the device model and the exact system version with usage; crash reports still carry them. It is listed as “approximate location” on this app’s Google Play data safety page for exactly this reason.

You can turn location off altogether and pick a city from a built-in list instead. The app then never asks the system for your position.

What the app sends

• Crash reports. If the app crashes, we receive the technical details of the crash: where in the code it happened, the device model and the operating system version.
• Performance data. How long the app takes to start and to draw its screens.
• Basic usage, recorded by Firebase itself: that the app was installed and opened, how long it was in use, the app version, the operating system and its major version, and the phone’s language — and on Android, that the app was removed.
• Which calculation convention is in use — the method and the school — and whether you changed it yourself rather than accepting the default, and to what. This is the measurement that matters: if many people in one region keep changing away from the default, the default for that region is wrong.
• Calibration. If you fit the times to your mosque’s timetable, the twilight angles that came out of it, rounded to a tenth of a degree.
• Taps on the calculation row on the main screen.
• Permissions: whether the app may currently show notifications, set exact alarms and use your location — yes or no for each, never the location itself.
• Prayer alarms that rang: which prayer, whether it was the reminder before it, whether it was set as an alarm or a notification, and whether it could actually be seen or heard — but not when. It is counted the next time you open the app, never as the alarm rings: a report sent at that moment would carry the prayer’s exact time, and prayer times hint at where a phone is. (Android versions 1.9.0 to 1.9.2 did send it as the alarm rang; 1.9.3 stopped that.)
• The tasbih: that it was used that day, and whether it was the built-in after-prayer set or a dhikr you saved yourself — at most once a day for each. Never the name you gave a dhikr, and never how many you counted.
• The rating request: that the app asked the system to show its rating prompt, and on how many separate days the app had been opened by then.
• The tip screen: that it was opened and from where, and whether the store could show its prices. If you leave a tip, Apple or Google handles the payment, and Firebase records that a purchase was made, which amount and its price.
• Sharing and contact: that the share sheet, or the Telegram or email link, was opened — not what you shared or wrote.
• An approximate location, derived by Google from the IP address of the connection — see above.

That is the complete list. The app never sends your coordinates or your city, anything you type, or anything about other apps on your phone. All of it, crash reports included, can be turned off at once under Settings → Send diagnostics.

Identifiers

The app creates an anonymous sign-in with no name, email or password behind it. It exists for one reason: so that one phone crashing forty times can be told apart from forty phones crashing once. It cannot be traced back to you, and deleting the app ends it.

No advertising identifier is collected. The part of the analytics software that would read it is not included in the app at all, and there is no advertising, no ad network and no cross-app or cross-site tracking of any kind.

Who processes it

Crash reports and the measurements above are processed by Google Firebase (Analytics, Crashlytics, Performance Monitoring and Anonymous Authentication) on our behalf, under Firebase's privacy terms. We operate no servers of our own. On Android the app now holds the INTERNET permission, which it did not before, solely for this.

City names

To show a city name rather than a pair of numbers, the app asks the operating system to turn coordinates into a place name — Apple's MapKit geocoding on iOS, the system geocoder on Android. That request is handled by Apple or Google under their own privacy policies. Searching for a city by name in the place picker uses the same service. The timetable itself never needs it.

Notifications and alarms

Prayer alarms and reminders are scheduled locally by your device. Nothing is pushed from a server, and no notification token is created or shared.

Children

The app is suitable for all ages. It asks for no personal information from anyone, including children, and the diagnostic data described above is not linked to any identity.

Changes

If this policy ever changes, the updated version will be published on this page with a new date. Any change that affects what data leaves your device will also be described in the app's release notes — as this one is.

Contact

Questions, or a disagreement between the app's times and your local mosque's timetable:

• Telegram: @pc_geek_uz
• Email: gulomovmazizullo@gmail.com