Navato
עברית
Request a pilot

Security, privacy and data

What your security, privacy and procurement teams need to know about Navato, in one place.

Where data goes
  1. The phone in each vehicle

    Map, search, routing and spoken directions. Navigation never needs a server.

    Always
  2. Servers in Frankfurt, Germany (EU)

    Only what a sharing switch is on for, sent while the vehicle is parked and the phone is online, and live location reports from phones set to send them to navato.ai.

    Off by default
  3. AI analysis, United States

    Shared trip summaries with no coordinates, dates, IDs or IP addresses.

    Off by default

Navigation needs no server

The map, address search, routing and spoken directions all run on the phone. Navato goes online while it guides a vehicle only if live location reporting is switched on, so a pilot can run with no drive data leaving your vehicles.

What your organisation controls

Sharing
Three separate switches in Settings › Data & privacy: Trip summaries, Full drive recordings and App diagnostics. All are off by default, and turning one off also deletes what was shared under it.
Live location reporting
Off by default on every phone. If it is switched on, the phone sends its position, while Navato tracks or guides the vehicle, to the https server set on that phone; the screen and the notification show it, and the driver can switch it off at any time.
Deletion and export
Delete my data on the server removes everything a phone has shared. Export my data saves a copy.
Accounts
There are none. If sharing is switched on, the phone gets a random ID; drivers are never asked for a name, email or phone number.
Updates
When a vehicle is parked and its phone is online, the app checks for settings and announcements and can download community updates, which are the same file for every phone.

Where data lives, and for how long

What a shared trip summary keepsBefore a shared drive leaves the phone, its first and last stretch and the area around every long stop are removed, and its start and end are kept only as approximate areas.

Start Kept only as an approximate area First stretch removed on the phone

The part that can be shared

Destination Kept only as an approximate area Last stretch removed on the phone

Diagram: a shared trip summary with its first and last stretch removed on the phone, and its start and end reduced to approximate areas.

AI analysis

When enabled, shared trip summaries are also analysed by Claude, made by Anthropic in the United States. Claude receives a version of the summary with no coordinates or other location or road identifiers, dates, IDs or IP addresses, and never receives recordings. Under Anthropic’s commercial terms, the data is not used to train its models.

Who processes data for us

Full details in the privacy policy

How we protect it

  • Everything travels over encrypted connections (HTTPS, with HSTS).
  • App keys are stored only as one-way hashes.
  • Recordings are kept in private storage, reachable only through short-lived signed links.
  • Access to production data is limited to the people who run Navato, is logged, and needs a secret access key that we replace regularly.
  • Our public pages load no code, fonts or images from other sites, set no cookies and use no analytics. Our internal management console shows OpenStreetMap map images.

We design our controls to meet the Privacy Protection (Data Security) Regulations 5777-2017.

Reporting a vulnerability

Write to security@navato.ai (see our security.txt). Please give us 90 days before you disclose it.

Documents for your review

Questions from your security team?

Include them in your pilot request, and we’ll go through them with you.