Mappos

Privacy Policy

Effective date: 21 November 2026 · Last updated: 21 November 2026 · Version 1.0

This policy explains what information Mappos (“we”, “the app”) uses, where it goes, how long it is kept and the choices you have. Mappos is operated by [Operator / organisation name].

In short
  • No account, no sign-up, no advertising, no tracking cookies and no analytics. We do not sell or rent your data.
  • Your location is used in your browser to show your position and plan routes. It is never stored on our server as a history.
  • Routes, searches and nearby-place lookups are sent to open map services (listed below) so they can answer.
  • Saved places, trips and settings stay on your device unless the optional Mappos server is enabled, in which case your places and trips are linked only to a random device ID.
  • Road reports (accidents, potholes …) that you submit are public and expire automatically.
  1. Information we use
  2. Location
  3. Where your data is stored
  4. Third-party services
  5. Community reports
  6. Voice & translation
  7. Retention
  8. Why we use it
  9. Sharing
  10. Security
  11. Your rights & choices
  12. Children
  13. Changes
  14. Contact & grievance officer

1. Information we use

DataWhenStored where
Precise location (GPS / Wi-Fi), speed and headingOnly after you allow location in your browserIn memory on your device while the app is open; not kept as a history
Search text, start / stop / destination pointsWhen you search or plan a routeYour device (recent searches); sent to geocoding & routing services to get results
Saved places (Home, Work, favourites)When you tap ☆ SaveYour device; or the Mappos server, linked to your random device ID
Trip history and activities (distance, duration, mode, kcal/fuel estimate, place names)When a trip or recorded activity endsYour device; or the Mappos server, linked to your random device ID
Recorded GPS trackDuring navigation / activity recordingOnly in memory on your device. Exported as a GPX file only if you choose to
Parking spotWhen you tap “Save parking”Your device only
Settings (theme, language, voice choices, fuel prices, mileage, vehicle height/weight, body weight for calorie estimates)When you change settingsYour device only
Random device IDCreated on first useYour device; sent to the Mappos server only to keep your own places and trips separate from other users
Road reports (type, location, optional note, time, votes)When you submit or voteMappos server (public) or your device if no server
Shortened, salted hash of your IP addressWhen you use the Mappos serverMappos server: for abuse prevention / rate limiting

We do not ask for your name, phone number, email address, contacts, photos or payment details. The body weight you enter for calorie estimates stays on your device.

2. Location

Mappos asks for your permission once, with an Allow location card, before your browser shows its own permission prompt. You can say “Not now” and still use the map by searching or by choosing Set my location here. Location is used to show your position, fill the start point, rank nearby suggestions, give turn-by-turn guidance, warn you about speed and reports ahead, and estimate reach.

Your position leaves your device only when it is needed to answer a request (for example, a route from your location, “nearby you” suggestions, weather, or a road report you submit), or when you deliberately share it (🆘 share location, share ETA). You can turn location off at any time in your browser or device settings.

3. Where your data is stored

On your device

Mappos uses your browser's local storage (keys starting with mappos.). This data stays on that browser until you clear it. Clearing the site's data in your browser removes it completely.

On the optional Mappos server

If the site owner runs the Mappos backend (api.php), places and trips are saved in JSON files on that server, separated by your random device ID. Road reports are stored there and shown to all users. The server also keeps a short-lived cache of map-service answers (see Retention), which can include coordinates and place names from your requests.

4. Third-party services

Mappos is built on free and open services. They receive the information needed to answer each request, and usually your IP address and browser details, under their own privacy policies:

PurposeServiceWhat it receives
Map imagesOpenStreetMap tile servers, OpenStreetMap France (Humanitarian), Esri (satellite & labels), OpenTopoMap, ÖPNVKarteThe map area you are viewing
RoutingOSRM via routing.openstreetmap.de (FOSSGIS) and router.project-osrm.orgStart, stop and destination coordinates
Search & addressesPhoton (komoot), Nominatim (OpenStreetMap Foundation)Search text and a nearby reference point; coordinates for address look-ups
Nearby placesOverpass APIYour location or route corridor
WeatherOpen-MeteoCoordinates of the place or destination
App componentsunpkg (map library), Google Fonts (typeface)Standard web requests (IP address, browser)

When the Mappos server's relay is switched on (Settings → “Route API calls via server cache”), routing, search, nearby and weather requests go through our server. The services then see the server's address instead of yours. Map images, the map library and fonts always load directly from their providers.

5. Community road reports

Reports are shared with every Mappos user so they can travel safely. A report contains its type, map position, optional note, time and vote counts. It does not contain your device ID. Please don't write personal information (yours or anyone else's) in notes. Reports expire automatically: for example accidents after about 3 hours, waterlogging after 12 hours and potholes after 30 days. Reports that several users mark as “gone” are removed sooner.

6. Voice guidance & translation

Spoken guidance uses your device's built-in text-to-speech voices. Depending on your device, the voice provider (for example Google, Apple or Microsoft) may process the spoken text under its own policy. For the “more languages” option, instructions are translated by your browser's on-device translator. Mappos does not send them to a translation server. The Voice packs screen only reads which voices are installed; it cannot change your system settings.

7. How long we keep data

DataKept for
Device storage (settings, places, trips, recents, parking)Until you delete it in the app or clear the site's data
Places & trips on the serverUntil you delete them in the app, or the operator removes inactive data
Road reportsUntil they expire (1 hour to 30 days depending on type; fixed speed cameras up to 1 year), or are voted away
Rate-limit records (hashed IP + time)Up to 24 hours
Server relay cache of map-service answers10 minutes to 24 hours depending on the service; deleted after at most 2 days
Server access logs (web server software)As configured by the operator; typically up to 30 days

8. Why we use your data

We use data only to provide the features you ask for: maps, search, routing, navigation and voice guidance, safety warnings, community reports, saved places and trip history. We also use it to keep the service secure and protect it from abuse. Location is processed on the basis of your consent (the Allow location prompt and your browser permission), which you can withdraw at any time. We do not use your data for advertising, profiling or automated decisions.

9. Sharing

We do not sell, rent or trade personal data. Data is shared only with the services listed in section 4 to answer your requests, with other users in the form of road reports, when you choose to share something yourself, or when the law requires it.

10. Security

Mappos should be served over HTTPS. The server validates and cleans every input, blocks direct access to its data folder and limits request rates. IP addresses are stored only as shortened, salted hashes. No system is perfectly secure, so please avoid putting sensitive information in report notes or place names.

11. Your rights & choices

Where the Digital Personal Data Protection Act, 2023 (India), the GDPR or similar laws apply, you have the rights they give you. These include access, correction, erasure, withdrawing consent, nominating someone to act for you, and complaining to the relevant authority (in India, the Data Protection Board of India).

12. Children

Mappos is not directed at children under 18 and does not knowingly collect their personal data. A parent or guardian who believes a child has used the service may contact us to have related data removed.

13. Changes to this policy

We may update this policy when features change. The “Last updated” date above shows the latest version, and significant changes will be highlighted in the app.

14. Contact & grievance officer

Mappos
Email: privacy@mappos.in
Grievance officer: naka
Address: [Chennai]

We aim to acknowledge requests within 72 hours and resolve them within 30 days.