Privacy Policy

Effective date: 18 August 2026

This Privacy Policy explains how the Hayya mobile application ("Hayya", "the app", "we", "us") handles information. By using Hayya you agree to this policy.

1. Information we collect

We do not collect any personal information. Hayya has no user accounts, no login, and no backend servers of ours that store your data. We do not receive your location, your prayer records, your settings, or any identifier from your device.

We run no servers of our own, but the app does make two kinds of outgoing request, both concerned only with keeping the app up to date. To let us ship fixes without waiting on an app store review, Hayya uses Expo's over-the-air update service, which it asks on each launch whether newer app code is available. Separately, about once a day it fetches a small file from this website to find out whether a newer version of the app has been released on the App Store or Google Play. See section 6 for exactly what each involves.

2. Information processed on your device

Hayya needs certain information to work, but this information stays on your phone and is never transmitted to us or to any third party:

Location

Hayya uses your location solely to calculate accurate prayer times for where you are. You can provide it in two ways:

• Device location (GPS): read from your device only while you are using the app, and used on-device to compute prayer times.
• Manual city search: you type a city name, which your device's operating system location services (provided by Apple or Google) resolve to coordinates.

Your location is used for calculation on your device and to store your chosen prayer settings locally. It is never sent to us and we never see or store it.

App data (settings and prayer history)

Your preferences (calculation method, madhab, alarm sound, theme, adhan language and similar), along with your prayer log — including which prayers you accepted or declined, your streak, and any written reasons you enter when declining — are saved in local storage on your device only. This data never leaves your phone and is not accessible to us. Uninstalling the app deletes it.

Notifications and alarms

Prayer alarms are scheduled locally on your device using its notification and alarm systems. We send no push notifications, and no server is involved in your alarms firing — they work with no connection at all.

3. Information we do NOT collect

• Name, email address, phone number, or contacts
• Advertising identifiers
• Your location, prayer history, streak, settings, or anything you write in the app
• Any behavioural tracking or advertising/analytics SDK inside the app
• Any data shared with advertisers or data brokers

One clarification, so this list isn't misleading: because the app contacts Expo's update service on launch (section 6), Expo can count app launches and see the IP addresses those launches come from. We do not use that as an analytics product, but it is aggregate usage information that exists as a by-product, and we would rather say so than claim none exists.

4. Device permissions and why they are used

• Location — to calculate prayer times for your location.
• Notifications — to show prayer alarms.
• Exact alarms / scheduling — so prayer alarms fire precisely at prayer times, the app's core purpose.
• Full-screen intent & display over other apps — to present the full-screen "call" alarm over the lock screen so you can pray on time.
• Run at startup — to re-schedule your alarms after the device restarts.
• Wake lock & vibrate — so the alarm can wake the screen and vibrate.

Granting these permissions does not send any data to us; they only allow the app to function on your device.

5. Third parties

We do not sell or share your personal data with third parties, and we do not integrate any advertising or analytics SDK. Three external services are involved in running the app:

• Your device's operating system (Apple or Google) provides the location and geocoding that turn a city name or GPS reading into coordinates. Their handling of that request is governed by your device maker's privacy policy.
• Expo (Expo, Inc.) provides the over-the-air update service described in the next section, acting as a processor on our behalf.
• GitHub (GitHub, Inc.) hosts this website, including the small file the app fetches to learn the latest version on the app stores. That request goes to GitHub's servers and is subject to their standard web logging.

6. App updates

Hayya makes two kinds of network request of its own, and both exist only to keep the app current. Neither one sends anything about you.

6a. Over-the-air code updates (Expo)

Hayya is built with Expo, and uses Expo's update service so that fixes can reach you without waiting for an app store review.

What happens: when the app launches, it asks Expo's servers (u.expo.dev) whether a newer version of the app's JavaScript code is available for your app version. If so, it downloads it and applies it the next time the app starts.

What Expo can see: as with any web request, your IP address (which approximates your city, not a precise location) along with basic technical details needed to answer it — your app version, runtime version, and platform. Expo can therefore count app launches and unique devices in aggregate.

What is never sent: your GPS coordinates, chosen city, prayer times, prayer log, streak, written notes, settings, or any account or advertising identifier. None of this leaves your device, and none of it is included in the update check.

Offline: the update check never blocks the app from starting. If you have no connection, or block the request, Hayya works exactly as it always does — prayer times are still calculated on your device and alarms still fire.

Expo's privacy policy is available at expo.dev/privacy.

6b. Checking for a new store version

Some improvements — anything that changes the app's underlying native code — cannot be delivered over the air and are only available by updating from the App Store or Google Play. So that you are not left on an old version without knowing, the app checks whether a newer one has been published.

What happens: at most once a day, the app requests a small file from this website (saiyedrushan.github.io/hayya-site/version.json) listing the latest version on each store and what changed in it. If that version is newer than the one you have installed, the app shows you the list of changes and offers to open the store. Tapping "Later" dismisses it; nothing is installed without you choosing to.

What GitHub can see: it is an ordinary request for a public file, with no query string, no body, and no identifier of any kind attached. As with any web request, GitHub's servers see your IP address (which approximates your city, not a precise location) and the standard technical headers a request carries. We receive no report of these requests and cannot tell who fetched the file.

What is never sent: exactly as above — no coordinates, city, prayer times, prayer log, streak, notes, settings, or identifiers. The request asks a question and sends nothing about you in order to ask it.

Offline: this check never blocks the app from starting, and it is skipped entirely while a prayer alarm is on screen. If it fails, or you block it, nothing happens at all — you simply are not told about the new version.

7. Children's privacy

Hayya is suitable for all ages and does not knowingly collect any information from anyone, including children.

8. Data security and retention

Your prayer data, location, and settings never leave your device, so they are protected by your device's own security, and we retain nothing of them because we never receive them. You can clear all app data at any time by uninstalling Hayya. Connection metadata from the two update checks is retained by Expo and GitHub under their own policies, not by us.

9. Changes to this policy

We may update this policy from time to time. Material changes will be reflected on this page with a new effective date.

10. Contact

If you have any questions about this Privacy Policy, contact us at rushan52@gmail.com.