Privacy Policy — Masjid Locator for the Car

Last updated: 14 November 2026

This page covers the Masjid Locator for the Car app (id.imajiedu.masjidlocator) for Android, on phones and on Android Auto, and for iPhone, iPad and Apple Watch. The sections below describe the Android app; the iPhone, iPad and Apple Watch section describes what is different on Apple devices. There is no CarPlay version yet. The short version: there is no account, no analytics and no advertising, the app reads no device identifier, and it sends nothing to us. To find mosques, the app sends your location to third-party OpenStreetMap search services. On Android, when the map is active, Google also receives your location for the map and routes, and Google's map component collects its own identifier and technical data. On iPhone and iPad, the map and routes come from Apple. Prayer times are calculated on your phone. The general Imajiedu policy at imajiedu.com/privasi describes the website and the Imajiedu app and does not apply to your use of this app; the location rounding figures on that page belong to the website, not to this app.

Who is responsible

The app is published by PT Taqwa Amanah Teknologi (Imajiedu). Our address, email and telephone are under Contact at the end of this page.

Data we receive: none

There is no account, sign-up or login. The app has no analytics, crash reporting service, advertising, tracking or purchase of its own, and it reads no advertising identifier, device identifier or install identifier. The one exception is Google's map component: when the map is active, it collects its own identifier and technical data for Google, as described under Google maps and routes.

The app has no Imajiedu server. Your location, the mosques you look for and your settings never reach us. The address imajiedu.id appears only as a contact label inside requests to the mosque search services, and is never contacted. The Kebijakan privasi (Privacy policy) link in the app opens this page in your browser, only when you tap it.

All we see is what Google Play gives every developer: aggregate install and usage figures. If the app stops unexpectedly, Android may send a technical crash report (app version, device model, Android version and the error) to Google Play, depending on your device settings. That report does not contain your name, contact details or location.

How the app uses location

When you open the app on your phone, it asks for approximate and precise location; approximate location alone is enough. If the permission has not been given, the car screen can ask for it too, as described under the car screen. Location comes from Google Play's location service on the phone in a power-saving mode. With precise location allowed, the position is typically accurate to about 100 metres, or better when another app, such as a navigation app, is using GPS at the same time. With approximate location only, Android deliberately gives the app a less exact position (Android describes it as accurate to within about 3 square kilometres), and that less exact position is what the app uses and sends to the search services.

Location is read only while the app is open on the phone screen, or while it is running on Android Auto. On the phone, reading stops when you leave the app. In the car, it continues while this app's Android Auto session is active, which may last for a while after you switch to another app on the car screen. During that time the app asks for a new position about every 2 minutes. It may receive one as often as every 30 seconds when another app is using location, and receives none while the device has moved less than 250 metres. The app does not ask for background location, and the adzan reminders never request a new position.

The speed and direction of travel that come with the position are used on the phone map (the direction arrow and the Bergerak N km/j, moving at N km/h, line) and are kept in memory only while the app runs.

The latest position is stored on the phone after rounding to three decimal places (about 110 metres), together with its time. It is overwritten by each new position and used only to work out reminder times while the app is not open. After 24 hours it is ignored, but it is not erased until a new position replaces it or you clear the app's storage. The unrounded position stays in memory only.

What leaves your device: the mosque search

To find nearby mosques, the app sends a request to the OpenStreetMap Overpass services: overpass-api.de and, if that fails or returns nothing, overpass.kumi.systems and then overpass.private.coffee. These services are run independently by third parties, not by us.

The request contains your phone's latitude and longitude as determined, NOT rounded, and the search radius (1, 3, 5 or 10 km; 3 km by default; if nothing is found and the radius is under 10 km, the search is repeated at 10 km). Like any server, those services also receive your IP address, the time of the request and standard technical data. The app adds a fixed label, "ImajieduMasjid/0.1 (+https://imajiedu.id)", which is the same on every device. No account, identifier or cookie is sent.

A search is sent when the first position arrives; on every new position while no mosque has been found yet; after you move more than 2 km (at most every 90 seconds); every 2, 5 or 10 minutes (5 by default) while the app is active, including when the vehicle is not moving; when you ask for a refresh (Muat ulang, Reload, on the phone, or the refresh button on the car screen); and when you change the radius. The services are tried in turn until one returns mosques, within a limit of about 9 seconds for the whole search, so one search can reach all three services, twice if it is widened to 10 km. What those services log is governed by their own policies.

What leaves your device: Google maps and routes

The Peta (Map) tab on the phone uses Google Maps when the map is active in your version of the app. The map follows your position, so Google receives map image requests for the area around you, together with your IP address. The app does not let Google Maps read your location itself; the position on the map is drawn by the app. When the map is shown, Google's map component (the Maps SDK) also collects data for Google on its own: a pseudonymous identifier specific to the Maps SDK that Google uses to count daily active users, your IP address, device details (Android version, name, model, brand and form factor), the SDK's version and an internal usage attribution identifier, and stack traces and crash metrics from the map component. Google states that it uses this data to maintain and improve Google services.

