PRIVACY AND LIMITS · UPDATED 14 November 2026
Real data. Limited claims.
Anyone can use it without an account. Signing in with Google is optional. Safety Maps records every visit with its own analytics, including what you search for, the places and routes you compare, and your IP address; see Analytics below. There is no navigation, emergency response, staffed support or incident reporting. Entrances, public access and staffing of listed places are unverified. In an emergency, call 112.
Analytics: what Safety Maps records
Every page on this site loads a small first-party analytics script (/analytics.js). It sends what it records only to this site's own server; no Google Analytics, advertising network or other tracking company is involved. It starts on your first page, without asking, and keeps working while you use the site. It records:
- Who you are to us: a random visitor ID kept in your browser's storage, a session ID, and, if you sign in with Google, your name and email address.
- Where you are: your full IP address and the country, state and city it points to. The lookup uses a copy of DB-IP's free database on our own server, so your address is not sent to another company for it.
- Your device: browser, operating system and versions, device type and model, screen and window size, pixel density, language, time zone, network type and speed, processor cores and memory, touch support, dark mode and similar settings.
- How you got here: the page that linked to us, and campaign tags such as
utm_sourcein the link. - What you do: every page you open with its title, how long you actively spend on it, how far you scroll and how fast it loaded; the links and buttons you click; and errors the page hits.
- Your journeys: the exact text you search for, the places you choose with their coordinates, your device location (if you press Use my current location) with its accuracy, but not the position used for Open near me, the start, destination and departure time of each comparison, how many routes came back, which route and places you opened, the filters you use, and the text of feedback you send.
This is kept in a separate analytics database on our server, with no automatic deletion. Only the Safety Maps owner can see it, in an admin dashboard that requires signing in with one of two named Google accounts. It is not sold or shared. If you delete your Google-linked Safety Maps account, the analytics linked to that account are deleted too. To have the analytics for your browser deleted, use the feedback form and include the visitor ID shown by running localStorage.getItem('sm.visitor') in your browser console, or clear this site's data to start with a new ID. Blocking JavaScript or /analytics.js stops it.
Searches and routes
When you press Search, the application sends your search text to Geoapify. When you compare, it sends selected endpoint coordinates to Geoapify for up to three driving preferences. Requests pass through the application server; your provider API key is not sent to the browser. Provider URLs necessarily carry parameters under Geoapify's API design. Geoapify processes requests under its own privacy policy. We have not independently verified vendor retention or deletion. Do not enter a home address, personal incident or sensitive journey.
Driving it. If you press Drive it in Google Maps or a place's Directions, your browser opens Google Maps with the start and destination (or the place) in the link, plus up to three suggested stops if you press Drive it with these stops under Plan your stops, and Google handles it under its own privacy policy. Nothing is sent to Google until you press one of those.
Sharing a trip
When you press Share trip, Safety Maps stores the start and destination you chose (their names and map points), and the time, distance and rough shape of the route you had selected, under a short random link, such as /t/Ab3dEf7h, for 30 days. Anyone with the link can open the same trip; it is not listed anywhere and search engines are told not to index it. If your start was your device location, the link holds a nearby point rounded to about 100 m and the name 'Shared start point', not your exact position, and the route's shape is not stored. The link's preview picture shows the two names, the route's shape and its time and distance. The message you send, and who you send it to, stay in your own app (for example WhatsApp); Safety Maps does not see them. A shared link also keeps whether the trip was by car, motorbike or on foot. Opening a shared trip compares it again from the current time. Your choice of Car, Motorbike or Walk is remembered in this browser only. A start and destination you have chosen but not yet compared are remembered in your own browser for up to 12 hours, so they are still there if you close and reopen Safety Maps; they are not sent anywhere, and a start taken from your device location is not remembered.
Your location
Opening the map on your area. When you open the planner, your browser asks whether Safety Maps may use your location. If you allow it, the map opens on your area. That position stays in your browser: it is not sent to Safety Maps, Geoapify or anyone else, and is not recorded (analytics notes only whether you allowed it). If you decline, the map stays on the whole of India, and it moves to whatever you search for.
Using it as your start. Safety Maps uses your location as a start point only when you press Use my current location. The position is rounded to about one metre, used as the start of your comparison, sent to Geoapify with the destination when you compare, and recorded in Safety Maps' analytics. It is not tracked in the background.
Open near me. When you choose Open near me (or open the Near me shortcut on Android), your browser asks for your location once. The position, rounded to about one metre, is sent to Safety Maps' own server only to look up the mapped places around it in our listings file, and the answer comes back to your browser. It is not sent to Geoapify or anyone else, not stored, not written to logs and not recorded in analytics: analytics notes only that you looked, how far the search reached, how many places came back and whether your location was accurate to within 50 m, 300 m or 2 km. Pressing Refresh asks again. It uses none of your daily allowance.
Your places and trips
Each comparison is added to Your trips under the planner (the ten most recent), and you can star trips (up to 20) and save places as Home, Work or a starred place (up to 20). Each holds the names and map points you chose and when you last used it. A trip that started from your device location is kept as “your location”, without the position itself, and asks for your location again when you use it. The crosshair button on the map reads your position once to show it on the map; it is not sent anywhere. Town and city suggestions are matched on your device from a list inside the app. If you press Start to follow a route, or turn on “Show where I am on this route”, your browser reads your position while that page is open and Safety Maps uses it only on your device, to place you on the route and on the map and to name the next fuel stop listed open ahead. It is not sent to Safety Maps or anyone else, not stored and not recorded in analytics, which notes only that the option was turned on or off. It stops when you turn it off or leave the page. Holding a place gives you a menu to copy it, open it in a maps app or share it; that happens on your device, and analytics notes only which action was used, not the place. Without signing in, they are kept only in this browser's storage; Safety Maps does not receive them. Clearing this site's data removes them. When you are signed in with Google, they are also kept with your account in Safety Maps' database (and its encrypted backups) so they appear on your other devices; the first time you sign in, those already in this browser are copied into your account. Delete account removes them from the live database straight away, and removing a trip or place removes it from the account. Analytics notes when you save, star, remove or reuse one, but not which place.
Trips saved for offline
When you press Save under Save for offline on a comparison, your browser keeps a copy of that comparison (the routes, the places along them and the start and destination you chose), the map pieces along the selected route, and the Safety Maps app itself, in this browser's own storage (Cache Storage). It is downloaded from Safety Maps only; nothing is sent anywhere else, and Safety Maps does not learn that you saved it beyond an analytics note that a trip was saved, with its size. It stays until you remove it under Saved offline, remove that trip, clear this site's data, or your browser clears it to free space. Opening it without a connection shows it as it was when saved: listed open states are for that departure time and may have changed.
Was it open?
A place's details ask whether it was open when you were there. If you answer, Safety Maps adds one to that place's count of “open” or “closed” answers for the day (UTC). Only those daily totals per place are stored; nothing about who answered, your location or your device is kept with them, and the totals are deleted after a month. To allow one answer per place a day, the server briefly keeps, in memory only, a note of your browser's visitor cookie (or account) and network address with the place; it is never written to disk and clears each day. This browser also remembers which places you answered today. Everyone who opens that place sees the last two weeks' totals. They are what people said, not a confirmed opening state or a rating, and they don't change the listed hours. Analytics notes that an answer was given, not for which place.
On your home screen
You can add Safety Maps to your phone’s home screen from your browser’s Share or menu button. After your first comparison the planner shows how: in iPhone and iPad Safari it explains the Share steps, and on Android it offers an Install button that opens your browser’s own install prompt. Closing that tip saves a single setting in your browser so it stays hidden. The site also installs a small helper in your browser (a service worker). Normally it caches nothing: every page and search comes from the server, and without a connection it shows a friendly offline page. It never caches searches, comparisons or other API responses. Analytics notes when Safety Maps is opened from the home screen, and whether an install prompt was accepted.
Using it without an invitation
Your browser gets a random visitor cookie, valid for 30 days, so that daily limits apply per browser. The application also counts requests per network address. Both counts are kept only in server memory and reset each day (and on restart). Analytics records visits separately, as described above. Visitors share one service-wide daily allowance; the application stores only that combined total.
Signing in with Google
Signing in is optional and only gives you a larger daily allowance. When you press Sign in with Google, Google asks you to choose an account and tells you that Safety Maps will receive your name, email address and profile picture. Safety Maps keeps your name, your email address, a one-way hash of your Google account ID, and when you first and last signed in. It does not keep your profile picture, contacts, Google password or any access to your Google account after sign-in. While you are signed in, the analytics described above are linked to your name and email.
Your account gets its own daily credit count in the database, kept for seven days like everyone else's. Feedback you send while signed in is stored with your account, so the owner sees your email address next to it. The browser holds an HttpOnly, Secure, SameSite=Strict cookie for 30 days; up to five devices can stay signed in. Sign out ends that device's session. Delete account, in the menu under your initial, removes your name, email, sessions, credit count and feedback from the live database straight away. Encrypted database backups made before that keep them until those backups are replaced. Google's own handling of the sign-in is covered by Google's privacy policy; you can also remove Safety Maps from your Google account's third-party connections at any time.
What this application retains
The review uses pseudonymous reviewer IDs. It stores invitation hashes in deployment configuration and hashes of random session tokens in a persistent database, with eight-hour session expiry. Up to three sessions per reviewer are kept; expired sessions are removed during subsequent sign-in. Invitation rotation/removal invalidates sessions for that invitation. The browser uses an HttpOnly, Secure, SameSite=Strict session cookie. Sign out invalidates that session and clears its cookie. Clearing browser cookies alone does not immediately delete a server record.
The database retains daily aggregate credit reservations per reviewer and for the service, minute-window counters, a provider-request lock and a pause switch. Credit rows older than seven UTC days are pruned during subsequent reservations, not on a guaranteed background deletion schedule. This operational database does not store search text, coordinates (including Open near me positions) or route responses; the separate analytics database does, as described above.
Feedback you send. If you press Send feedback, the text of your three answers is stored with your pseudonymous reviewer ID and the time. Only the review owner can read it, in the app. Each item is deleted after 90 days, and each reviewer can send up to 10 a day. Feedback is part of the encrypted database backup. Leave out addresses, journeys and other personal information; to have feedback deleted sooner, ask the person who invited you. Current results remain in browser memory until refresh, sign-out or navigation; someone using your device may see them. API responses are not put in the offline service-worker cache.
Source data
The source is public OpenStreetMap data for all of India, from Geofabrik's India extract, kept to places inside India's official outline (Natural Earth, India point of view, plus 3 km for coastal and border roads). The review shows the data's date, labels it STALE seven days later and is refreshed by a reviewed weekly update. Unknown individual edit times remain visible. It is not a new field survey or a completeness guarantee. The server reads a checksum-verified listings file from its own storage; the complete file is not a public static asset. OpenStreetMap attribution and ODbL licensing apply. No private field observations or participant records are collected here.
Hosting and usage
Railway receives ordinary hosting/network metadata, and may retain IP addresses, URLs and operational/security metadata under its policies. Server logs avoid request URLs, bodies, cookies and headers; this does not promise zero infrastructure logs. Analytics is recorded in its own database, as described above. There is no runtime AI processing or external tile/font request: map tiles and fonts are served by this application.
A persistent shared allowance limits all invited reviewers on this service. There are also per-reviewer limits, minute limits, a limit on how many provider requests run at once (three when the planner is open to everyone, one when it is invitation-only) and an owner pause switch. A request already in progress can finish when paused. Failed provider requests reserve credits conservatively and are not retried automatically. These controls cover this service, not every use of the Geoapify account/key; separate local tools or other integrations have separate allowances. The provider's own quota may be soft. Quota resets are based on UTC, not local midnight.
Access, corrections and pilot readiness
To ask about privacy, a source listing or deleting feedback you sent, use the feedback form at the bottom of the planner (without personal details), or ask the person who invited you. No public contact address or support team has been established yet. Do not submit sensitive information through GitHub issues or URLs. Field validation, participant comprehension, physical-device testing and production operational ownership remain incomplete. This disclosure describes the controlled review and is not a compliance certification or final public-pilot privacy notice.