YOUR JOURNEY IS YOURS

Privacy, in plain language.

This policy covers Nammove on the web, iOS and Android. Updated 18 November 2026.

Location stays in your browser

Location is requested only when you select a location action. With permission, the browser supplies coordinates, accuracy, timestamp, heading and speed when available. Nammove processes the latest fixes locally to estimate your corridor position and direction. We do not send a GPS trace to a Nammove server, sponsors or AI. Coordinates are held in memory, not saved with your journey. Leaving the app page stops its location watch.

Mobile location and arrival reminders

In the iOS and Android apps, location is optional and is used only for a ride you start. With your permission and choice for that ride, iOS can continue location updates in the background; Android uses a visible location foreground-service notification rather than unrestricted background-location permission. Tracking stops at arrival or when you end the ride. Active-ride state and recent location observations may be saved temporarily in the phone’s local database to recover the ride after an interruption; those observations are removed when the ride ends. Raw GPS observations are not included in cloud backup or sponsor analytics. Notifications are local arrival reminders, not remote marketing pushes. You can plan and confirm stations manually without location or notification permission.

Maps make network requests

Online street maps request OpenStreetMap vector tiles and basemap font glyphs directly from OpenFreeMap. The provider receives normal request information such as your IP address and requested map areas. Following your location changes those map areas. Choose Network view to use the bundled diagram. Interface and metro-station fonts, MapLibre workers and network data are served by this site.

OpenFreeMap privacy policy ↗

The native mobile apps bundle their offline Bengaluru map, glyphs and route files on the phone. A supported offline map does not require street-tile requests. Opening external sponsor, support or other website links contacts that website under its own privacy policy.

What is saved on this device

Local storage keeps your language, favourite station IDs, selected origin and destination, and your last confirmed ride station/transfer state. Accounts are optional. Journey summaries and recorded spending are stored in IndexedDB, separately for guests and each account. Passwords are sent over HTTPS to Supabase Auth and are not saved by Nammove; this browser stores the session needed to keep you signed in. The service worker caches the app shell, fonts, data and diagram so planning can work offline. It does not pre-download street tiles. Clear site data in your browser to remove caches as well.

Your destination reminder setting, alerts already shown, and dismissal of the install banner are also saved on this device. Notification permission is requested only when you turn on a reminder. Reminders use the same foreground GPS or manual station confirmations; no location is sent to a reminder server.

Optional account backup and deletion

When you sign in, new journey summaries and recorded payments can sync through our Supabase project in Mumbai, India. Summaries include route station IDs, start/end times, reached stops and amounts you enter. Confirmed stops and times can reveal precise places you visited, and amounts can reveal your fare purchases. Raw GPS coordinates and traces are not backed up. Guest journeys stay separate unless you explicitly add them to your account. You can pause backup or sign out without losing guest records. Cloud data is protected by account ownership rules. Sponsors cannot access private journey history.

Supabase Auth handles sign-in and sends account-confirmation and password-reset emails through Resend. Resend receives the recipient email address and the authentication message. Email engagement tracking is disabled. Account data stays until you delete it. Delete your account in Account → Delete account, or use the web deletion page below. After password verification, deletion removes the Auth identity and its backed-up journeys and sync receipts. Guest records and copies on other devices are separate; clearing that device’s site/app storage removes local copies. Service providers may retain operational logs and backups under their retention policies.

Delete your Nammove account · Manage your account

Mobile service connections

When the mobile app loads the public sponsor catalog, signs in or syncs a backup, our Supabase gateway can record an approximate city and country inferred from the connection’s IP address. These logs help diagnose service problems and prevent abuse. The public catalog can load while you use the app as a guest.

Website hosting

This website is configured to use Vercel. To serve pages, the host receives request details such as your IP address and requested URL, and may keep access logs. Shared route URLs can include selected station names or IDs. Nammove does not add GPS traces to these requests.

Cookieless usage analytics

When analytics is available, Nammove automatically uses PostHog in the US on the web to measure visits and actions such as journey planning, ride completion and offline readiness. We send page categories, language, broad journey-length bands and limited referral categories. Analytics removes station names and IDs, route slugs, URL queries, full referrers, GPS coordinates and report text before sending. No stored browser or session ID is sent. Session recording and automatic click capture are disabled.

PostHog uses your network IP address, browser user agent and site hostname to compute a daily hash. It removes the raw IP address and user agent before storing events; the site hostname remains. Returning visits across different days cannot be measured reliably. Location enrichment is disabled. We save only your analytics preference on this device, with no analytics cookies or persistent analytics identity. You can stop analytics below. A previous refusal, browser Do Not Track or Global Privacy Control keeps it off. Planning works with either choice. Offline use and blocked requests are missing from these estimates.

Usage analytics is unavailable on this deployment.

PostHog privacy policy ↗

Sponsors

Sponsor visibility follows Nammove’s admin setting. Active campaigns follow their schedule, station targeting and placement settings. Without a connected backend, ordinary journeys show no sponsors. The explicit ?sponsor=1 (or ?sponsors=1) test mode can show labelled examples; these do not claim a partnership. Sponsor links use static campaign and placement tags, without journey, device or GPS identifiers. Guidance, transfers and get-off prompts take priority. Close and pause controls remain available. The public catalog refreshes once a minute while visible; cached campaigns expire within five minutes offline. Admin sign-in uses the same Supabase project, and only assigned administrators can change campaigns or visibility.

Measuring sponsor performance

The mobile apps measure sponsor interactions only, using PostHog in the US. On web and mobile, when analytics is enabled, we measure a sponsor view after at least half the creative stays visible for one continuous second, and measure detail opens and website clicks separately. Events include the campaign ID, placement, map/card surface, platform and a temporary random exposure ID held only in memory. This connects a view to a click without identifying a rider. No journey, station, account or location is included. Reports count measured exposures, not exact people; offline activity and opted-out visits are not backfilled. Samples, previews and tests are excluded from live campaign totals. The analytics control above, Do Not Track and Global Privacy Control also stop sponsor measurement.

Sponsorship and AI

Sample offers do not influence route selection. This beta has no AI endpoint or ChatGPT login. AI remains Coming soon.

Reports and contact

Support reports are copied or downloaded locally only when you choose to do so. Nothing is submitted automatically. Emailing a report sends your email address and message through your email provider to the support inbox. Support · iOS, Android and web apps

mjn@manjumjn.com