If you tap a mosque on the map or its card, the app asks the Google Routes API for a driving route. That request contains your current position, not rounded, the mosque's position, and technical data: the app's key, its package name, the app certificate fingerprint (the same for every user), and Android's standard label, which usually names the Android version and device model. Routes are never requested from the car screen.

If the Map tab shows Peta belum aktif (Map not yet active), the app makes no request to Google Maps or Routes at all. Data received by Google is governed by Google's Privacy Policy.

Your position itself is produced by Google Play services on the phone. How Google processes location there, for example Google Location Accuracy, follows your device settings and Google's policy.

Directions to a mosque

When you tap Arahkan (Directions), tap a mosque on the car screen, or tap Directions (Arahkan on an Indonesian device) in a notification, the app opens your map or navigation app with the mosque's coordinates and name. Your own location is not included. From then on, that navigation app's policy applies.

On Android, the only link to a website is Kebijakan privasi (Privacy policy) in the phone's Pengaturan (Settings) tab, to this page on imajiedu.com. It opens only when you tap it, in your device's browser, and the app sends nothing when it opens it, your location included. This page is part of the website, so your visit here is covered by the general Imajiedu policy. The link never appears on a car screen. The app has no in-app browser, no sharing and no uploads. The links on iPhone and iPad are described in the iPhone, iPad and Apple Watch section.

iPhone, iPad and Apple Watch

The iPhone and iPad app works like the Android app, with the differences below. There is no account, analytics, advertising, tracking or purchase, and the app reads no advertising or device identifier. All we see is what App Store Connect gives every developer: aggregate download and usage figures, and technical crash reports if you allow your iPhone to share analytics with developers. Those reports contain no name, contact details or location.

Location: the app asks for While Using the App location only, never background location. Location is read only while the app is open on screen and stops when you leave it. For the mosque list, distances, prayer times and the search, the app reads the position at an accuracy of about 100 metres, with a new position at most every 30 seconds and none while the device has moved less than 250 metres. If you turn Precise Location off in iOS settings, the app receives an approximate position from iOS, and that position is what it uses and sends to the search services.

While the Map tab is shown, Apple's map (MapKit) reads your position itself, continuously and at full accuracy when Precise Location is on, to draw the direction arrow and follow you on the map. This reading is not bound by the 100 metre, 30 second and 250 metre limits above. The app uses the direction and speed from it only for the arrow on screen, on the device; nothing of it is sent to us, and the reading stops when you leave the Map tab or the app.

Mosque search: the same as on Android. The unrounded coordinates, the radius (1, 3, 5 or 10 km) and the same fixed label go to the same three Overpass services, on the same schedule. If the Overpass services have not answered within 8 seconds or find no mosque, the app also searches Apple Maps for "masjid" and "mosque" around your position; that request contains your position, not rounded, and the radius. While Overpass answers in time, this request is not sent.

Map and routes: the Map tab uses Apple Maps, not Google. Apple receives map image requests for the area shown, around your position. If you tap a mosque on the Map tab, the app asks Apple for a driving route; that request contains your position, not rounded, and the mosque's position. If you tap Directions, or a mosque in the Nearby list, the app opens Apple Maps, Google Maps or Waze, whichever you chose, with only the mosque's coordinates and name, not your location. Data received by Apple is governed by Apple's Privacy Policy.

Reminders: three reminders per prayer, each of which can be turned off: before the adzan (1 to 20 minutes, 10 by default), at the adzan, and Get ready to pray after the adzan (1 to 9 minutes, 5 by default), each with its own short tone. The before-the-adzan reminder has a Snooze 5 min button, which sets the same reminder again five minutes later. All are local notifications scheduled on the iPhone for the moments the app worked out, and planned again when the iPhone's time zone changes, with no server and no push notification. A notification may carry the nearest mosque's name and coordinates so that its Directions button works.

Lock Screen, Dynamic Island, widget and Apple Watch: the app keeps a small summary on the iPhone, in a container shared with its widget and Live Activity: the position rounded to three decimal places (about 110 metres) with its time and the iPhone's time zone, the prayer time settings, the prayer times for a few days around that time, and up to three nearest mosques (name, the mosque's exact position, and its distance and direction measured from your unrounded position). So the summary is no vaguer than your position: from a mosque's position, distance and direction, where you were at that moment can be worked out exactly or nearly so. The Live Activity carries that nearest mosque too. If you install the Apple Watch app, the same summary is sent to your watch over Apple's connection between your own devices, and the watch keeps it. The watch app asks for no location and makes no internet request: it shows the prayer times the iPhone calculated and included in that summary, and works out by itself which stage is current, such as the countdown to the next prayer. The Live Activity is updated by the iPhone itself, with no push notification.

