Privacy policy
The short version
Your stops, your candidates and your finished routes live in your own browser. To work a route out, the app sends them to the server, which plans it and sends the answer back; the working copy is erased as soon as the answer is sent. The server keeps a small record per browser: how many routes and searches you ran this month and what they used at Google, when you last used the app and whether that was on a phone or a computer, the country and language you planned in, whether you have a paid plan, any days you chose to save, and, only if you gave them, an email address or your own Google key, which is kept encrypted. Addresses you plan with go to Google Maps to be located and routed. If you press "use my location", your browser asks you first, and only if you agree are those coordinates sent to Google to be turned into a street address, exactly as a typed address is; nothing about where you are is written into any record on the server. One alert can leave your browser in one case only, described below. The one exception to all of this is the owner's own browsers, which he marks himself: those keep their last day of plans so that he can trace a fault in his own use, and they are dropped after a day. That is the whole list.
1. Who is responsible
Excel Armor
Rabbi Averbuch 26, Ramat Hasharon 4740020, Israel
Registered in Israel as an exempt dealer (עוסק פטור), business number 026627760.
Person responsible: Noam Brand. Email support@excel-armor.com, telephone +972 54 283 7000. There is no data protection officer; the business is not of a kind or size that requires one, and the address above reaches the person who decides these things.
2. What stays in your browser
These never leave your device except when you press “Plan route”, and then only as part of the plan you asked to be worked out: the stops you typed, the candidates found for your category stops, your last finished route, your search options and the rules you set for each kind of place, your travel mode, your saved places, your chosen language, and a random id that tells the server "the same browser as before". The website itself also keeps your light or dark choice and whether you dismissed the "add to home screen" hint.
The random id is not your name and is not linked to one. Press Clear in the app to remove the plan; clear the site data in your browser to remove all of it, including the id.
3. What the server keeps, per browser
| Record | What it holds | How long |
|---|---|---|
| Usage | The month; how many routes and searches you ran in it and what they used at Google, priced at Google's list price; when you last used the app, and whether that was on a phone or a computer; the country and language you planned in; spare routes from invites; whether you came through someone's invite, and how many people who came through yours bought a plan. | The counts start again each month. Deleted on request. |
| Licence | Your plan, its expiry date, and the email address the payment provider passed on. | Until it expires or is refunded, then deleted on request. |
| Saved trip days | The stop lists you chose to save with "Save this day", up to 14 per browser. These do contain addresses, because that is what they are for. | Until you delete the day in the app. |
| Your own Google key | Only if you connected one. Kept so your routes are billed to your Google account, and stored encrypted. Never shown back in full and never given to anyone else. | Until you press Disconnect. |
| Email address | Only if you typed one into the "three tricks" box. | Until you unsubscribe or ask for it to be removed. |
4. Why, and on what legal basis
Where the General Data Protection Regulation applies, these are the bases we rely on (Article 6):
- Planning your route — the addresses and the times. Performance of a contract, Article 6(1)(b): it is the service you asked for, and it cannot be done without them.
- Counting routes and enforcing plan limits — contract, Article 6(1)(b), together with our legitimate interest in running a free tier that is not drained by a script, Article 6(1)(f).
- Your plan and payments — contract, Article 6(1)(b). The payment itself is handled by Lemon Squeezy as merchant of record, which keeps its own records for its own legal obligations.
- Your own Google key — contract, Article 6(1)(b), and only because you chose to connect one.
- Where you are, if you press "use my location" — your consent, Article 6(1)(a). Your browser asks before anything happens and refusing costs you nothing: the app works exactly the same when you type the address instead. The coordinates are used once, to fill in that one box, and are not written into any record.
- The email address for the "three tricks" emails — your consent, Article 6(1)(a). You can withdraw it at any time, with the unsubscribe link in every email or by writing to us, and withdrawing it does not affect anything sent before.
- Keeping the app working and unabused — including the one alert described below. Legitimate interests, Article 6(1)(f): an app nobody can use is of no use to you either.
- Counting page views — legitimate interests, Article 6(1)(f). It is done without cookies and without an identifier, so it cannot single you out.
Under Israel's Privacy Protection Law you are never obliged to give any of this. Nothing in the app asks for a name, and the only fields that take personal details at all — an email address and your own Google key — are optional, marked as optional, and the app works without them.
5. Who else receives data
- Google Maps Platform. Every address you plan with is sent to Google to be located, searched around and routed. If you press "use my location" and agree, the coordinates your device reports are sent the same way, once, to be turned into a street address. When you use your own Google key, those requests go under your Google account and Google's terms for it apply to you.
- Google Apps Script. The app runs on Google's servers, which host the records in section 3.
- Cloudflare. This website is served by Cloudflare Pages, which sees the network address of anyone who loads a page, as any web host does.
- Umami (analytics). If switched on, it counts page views and button presses without cookies and without a personal identifier. It does not see your addresses.
- MailerLite. If you gave an email address, it is stored there for the three emails you asked for. Every email carries an unsubscribe link.
- Lemon Squeezy. Payments are taken by Lemon Squeezy as the merchant of record. Navido never sees your card details. Lemon Squeezy tells Navido which browser id paid, which plan, and the email address on the order.
- ntfy.sh — two alerts, two cases only. If the app's own permission at Google lapses, so that nobody can plan a route, your browser sends a single message to a notification service so the operator knows to fix it: the words "Navido needs re-authorising" and Google's own error text. And if you press "Report a problem", your browser tells the same service that somebody has reported one, in a single line naming only the app version and the language — never a word of what you wrote, because that address is a public one anybody can read; what you wrote goes by email, from your own mail app, to the address shown on the screen before you send it. Neither message carries your stops or your addresses, and each is sent at most once every six hours per browser. ntfy.sh sees your network address and your browser's user-agent string, as any website you visit does.
Nobody on that list is allowed to use what they receive for their own purposes beyond providing their service, and nothing is ever sold. There is no advertising network, no data broker and no profiling.
6. Where the data goes
Navido is operated from Israel, which the European Commission recognises as providing an adequate level of protection. Some of the services above are outside the European Economic Area — Google and Lemon Squeezy in the United States, ntfy.sh in Germany, MailerLite in the European Union, Cloudflare on a global network. Each acts under its own data processing terms, and where those involve a transfer out of the EEA they rely on the European Commission's standard contractual clauses or on an adequacy decision for the country concerned.
7. How long we keep it
The table in section 3 gives the period for each record. Two rules apply across all of them: the working copy of a plan is erased from the sheet the server uses as scratch space as soon as the answer has been sent, and anything still held for your browser id is deleted when you ask, within 30 days.
8. Your rights
Wherever you are, we offer all of these, and we do not charge for them or treat you differently for using them:
- To know what is held for your browser id, and to get a copy.
- To correct anything wrong or out of date.
- To delete it. In the app: Clear removes the plan, Disconnect removes your Google key, the cross next to a saved day removes that day, and clearing the site data in your browser removes everything held there. Write to us for anything on the server.
- To restrict or object to a use that rests on our legitimate interests, including the page counting.
- To take it with you — a copy in a machine-readable form.
- To withdraw consent you gave for the emails, at any time.
Under Israel's Privacy Protection Law you also have the right to review information held about you and to demand its correction or deletion where it is incorrect, incomplete or out of date.
Under California law: we do not sell personal information and we do not share it for cross-context behavioural advertising. We have not done so in the preceding twelve months, and we do not knowingly collect information from anyone under 16. The rights listed above are offered to every visitor, whichever state you are in.
To use any of them, write to support@excel-armor.com from the address you want to ask about, or from any address together with the browser id shown in the app's Advanced panel. We answer within 30 days. We may ask you to confirm the request from the same browser, because a browser id is all that identifies a record and we will not hand somebody else's saved days to whoever asks first.
9. Complaints
If you think we have handled your data wrongly, tell us first at support@excel-armor.com — it is usually the fastest way to put it right. You can also complain to a regulator: in Israel, the Privacy Protection Authority at the Ministry of Justice; in the European Economic Area or the United Kingdom, the data protection authority of the country you live in.
10. Automated decisions
The app chooses which petrol station or pharmacy to send you to, using the rules you set and the distances Google reports. That is the service, it changes nothing about you, and it has no legal or similarly significant effect, so it is not the kind of automated decision-making Article 22 of the GDPR restricts. There is no profiling of any kind.
11. Security
Everything travels over HTTPS. The server records are keyed to a random browser id rather than to a name. Your own Google key, if you connect one, is held on the server encrypted and never returned to a browser: the app only ever shows its last four characters. Payment card details never reach Navido at all. This website loads nothing from a third party and declares a strict content security policy that says so. No system is perfect, and if a breach ever affects you we will tell you and the regulator as the law requires.
12. Children
Navido is not aimed at children and is not intended for anyone under 16. It asks for no personal details from anyone. If you believe a child has given us an email address, write to support@excel-armor.com and it will be removed.
13. Representative in the European Union
Navido is operated from Israel and has no establishment in the European Union. Article 27 of the GDPR requires a representative in the Union, except where the processing is occasional, does not involve special categories of data on a large scale, and is unlikely to result in a risk to people's rights. Navido's processing of European visitors' data is occasional, involves no special categories, and is limited to the addresses needed to plan a route. On that basis no representative is appointed. This position is kept under review, and will change with the volume of use from the Union.
14. Changes
When this policy changes, the date at the top changes with it. A change that affects you materially will be said plainly in the app as well.