Pino
Security and Privacy
A plain-language explanation of how Pino treats your data. The legally binding document is the privacy policy; this page exists to be readable.
In short Pino is offline-first by architecture: maps are stored on your device and routes are calculated on your device. Offline-first is also privacy-first — data that never needs to leave the device is data that cannot be collected in transit.
Are maps stored locally?
Yes. Downloaded map regions are stored on your phone or watch. Viewing the map, searching and navigating read from local storage, not from a server.
Are routes processed locally?
Yes. Route calculation runs on the device using the downloaded routing data. Your origin, destination and route are computed without a server round-trip.
Does location history leave the device?
Positioning during navigation happens on-device via GPS. The precise data-handling commitments — including whether any diagnostic data is ever transmitted — are stated in the privacy policy, which is the document to rely on.
What syncs between phone and watch?
The Wear OS app runs standalone and does not depend on a phone connection for maps, search or navigation. Details of any optional phone-watch synchronization will be documented here once verified.
Is an account required?
Account and sign-in requirements, if any, are shown in the app and will be documented here explicitly.
What analytics are collected?
This website uses a minimal, vendor-neutral event layer that never receives precise location, downloaded-map names or navigation data. In the app, any analytics collection is governed by the privacy policy.
Data deletion and contact
To ask about or request deletion of any data associated with you, email support@m23n.com. You will get a human answer about what exists (often: nothing beyond your email) and what was deleted.