Permissions, backups and deletion: the app asks only for While Using the App location and notifications; both can be withdrawn under iOS Settings → Masjid Locator for the Car. The settings and the summary above may be included in YOUR OWN iCloud or device backup, not sent to us. Deleting the app from the iPhone removes all its data, including the widget and the Live Activity; deleting the app from the Apple Watch removes the summary on the watch.

Links: iPhone and iPad have two links to a website. Privacy policy in the Settings tab opens this page, and the OpenStreetMap credit (in the Settings tab and under the mosque list) opens openstreetmap.org/copyright. Both open in Safari only when you tap them, and the app sends nothing when it opens them, your location included. From then on, that site's policy applies. The Apple Watch, the widget and the Live Activity show no link.

Third parties that receive your data, and how it is protected

The app shares your location only with the recipients below, only to perform its functions, and without your name, contact details, account, identifier or cookie. (1) overpass-api.de, run by FOSSGIS e.V. (Germany); privacy policy: https://www.fossgis.de/datenschutzerklärung/ (FOSSGIS's server terms for overpass-api.de refer to it). (2) overpass.kumi.systems and (3) overpass.private.coffee, both run by Private.coffee, a non-profit association in Austria; privacy policy: https://overpass.private.coffee/#privacy. All three receive your latitude and longitude, not rounded, the search radius and the fixed label "ImajieduMasjid/0.1 (+https://imajiedu.id)", and, like any server, your IP address and the time of the request. (4) Apple, on iPhone and iPad only; privacy policy: https://www.apple.com/legal/privacy/. Apple receives map image requests for the area shown, route requests containing your position, not rounded, and the mosque's position, and, only when Overpass has not answered in time or found no mosque, a search for "masjid" and "mosque" with your position, not rounded, and the radius.

FOSSGIS and Private.coffee are based in the European Union and subject to the GDPR. According to their published policies: FOSSGIS states that its server logs are not attributed to particular people and are not combined with other data sources. Private.coffee lists what it logs: a shortened IP address, the time, the request type and protocol version, the service address (without request parameters) and the app's label; those logs are kept for at most 48 hours to deal with technical problems, and no cookie is set for API use. Apple states that it does not sell personal data and that it uses it to provide its services.

On the basis of their published policies, which we read on 14 November 2026, we confirm that each recipient above gives the data it receives the same or equal protection as this policy: the data is used only to provide the service requested, it is not sold, and it is not used for advertising. This confirmation rests on their policies; we cannot inspect their servers ourselves. If a recipient's policy stops giving equal protection, we will stop using that service and update this page.

On Android, Google also receives data when the map is active, as described under Google maps and routes, under Google's Privacy Policy (https://policies.google.com/privacy). As stated there, Google uses some of the data from its map component to maintain and improve its own services. The navigation app you open with Directions receives only the mosque's coordinates and name, not your location.

Prayer times and adzan reminders

Prayer times are calculated on the phone from the date, your position and the device's time zone, using the method you choose. This calculation uses no internet.

The app already has two reminders for Subuh, Dzuhur, Ashar, Maghrib and Isya, both on by default: a reminder before the adzan (1 to 20 minutes, 10 by default) that vibrates without sound, and a silent reminder at the adzan. Both are scheduled with an Android alarm on the phone, with no server and no push notification. How punctual they are depends on the exact-alarm access described under Permissions. If your position is less than 10 minutes old, the notification may name the nearest mosque, its distance and the estimated travel time.

The before-the-adzan reminder has a Snooze 5 min button (Tunda 5 mnt on an Indonesian device). It closes the notification and sets a separate alarm on the phone that shows the same reminder five minutes later; the at-adzan reminder already scheduled still appears. If the adzan time has arrived by then and the at-adzan reminder is on, only the at-adzan reminder appears; if that reminder is off, the snoozed reminder arrives as the adzan notice. Nothing leaves the device.

Turning a reminder off in the app's Pengaturan (Settings) screen cancels its alarms. Turning notifications off in Android's settings hides the reminders, but the app keeps scheduling them on the phone. Neither erases the stored last position.

Permissions

Approximate and precise location: to find mosques, calculate distances and calculate prayer times. It is asked for when the app opens on the phone, or from the Allow (Izinkan) button on the car screen. Without location permission the app cannot search for mosques, and the car screen shows Location needed (Butuh izin lokasi). Notifications (Android 13 and later): for the adzan reminders; asked together with location when the app opens on the phone.

