1. Who we are
NamazClick is a prayer-time app published by an individual developer under the name NamazClick (“we”, “us”), Moradabad, Uttar Pradesh, India. For the purposes of India's Digital Personal Data Protection Act, 2023 (the “DPDP Act”) and the DPDP Rules, 2025, we are the Data Fiduciary for the personal data described here.
Contact: [email protected]. The person who answers questions about personal data and handles grievances is our Grievance Officer, Mohd Zubair ([email protected]).
2. The short version
Most of NamazClick works on your phone and sends nothing anywhere: your jamaat times, quiet windows, call guard, reminders and settings. Two features need our server, and both are optional:
- Snap: you photograph a mosque's timetable board, the times are read by an AI service (Claude, from Anthropic), you check them, and you can share them on the mosque's page for others.
- Mosques: a map and list of mosques near you, each mosque's times, following a mosque so its times update in your app, and reporting a problem.
You can use NamazClick without either of them by entering your times yourself. We have no accounts, and we do not ask for your name, phone number or email address in the app. The app contains no advertising, analytics or crash-reporting software.
This website is a set of static pages. It sets no cookies and runs no analytics. Our hosting provider (Cloudflare) processes technical request data such as your IP address to deliver the pages and protect them against abuse; see section 10.
3. What stays on your phone
The app keeps the following in its private storage on your phone. Unless a row says otherwise, none of it is sent to us.
| Data | Why |
|---|---|
| Your jamaat times, Jummah choice, mosque name, quiet-window lengths | To know when to decline calls and when to remind you |
| Settings: call guard on or off, theme, language, message to callers, reminders | To remember your choices |
| Family list (Android): the names and numbers you pick from your contacts | So these people can still call you during a jamaat |
| Calls list (Android): number, contact name (if you allowed contacts), time and prayer of calls that arrived during a quiet window | So you can call back or send a text after you pray. Kept for up to 7 days or 500 entries. |
| Repeat-caller counter (Android): a one-way hash of the number and the call times | To let someone through who calls again and again |
| Approximate location, rounded to about 1 km, if you asked for calculated times | To calculate prayer start times for your area on the phone |
| The list of mosques you follow (also sent to our server; see section 4), and that you accepted the terms for sharing photos and reports | To refresh followed mosques' times and not ask you again |
| If you used Hide this contributor: how many contributors you hid (a number only), and a random viewer token in the phone's secure storage (see section 4) | To show the count in Settings, and to leave hidden contributors' times and photos out |
| Your install ID, in the phone's secure storage (also sent to our server with Snap, follow, report, hide and delete requests; see section 4). The app never shows it: it is the key to your data. The Privacy screen shows a deletion code made from it instead, which cannot be turned back into the ID. | To link your follows, reports, scans and hidden contributors so you can delete them |
On Android the app is set not to be included in Google's cloud backups. On iPhone, Apple's own device backup (iCloud or a computer) may include app data, as it does for any app; that backup is controlled by you and Apple.
4. What reaches our server, and why
Only when you use Snap or Mosques does the app talk to our server. This is everything it sends and what we keep:
| Data | When | Why |
|---|---|---|
| Install ID: a random code the app creates on your phone. It is not your name, number, email, advertising ID or phone serial number. Our server stores it only in a scrambled (keyed-hash) form. | With each Snap, follow, report, hide or delete request. Not with map searches or mosque pages. With it, our server also stores the deletion code shown in the app (section 13). | To link your follows, reports, scans and hidden contributors; to limit how often one install can scan, report or hide (so the service cannot be abused); and so you can delete your data |
| Board photo: cropped to the board, re-saved on your phone so its hidden details (EXIF: camera, time, GPS) are removed, and made smaller | When you send a scan | To read the times, and (only if no people are visible) to show the board on the mosque page |
| Location at scan time: one precise reading of where the phone is, its accuracy, the time of the photo and your time zone | When you send a scan | To find the mosque you are standing in, or to place a new mosque on the map; to check times against the sun for that place. For a photo you choose from your gallery, the reading is where you are when you send it, so it is only used to match a mosque already on the map, never to place a new one. |
| Times you confirm and, for a new mosque, the name you give it | When you tap Done after checking the times | To publish the mosque's timetable for everyone |
| Map position: your current position or the point the map is centred on, and the search radius (1 to 5 km) | When you open Mosques or move the map | To list nearby mosques. Used to answer the search; we do not save it to your install ID or keep a history of searches, also when the request carries your viewer token (below). |
| Follows: which mosques you follow | When you follow or unfollow | To keep your followed mosques' times up to date |
| Reports: the mosque, a reason (wrong times, wrong location, duplicate, shows people, not a mosque, other) and an optional note of up to 500 characters | When you report a mosque | So we can review and fix or remove content |
| Hidden contributors: when you tap Hide this contributor on a mosque page, the app sends only which mosque and whether you mean its times or its photo. Our server finds the anonymous install behind that content and stores your scrambled install ID, theirs, and that mosque's id and location. The app never learns who they are, they are not told, and nobody else can see whom you hid. | When you hide a contributor, or tap Show all again | To hide that person's times and photos from you at mosques within 5 km of where you hid them (5 km is the app's largest search radius; hiding them at a mosque further away covers 5 km around that one too). If several people hide the same contributor, our moderators review that contributor's uploads (to keep the service free of abuse). |
| Viewer token: a random code our server gives your phone the first time you hide someone. It is not your install ID and says nothing about whom you hid. Our server stores it only in scrambled (hashed) form. | Only after you hid someone: inside map-search and mosque-page requests (not in a header or web address), until you tap Show all again or delete your data | So those requests can leave out the contributors you hid, without sending your install ID |
| Technical and security logs: time, which feature was used, the result or error, rate-limit events, the install ID and IP address in scrambled (hashed) form, and, for scans, timetable submissions and reports, which scan and mosque it was about (never for follows). With each scan we also keep the scrambled network address, so that one network cannot count as several people when times are confirmed; it is deleted with the scan. Our hosting provider's own request logs may also contain the IP address. | With each request | To keep the service running, detect and investigate abuse and unauthorised access, and meet legal duties |
Your consent. We process this data because you choose to use these features. Before your first scan the app asks you to accept the terms for sharing photos and times, and your phone asks your permission for the camera and location. You can stop at any time: stop using Snap and Mosques, unfollow mosques, turn off the permissions in your phone's settings, or delete your data (section 13). Withdrawing consent does not affect processing that already happened, and it does not stop the rest of the app from working.
Please do not write personal details about yourself or anyone else in a report note or a mosque name.
5. Snapping a mosque board
- On your phone. The document scanner crops the photo to the board. (A plain camera mode is available for LED and TV screens; frame just the screen.) The app checks the photo is sharp enough, re-saves it as a new image without its hidden details (EXIF, including any GPS), and makes it smaller.
- Reading the times. Our server sends the photo to our AI service, Claude from Anthropic (section 10), which reads the prayer times and tells us whether any people are visible. Anthropic receives the photo and our instructions, not your install ID or your location. Text written on a board is treated as data, never as instructions.
- You check. The app shows the times it read, with any doubtful ones highlighted. Nothing is shared until you confirm.
- Photos with people. If the AI service finds that people are visible, the photo is never stored or shown to other users. If it misses someone, anyone can report the photo; it is hidden at once and deleted within 24 hours. The times you confirm can still be used.
- Board photos without people may be shown on the mosque's page, so others can check the times against the board. They are delivered through links that expire after about an hour.
The app crops photos to the board; it does not blur faces. The check for people is automatic and can miss someone. Anyone can report a photo with the “Shows people” reason: it is hidden at once and deleted within 24 hours unless a moderator finds no one in it.
6. Location
- At scan time. When you send a scan, the app takes one precise location reading while it is open (on Android, “precise location”, foreground only). We treat that point as the mosque's location: it is used to match the mosque within about 300 metres, or to place a new mosque. Once you submit the scan, only the mosque's point is kept; the reading itself is deleted then, or within 24 hours if you don't submit. It is not used for anything else.
- Photos from your gallery. If you choose a board photo you took earlier, the app takes the reading when you send it, which may be far from the mosque (at home, for example). That reading is used only to match a mosque already on the map; a gallery photo can never place a new mosque.
- On the mosque map. The map shows where you are, and the app sends the position to search for mosques nearby (section 4). We do not keep a history of these searches.
- Calculated start times (optional) use one approximate reading, rounded to about 1 km, and are calculated on the phone. That reading never leaves the phone.
- Never in the background. NamazClick does not ask for background location and does not track you. We keep no record of where you go.
Your phone's location service (Google on Android, Apple on iPhone) produces the reading under its own privacy terms.
7. What other people can see
Mosque pages are public to every NamazClick user: the mosque's name, area and point on the map, its timetable, how many people confirmed it, when it was last updated, and a board photo if one without people exists. Contributions are anonymous: nobody can see who scanned, confirmed, followed or reported a mosque, or who hid whom, and your install ID is never shown. If you hide a contributor, you see that their content is hidden at mosques within 5 km of where you hid them, but never who they are. One limit to know about: someone who hides your times or photo can tell which other times and photos within 5 km of that mosque came from the same anonymous person (and, by hiding them again at those mosques, a little further each time). Each of these steps costs them a hide, and hides are limited to 30 a day. They still never learn who you are.
8. Permissions and why we ask
The app asks for each permission when it is first needed, and explains why. You can refuse any of them.
Android
- Call screening role (“caller ID and spam app”): lets Android ask NamazClick, on the phone, whether an incoming call should ring during a jamaat. Only one app can hold this role at a time.
- Do Not Disturb access: to quiet notifications and other sounds during a jamaat. Calls you allow still ring.
- Alarms and reminders (exact alarms): so the quiet window starts and ends on time.
- Notifications (optional): for the reminder 10 minutes before each jamaat.
- Camera (optional): to photograph a mosque board. On many phones the document scanner is provided by Google Play services and runs on the phone.
- Location (optional): precise location while the app is open, when you send a scan or use the mosque map; approximate location for calculated times.
- Contacts (optional): asked only when you add people to the family list. See section 9.
- Start at boot: so your quiet windows keep working after the phone restarts.
The app does not ask for permission to read your call log, send or read SMS, use the microphone, read your photo gallery, or use your location in the background.
iPhone
Apple does not allow apps to block calls, so the iPhone app does not touch your calls. It may ask for notifications (reminders), the camera (to photograph a board), and location while using the app (scans, the mosque map and calculated times). The Namaz Focus is something you set up yourself in the iPhone Settings app; NamazClick only guides you and cannot see or change it.
9. Calls, contacts and messages
- Calls (Android). When a call comes in, Android gives NamazClick the caller's number. The app decides on the phone whether to let it ring. Calls outside a jamaat window are not recorded. Calls inside one are added to the calls list on your phone. No call information is ever sent off your phone.
- Contacts (Android). Without the contacts permission, Android never asks NamazClick about calls from your saved contacts, so they always ring. If you allow contacts (when adding family-list people), the app reads only what it needs on the phone. Granting it means calls from saved contacts are also declined during a jamaat, except the family list and repeat callers. Your contacts are never uploaded.
- Messages. “Send text” opens your own SMS app with a message filled in. Nothing is sent until you tap send in that app. NamazClick cannot send, read or see your messages.
10. Companies that process data for us
These companies process data on our behalf, under contracts that limit them to providing their service to us. We do not sell data to anyone or share it for advertising.
| Company | What it does | What it receives |
|---|---|---|
| Supabase (on Amazon Web Services) | Our database, file storage and server functions, in Mumbai, India (AWS ap-south-1) | Everything in section 4 |
| Anthropic (Claude API) | Our only AI service. Reads prayer times from board photos and says whether people are visible. A second Claude model looks again when a photo is hard to read. | The board photo and our instructions. Anthropic does not train its models on content sent through its commercial API; it may keep it for a limited time for safety and abuse monitoring, as its terms allow. |
| Google (Maps SDK for Android) | Draws the mosque map in the Android app | Map requests from your phone, including IP address, device and SDK details, map movements, crash details within the map software, and a pseudonymous identifier Google uses to count its users. Google processes this under the Google Maps Platform terms and Google's privacy policy. |
| Apple (Apple Maps) | Draws the mosque map in the iPhone app | Map requests from your phone, under Apple's privacy policy |
| Google (ML Kit document scanner, Android) | Runs the document scanner on the phone | The scan itself stays on the phone. ML Kit sends Google technical information such as the device model, app version, performance and error codes, and a per-installation identifier, for diagnostics. |
| Cloudflare | Hosts this website | Website request data (IP address, browser, page requested) |
Directions open Google Maps or Apple Maps with the mosque's location. What happens in those apps is covered by Google's or Apple's privacy policy. The app is distributed through Google Play and the Apple App Store (and TestFlight for iPhone testers), which process data about your download and your account under their own policies. If you join our test, Google or Apple may share your tester email address and any feedback you send through them with us.
Map and mosque data include information from OpenStreetMap; see attribution. No data about you is sent to OpenStreetMap.
11. Where data is stored and processed
Our database and stored photos are in India (Mumbai, India (AWS ap-south-1)). Every night an encrypted copy of the database (never the photos) is made as a backup and kept for 7 days with GitHub (Microsoft), in the United States; it is locked with a key only we hold, so GitHub cannot read it. Reading a photo with Claude (Anthropic), and map requests to Google or Apple, may be processed on those companies' servers outside India, including in the United States. The DPDP Act allows this, subject to any restrictions the Government of India may set, and we will follow them.
12. How long data is kept
| Data | Kept for |
|---|---|
| Photos in which people are visible | Never stored when our automatic check finds people. A photo reported as showing people is hidden at once and deleted within 24 hours. |
| The exact location reading taken at scan time | Deleted when you submit the scan (the mosque's point is kept instead), or within 24 hours at most. |
| Scan records: the board photo without people, the times read, warnings, the AI model used, and the scrambled network address | Up to 400 days (about 13 months) from the scan, then deleted. Sooner if you delete your data, or if the photo is removed after a report. |
| Follows | Until you unfollow or delete your data |
| Hidden contributors and the viewer token | Until you tap Show all again (Settings → Privacy and data → Hidden contributors) or delete your data. A hide is also deleted when the hidden contributor deletes their data, and when either install has not used our server for 400 days. |
| Install record: the scrambled install ID, the deletion code, and when it first and last used our server | Until you delete your data, or 400 days after it was last used. If we blocked an install for abuse, only the block record (scrambled ID and reason) is kept while the block lasts. |
| Which install confirmed which timetable | While the vote can still matter: the link to your install, and the vote's link to its scan, are removed 30 days after a timetable is replaced; the link to your install is removed from any vote after 400 days, and at once if you delete your data. The scan record itself (with your install link and the mosque) is kept up to 400 days like every scan record, unless you delete your data. |
| Reports | Until we have dealt with them (closed automatically after 90 days at most), and then 365 days so we can spot repeated abuse; sooner if you delete your data |
| Mosque pages: name, location and the confirmed timetable | As long as the mosque is listed. These are shared community information. If you delete your data, they stay on the mosque page but are no longer linked to your install ID. |
| Technical and security logs | 400 days (at least one year, as the law requires), then deleted, including after you delete your data; deleting your data removes from them which mosques and scans you touched. The DPDP Rules, 2025 (Rules 6 and 8) require this so that unauthorised access can be investigated. Daily rate-limit counters are deleted after 7 days. |
| Encrypted backup copies of the database (never photos) | 7 days each, then deleted. A new copy is made every night, so anything deleted from the database, by you or by the schedules above, is gone from every backup within 7 days. |
| Data on your phone | Until you delete it in the app, clear the app's storage, or uninstall the app. Board photos are deleted from the phone as soon as the app has prepared the copy it reads; any left over (for example if the app was closed during a scan) are deleted the next time the app starts, or when you delete your data. |
13. Deleting your data
- In the app: Settings → Privacy and data → Delete all my data. This erases the app's data on your phone, including any board photos left in its temporary storage, and asks our server to delete the follows, reports, scans (including their photos), hidden contributors and viewer token linked to your install ID; other people's hides of your contributions are deleted too. The app then starts fresh with a new install ID. If your phone is offline, the app tells you so you can try again, or delete on the phone only: the app then keeps just the old install ID, in its secure storage, and finishes the deletion on our server the next time it is online. Keep the app installed until then: if you uninstall it first, the server deletion cannot happen, so email us the deletion code that Settings → Privacy and data shows for the pending deletion.
- By email: write to [email protected] with the subject “Delete my data” and the deletion code from Settings → Privacy and data. Full steps, and what we need to find your data, are on the delete-data page. Never send us your install ID itself.
Uninstalling the app does not delete data on our server, because we cannot tell that you uninstalled. Use “Delete all my data” first, or email us.
14. Security
- All traffic between the app and our server is encrypted (HTTPS).
- Our provider encrypts stored data. Every database table is protected by access rules, the app can reach only the functions it needs, and the key for the AI service never leaves our server.
- Photos are kept in private storage and shown only through links that expire after about an hour.
- Requests are limited per install and per network so the service cannot be flooded or misused.
- On your phone, app data sits in the app's private storage and the install ID in the phone's secure storage (Android Keystore, iPhone Keychain).
No system is perfectly secure. If a personal data breach happens, we will tell affected users and the Data Protection Board of India, as the DPDP Rules, 2025 require, and report to CERT-In where the law requires.
15. What we do not do
- We do not sell or rent your data, or share it for advertising.
- We do not show ads or use advertising identifiers.
- We do not track you across apps or websites, or build a profile of you.
- We do not read your messages, listen to your calls or upload your contacts.
- We do not use your photos or data to train AI models, and our AI provider, Anthropic, does not either (section 10).
16. Children
NamazClick is a general-audience app for people aged 13 and over. It is not designed for children under 13, and it has no ads, tracking or behavioural monitoring of anyone.
Everything that sends personal data to our server is for people aged 18 or over, because India's DPDP Act, 2023 treats anyone under 18 as a child: uploading a board photo (Snap), sharing times, reporting a problem and following a mosque. You confirm you are 18 or over when you accept the terms in the app, before the first time you use any of them. Anyone can use the rest of the app, which works on the phone and sends nothing to us: entering times yourself, the quiet windows, reminders and the call guard. The Mosques map sends only the area being looked at to find nearby mosques, which is not stored or linked to you (section 4).
If we learn that someone under 18 has sent us a photo, times, a report or a follow without verifiable consent from a parent or lawful guardian, we will delete it. Parents can write to us at [email protected].
17. Your rights in India (DPDP Act, 2023)
Under the DPDP Act, 2023 and the DPDP Rules, 2025 you have the right to:
- get a summary of the personal data we process about you, how we process it, and who we share it with;
- have it corrected, completed, updated or erased;
- withdraw your consent at any time, as easily as you gave it;
- have a grievance answered by us;
- nominate another person to exercise these rights if you die or become unable to; and
- complain to the Data Protection Board of India after using our grievance process.
Most of these you can do yourself in the app: change your times, unfollow mosques, or delete all your data. For anything else, write to the Grievance Officer. Because we have no accounts, we find your data by the deletion code the app shows; the delete-data page explains what to send.
18. Questions and grievances
Write to our Grievance Officer, Mohd Zubair, at [email protected]. We will acknowledge your message within 24 hours and resolve it within 15 days (well within the 90 days the DPDP Rules, 2025 allow). If you are not satisfied, you may complain to the Data Protection Board of India.
19. Changes to this policy
We will post any change on this page and update the effective date. If a change affects how your data is handled, we will tell you in the app before it applies and ask again where the law requires. Features that are not in the app today, such as accounts, crash reporting or sending texts automatically, will not start without an update to this policy. This policy is written in English; Hindi and Urdu versions will follow, and the English version applies if they differ.
Effective date: 2026-10-07.