Privacy policy
Last updated: October 27, 2026
In short
#- Navato navigates without sending anything to us, unless you switch on live location reporting to our server. The map, search and routing all run on your phone.
- Sharing drive data is optional, off until you turn it on, and split into separate switches.
- The app has no accounts. It never asks for your name, email or phone number.
- Shared drives are trimmed on your phone before they leave it.
- This website sets no cookies and uses no analytics or third-party trackers.
- You can export or delete your data at any time.
Who we are
#This policy covers the website navato.ai and the Navato app for Android. The controller of the data (under Israeli law, the controller of the database) is Navato. For anything about privacy, write to privacy@navato.ai.
This website
#Visiting the site
Pages are served by our hosting provider, Vercel, which receives your IP address and browser details in order to deliver the pages and protect the service. We do not keep raw IP addresses. To limit abuse, our server turns your IP address into a one-way code that changes every day, counts requests under that code, and deletes the counts after two days.
We use no cookies, no analytics, no advertising pixels and no social plugins. Our public pages load no code, fonts or images from other sites, so your visit is not shared with font or image services. Our internal management console, used only by the people who run Navato, shows map images from OpenStreetMap.
Your browser keeps up to three preferences on your device. They are never sent to us:
| Key | What it remembers |
|---|---|
navato.lang | the language you chose |
navato.langHint | that you have seen the language suggestion |
navato.motion | that you paused the animation |
You can delete them at any time in your browser settings.
Joining the beta
If you join the beta, we keep your email address, your name and role if you gave them, the page language, and the time and version of the privacy notice you accepted. We do not store your IP address or browser details with them. We use this only to invite you to the beta and to email you about it. The legal basis is your consent and your request to join. We keep it until the beta ends and for no more than 24 months, or until you ask us to delete it. Every email we send includes a way to unsubscribe. We never sell this information or use it for advertising.
Asking about a pilot or partnership
If you send a request through the form for organisations, we keep what you entered: your name, work email, organisation and sector, and, if you gave them, your role, the number of vehicles, your phone number and your message. We also keep the page language, the page you sent it from, and the time and version of the privacy notice you accepted. We do not store your IP address or browser details with it.
We use this only to reply to you and to discuss a pilot, a partnership or your question. The legal basis is your request and your consent. We keep it for up to 24 months from your request, or until you ask us to delete it. We never sell it, and we never use it for advertising or newsletters. If your organisation runs a pilot under a written agreement, that agreement also says how pilot data is handled.
The app
#What stays on your phone
Navato keeps these on your phone only: your drive recordings (when recording is on), your last position, your favourite and recent places, what the app has learned about your car, and the details of other devices you use with the app. None of it is sent to us unless you turn on sharing, and then only as described below. Recordings you export or share yourself, for example to a messaging app, are under your control.
Record Wi-Fi and cell signals is on by default (an app update switches it on once, also where it was off before), and you can switch it off in the app's settings. While it is on and your phone's location is on, your drive recordings also list, in full, the Wi-Fi networks and mobile-network cells your phone detects during the drive: each Wi-Fi network with its name and its unique identifier (BSSID), including networks shared from a phone, which are marked as such, and each cell with its network identifiers. If Full drive recordings is on, these entries stay in a recording when it is uploaded, and our server keeps them with the recording for as long as it keeps the recording.
When the app goes online
Whatever your sharing switches are set to, when your phone is online and the car is parked, the app asks navato.ai for its service settings, which can pause sharing or ask you to update the app (each time it starts and about every 12 hours), and for the announcements shown under Messages (about every 12 hours). With Use community knowledge on, it also downloads the community pack. These requests are the same for every phone and carry no app ID, no device code and nothing about your drives. As with a visit to this website, our hosting provider Vercel receives your phone's IP address to answer them. We use it only for a short per-minute limit against abuse and do not store it. If you switch on live location reporting, the app also goes online while you drive (see below).
Sharing, if you turn it on
In Settings › Data & privacy there are three switches, all off by default. You choose each one separately, and the app records your choice with its time and the consent version (currently c2). Turning a switch off stops future uploads and deletes what was shared under it. Delete my data on the server removes everything at once. The app uploads only while the car is parked, never while you navigate. Live location reporting, below, is a separate setting.
| Switch | What is sent | Kept for |
|---|---|---|
| Trip summaries | The roads you drove, your speeds on them and how well Navato tracked you, plus your car's make if you chose one. This includes location data. | 12 months |
| Full drive recordings | A detailed technical log of the trip: positions, speed and other technical readings recorded during the drive, for research and for replaying drives when we test improvements. This includes precise location data and, if Record Wi-Fi and cell signals is on, the Wi-Fi networks (names and identifiers included) and mobile-network cells the phone detected. Uploaded on Wi-Fi only unless you allow mobile data. | 30 days |
| App diagnostics | Error and performance counters, such as how long a route took to calculate. No location. | 90 days |
Before a trip summary or a recording leaves your phone, the phone:
- removes the first and last stretch of the trip, and the area around every long stop;
- removes identifiers of your vehicle and of other devices you use with the app, and any name or address you typed.
A trip summary is coarsened further: where the trip started and ended is kept only as an approximate area. A recording keeps precise positions between its trimmed ends and, if Record Wi-Fi and cell signals is on, the Wi-Fi networks and cells it lists, with their names and identifiers, which is why it is a separate switch, uploaded on Wi-Fi only by default and deleted after 30 days.
The app shows the exact distances and thresholds on its consent screen, before you agree.
Trips from the app's demo drive and from test devices are marked as such and are never used to build shared knowledge.
Live location reporting
Settings › Live location reporting is off by default. If you switch it on, you enter a server address (it must start with https://), a code or access key if that server needs one, and a unit name, choose how often to send (from every 2 seconds to once an hour), and confirm. The app first asks you to allow its notifications and location access. From then on, on every drive until you switch it off, while Navato is tracking or navigating with its notification showing (also with the screen off), the app sends that server the phone's current position, an approximate accuracy, the speed, the direction of travel, a one-word indication of how certain the position is, the time, the unit name and the app version. When that server is navato.ai, each request may also carry a short technical status of the navigation and of the sources it uses for the position; the app never sends it to another server. Tracking starts by itself when the car first moves with Navato open, when you set your position or when you choose a destination, and ends about 10 minutes after the end of the drive (while a route is active, only after the route ends). A stop, even a long one, can still count as part of the drive, and reporting goes on during it. The unit name is whatever you typed; we ask for a vehicle or team name, not a person's name. Like any internet request, the server you choose also receives the phone's IP address and the app's name and version. The app never sends the destination you entered, the route Navato planned or your recordings; the positions it sends do show where the car drives and stops. It sends nothing when the app is closed or after Navato stops tracking. While it reports, the map shows Sending location and the app's notification names the server, with a button to stop. Positions that could not be sent wait on the phone, in its memory only, and are lost when the app closes. The access key is stored on your phone encrypted with the Android Keystore and is sent only to the address it was entered for. Live location reports are not linked to the app's random ID and are never used to improve navigation or sent for AI analysis.
The server is the one you choose. If it is not navato.ai, the data goes to that server's operator, not to us, and their terms apply.
If you report to navato.ai with a code from us (for organisations that test Navato), our server keeps the positions of the last 24 hours, including each unit's latest one, linked to the unit name and to the feed the code belongs to. Only the people who run Navato can see them, in our management console. During a pilot, the written pilot agreement says who else may see them. Unless history is switched on for the feed (see below), we use them only to show them there. Positions, including each unit's latest one, are deleted within about 25 hours after they were sent (the deletion runs every hour), except the copies kept as history. For each access key we issue, our server also keeps the unit name it is bound to, if any, and when the key was created, connected to a phone and last used; these key details are deleted 30 days after the key or its feed is switched off, or 24 hours after the key was created if it was never connected to a phone. Once its positions are deleted (within about 25 hours of the last report), a feed that is switched off keeps only its name, counters and these key details and, if it has history, that history until its period ends or the organisation asks us to delete it. The key details are deleted 30 days after the feed was switched off; its name and counters 30 days after it was switched off or when the last of its history is deleted, whichever is later. Database backups are replaced as the table below says. Our hosting provider's logs keep the phone's IP address for a limited period set by our hosting provider; we do not store it ourselves. The access key is stored on our server only as a one-way hash. Our console shows the reports on map images from OpenStreetMap; its map servers see which map area is viewed, not the reports. For these reports the controller is Navato, unless a written pilot agreement makes your organisation the controller. We process them because you, or the organisation that gave you the code, asked us to.
History. The organisation that gave you the code can choose to keep history for its feed; we then switch history on for that feed. History is off unless it does, and it starts only when it is switched on: positions received before that moment are never kept as history. From then on, our server also keeps, as history, the positions it receives for that feed, together with what is computed from them: a summary of each drive (when it started and ended, its distance, the time spent driving and stopped, its speeds, how certain its positions were and the areas it passed through) and daily totals for each unit. History also keeps, with the positions, the technical status sent with the reports (see above); without history, that status is not kept. History is kept for the period that organisation chose, which may be unlimited. The organisation can ask us at any time to delete its feed's history, or a part of it, and we then delete it. When the period ends, when history is switched off for the feed or when the feed is deleted, the history concerned is deleted within a day. Only the people who run Navato can see the history, in our management console, where they can search it by unit, feed and time, show the drives on a map and see statistics such as distance, driving time and speeds; every search and every copy is logged. We may give the organisation that gave you the code copies of its feed's history as files; what it then does with them is its responsibility. During a pilot, the written pilot agreement says who else may see the history and receive copies of it. We use history only to show it in our console, to compute these statistics and to give that organisation copies. The positions, and the figures computed from them, are approximate and are not a certified record. History is not linked to the app's random ID and is never used to improve navigation or sent for AI analysis. For history, the controller and the reason we process it are the same as for the reports above.
Your random app ID
The first time you turn sharing on, the app creates a random ID and a secret key. Our server stores the ID and a one-way hash of the key, so even we cannot recover the key. With the ID, it keeps the app version and the app's language. The app also adds a separate random code for each vehicle you use it with, so that trips from different vehicles are not mixed. It also gives your phone a short device code, shown at the bottom of Data & privacy, so you can ask us by email to delete your data. None of these is linked to your name, phone number, Google account or advertising ID. When you delete your data, the app starts again with a new ID.
How we use shared data
Only to improve navigation for all Navato drivers: to learn real road speeds and junction delays, places where GPS is unreliable, places where Navato needs to do better, and how to make it work well for more drivers. We also send your own phone results about your own trips. We never sell data, never use it for advertising, and never give it to anyone who would.
Analysis with AI
#Shared trip summaries are analysed on our servers, and a fixed set of rules always runs. When enabled, we also use Claude, an AI model made by Anthropic, through Anthropic's API. Anthropic is in the United States.
- What Claude receives: a version of the trip summary with no coordinates or any other location or road identifier, dates, start or end areas, app ID or IP address.
- What Claude never receives: recordings.
- Checks: our software checks its answers before they are used.
- Training: Anthropic processes this data on our behalf and, under its commercial terms, does not use it to train its models.
No decision that has legal or similarly significant effects on you is made automatically.
Knowledge shared with everyone
Road knowledge is published to all drivers only when several different phones support it, so it cannot be traced back to one driver. It is published as one file that is the same for every phone. With Use community knowledge on, the app downloads that file when you are online and parked. Downloading it tells us nothing about who or where you are, you do not need to share anything to receive it, and you can turn it off in Data & privacy.
What we never collect
- your name, email or phone number (the app has no accounts);
- your vehicle's VIN, or identifiers of other devices you use with the app;
- the first and last stretch of a shared trip, where it starts and ends;
- contacts, photos or data from other apps;
- your advertising ID;
- your location in the background: the app has no background-location permission, and collects data only while Navato is navigating or tracking a drive in the foreground, with its notification showing.
Who processes data for us
#| Service | What it does | Where |
|---|---|---|
| Vercel Inc. | Website hosting, server functions and private file storage | Servers in Frankfurt, Germany (EU); a US company |
| Neon | The app's database | Frankfurt, Germany (EU) |
| Anthropic PBC | AI analysis of trip summaries, as described above | United States |
| Cloudflare, Inc. | DNS for navato.ai, and forwarding of email sent to our @navato.ai addresses | Global |
| An email service, which we will name here before we send the first beta email. | Sending beta emails |
Each of them works under a contract that limits it to providing its service to us.
International transfers
#Our servers and database are in the European Union. Israeli law allows transfers to EU countries, and the EU recognises Israel as protecting personal data adequately. Anthropic and the parent companies of some of our providers are in the United States. Those transfers rely on contractual safeguards and, where Israeli law applies, on the Privacy Protection (Transfer of Data to Databases Abroad) Regulations 5761-2001.
How long we keep data
#| Data | Kept for |
|---|---|
| Full drive recordings, with the Wi-Fi networks and cells they list | 30 days |
| Trip summaries and the results derived from them | 12 months |
| App diagnostics | 90 days |
| Export files you request | 24 hours |
| Everything linked to an app ID that has not connected for 13 months | deleted |
| Records of consent choices and deletions (dates and switch states only) | 24 months |
| Database backups | replaced within 30 days |
| Live location reports sent to navato.ai | positions, including each unit's latest one, up to about 25 hours; if history is switched on for the feed, positions, drive summaries and daily totals for the period the organisation chose, which may be unlimited, deleted within a day after it ends or when the organisation asks us to delete them; the technical status sent with the reports, only as part of that history and for as long as it is kept; access key details (the unit name a key is bound to, and when it was created, connected to a phone and last used), until 30 days after the key or its feed is switched off (24 hours for a key never connected to a phone); a switched-off feed's name and counters, 30 days after it is switched off or when the last of its history is deleted, whichever is later |
| Daily IP codes used against abuse | 2 days |
| Beta sign-ups | until the beta ends, at most 24 months |
| Pilot and partnership requests | up to 24 months |
| Shared road knowledge (anonymous, combined from several phones) | as long as it is useful |
Security
#- 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 run no code from other sites; our internal management console uses the open-source Leaflet map library, served from navato.ai, and map images from OpenStreetMap.
- The live-location console is reachable only with a secret access key, its sessions end after 8 hours or 30 minutes without use, and every change to a feed, every search of the history and every copy of it is logged.
We design our controls to meet the Privacy Protection (Data Security) Regulations 5777-2017.
To report a vulnerability, write to security@navato.ai (see security.txt). Please give us 90 days before you disclose it.
Your rights
#Under Israel's Privacy Protection Law 5741-1981, you may review information about you and ask us to correct or delete it. If the GDPR applies to you, you also have the rights of access, rectification, erasure, restriction, portability and objection. You may withdraw your consent at any time, without affecting what was done before.
How:
- In the app: Export my data, and Delete my data on the server, in Settings › Data & privacy.
- Live location reports on navato.ai: they are deleted within about 25 hours; if history is switched on for the feed, positions, drive summaries and daily totals are kept for the period the organisation chose, which may be unlimited. To see what we keep about a unit, or to have it deleted, write to privacy@navato.ai with the unit name and the time range.
- For anything else, including beta sign-ups and pilot requests: write to privacy@navato.ai. We answer within 30 days.
Because the app has no accounts, we can act on app data by email only if you send the device code shown at the bottom of Data & privacy. We can delete data this way, but we never send exports by email: use Export my data in the app.
You may also complain to Israel's Privacy Protection Authority, or to your data protection authority in the EU.
You are under no legal obligation to give us any of this information. Navigation works fully without it.
Children
#Navato is meant for drivers. The beta is open to people aged 18 and over, and we do not knowingly collect information about children.
Changes
#We will publish any change here with a new date. If a change affects what the app shares, the app will pause sharing and ask you to review your choices before anything is sent under the new terms. The app update that started recording Wi-Fi networks and cells in full did not pause sharing: if Full drive recordings is on, recordings uploaded after that update include them.
Contact
#Navato. Email: privacy@navato.ai.