Exact alarms (Alarms & reminders): so reminders arrive on the minute. The app shows no permission prompt for this. While this access is off and a reminder is on, the Pengaturan (Settings) screen shows an Allow on-time alarms row (Izinkan alarm tepat waktu on an Indonesian device). Tapping it opens the Alarms & reminders page in Android's settings, where you decide; on Android 14 and later this access is off by default for new installs. Without it, Android may delay a reminder: on some devices by up to about an hour, and longer when battery saver is on. As soon as the access is given, the app schedules the next reminder again so it arrives on time.

Starting after a restart: to set the reminder alarm again after the phone restarts or the app is updated. Internet and network state: for the search, the map and routes. Android Auto map templates: to show the list and map on the car screen.

The app does not ask for background location, microphone, camera, contacts, photos or files, phone, Bluetooth or accounts. Location and notification permissions can be withdrawn at any time under Settings → Apps → Masjid Locator → Permissions. Exact alarms are managed under Special app access → Alarms & reminders, or through the row on the app's Pengaturan screen while that access is off. Internet, network state, starting after a restart and the Android Auto map templates are granted when the app is installed and cannot be switched off individually.

The car screen (Android Auto)

Android Auto receives a list of up to 6 nearby mosques: name, distance, estimated minutes, type (Masjid or Mushola), and numbered markers for the mosques' positions on the map. To refresh, the app uses Android Auto's own refresh control where the car supports it (Car App API level 5 and later); older car systems get the app's Refresh button (Muat ulang on an Indonesian device). The app does not put your own position on the car screen's map, although the distances are calculated from it.

If location permission has not been given, the car screen shows Location needed (Butuh izin lokasi) with an Allow (Izinkan) button. That button works only while the car is parked, and opens Android's location permission request (approximate and precise) on the phone; the car screen reminds you to look at the phone only when the car is safely stopped. Your choice on the phone has the same effect as a permission given when opening the app.

The app reads no vehicle data at all: no car speed, no sensors and no location from the car. How the adzan reminders appear on the car screen is decided by Android Auto.

What is stored on your device

Your settings: calculation method, Asr school, search radius, refresh interval, reminder minutes and reminder choices. The rounded last position with its time, as described above. A technical note of the last error (the error's stack trace and its time), saved when the app crashes or when a screen fails to load. It is not sent anywhere by the app. While it exists, the Pengaturan (Settings) tab shows a Last error report row (Laporan galat terakhir on an Indonesian device) that opens it, and tapping the note deletes it.

Mosque search results and routes are kept in memory only while the app runs. The app stores no files, downloads or travel history. Everything sits in the app's private storage; we cannot read it.

Backups

The app allows Android Auto Backup. Your settings, the rounded last position with its time, and the last error note may be copied to YOUR OWN Google account backup and restored when you change phones or reinstall. That data goes to your Google account, not to us. You can turn it off under Settings → Google → Backup (the location can differ by device).

Deleting your data

We hold no data of yours, so there is nothing to ask us to delete. There is no button in the app that erases everything. To remove all data on the phone: Settings → Apps → Masjid Locator → Storage → Clear storage, or uninstall the app. Backup copies are removed through the Google backup settings on your device.

Requests already sent to the Overpass services, Apple and Google are governed by their policies, named under Third parties that receive your data. We never receive them, so we cannot delete them for you.

Children

We receive no data from anyone, children included. There are no accounts, advertising, purchases, chat, sharing or uploads. The only link to a website is the link to this privacy policy; iPhone and iPad also show an OpenStreetMap credit link to openstreetmap.org/copyright. Both open in the browser only when tapped and send nothing. It is the same for everyone, and there is no age check.

Whoever is using it, its main function sends the device's location to the third-party services named above, and when the map is active Google's map component collects its own identifier and technical data, as described above. Parents or guardians can choose approximate location, withdraw the location permission, or contact us using the details below.

Not sold

We do not sell, rent or trade data, and we receive none to begin with. The app sends location to the services named above only for the mosque search, the map and routes, never for advertising. How those services use what they receive, including Google's use of map data to improve its services, is set by their own policies. We do not build a profile of you.

Retention and security

We keep nothing, because nothing reaches us. Data on the phone stays until you delete it or uninstall the app; the stored position is overwritten by each new one. Records at the Overpass services, Apple and Google follow their own policies.

Every connection uses HTTPS. Data on the phone sits in the app's private storage and is protected by Android.

Changes to this policy

When the app's data practices change — a new reminder, a new service or another use of location, for instance — we update this page and the date above. This version takes effect on 14 November 2026.

Contact

PT Taqwa Amanah Teknologi
Fady Nandita As Shiddiq
Jl. Diklat Pemda Dukuh Pinang No. 24, Bojong Nangka, Kelapa Dua, Kabupaten Tangerang, Banten 15810, Indonesia
imajiedu@gmail.com
+628119949720