Navigaze privacy policy
Last updated 11 September 2026
Navigaze knows where you are, so this page has to be specific rather than reassuring. It says what leaves your phone, who receives it, how long it is kept, and how to get rid of it.
1. Who we are
Navigaze is sold by Sufi Plugins (Lucas Crowley), Maryland, USA, and built with Dawson Margeson. Sufi Plugins is the controller of the personal data described here. Contact: help@navigaze.org. Postal address available on request at help@navigaze.org.
Navigaze is an independent app for Even Realities G2 glasses and is not affiliated with Even Realities. The app runs on your phone; the glasses are a display and a set of gestures. There is no Navigaze account: a Pro subscription is a licence key, not a login.
2. What Navigaze handles, and why
Most of what Navigaze keeps stays on your phone. What leaves it does so to answer a request: to find a place, draw a route, read a speed limit, show a nearby report, or back up your places. This table is the whole picture; the sections after it explain the parts that need more than a line.
| Data | Why | Where it goes | How long |
|---|---|---|---|
| Saved places (home, work, favourites), recent destinations, saved routes, settings | To run the app | Your phone. Copied to our cloud backup if you are on Pro and backup is on (it is on by default) | On your phone until you delete them. In the backup until you switch backup off, delete it, or 2 years after the last backup |
| Trip history (origins, destinations, times), workouts, Health Connect totals | Predicted destinations, and your own workout log | Your phone only. Removed from the cloud backup on the way in and on the way out | Until you clear them in Settings or uninstall |
| Your position, while the app is open, in the lookups it makes | Speed limits, routing, nearby alerts, weather, transit, rentals | To the map and data providers named in Location, either straight from your phone or through our server | Not stored by us, except: your last speed-limit position is held on our server for up to 1 hour (Pro), so the same stretch of road is not billed twice |
| Search text (an address or place name) | To find it | To OpenStreetMap search services straight from your phone, and to TomTom search through our server | Not stored by us |
| A random install identifier | To give every install free speed limits and address search within a daily cap, and to count daily active installs | Our server | One small usage record per install (first day seen, number of active days, recent dates), kept while the install is active; daily heartbeat marks expire after 2 days |
| Alerts you report (type, position, time) with a random reporter id | So nearby drivers see them | Our community server | Between 30 minutes and 4 hours depending on type; camera reports up to 90 days |
| Your position about once a minute, with a random per-launch id, while community alerts are on and the app is open | To fetch the reports near you and, only if you switched sharing on, to show your dot to others | Our community server, in memory only | Served to others only after a 90-second delay and never after 10 minutes; if sharing is off it is not stored at all |
| Short voice clips, while you run a voice search or command (Pro) | To turn speech into text | Through our server to a commercial speech-to-text provider | Not stored by us |
| Convoy positions, chat and voice, while a group ride runs | To share them with your group | Our Convoy relay. Positions and chat are encrypted end to end on your phone; voice is mixed on the relay, so it is not end-to-end encrypted | Not stored; forwarded while the ride runs |
| Your licence and subscription: email address, PayPal subscription id, plan and status | To give you Pro, email your key, handle billing and support | Our subscription server; PayPal handles the payment | While you are a customer, and afterwards as long as tax and accounting law requires |
| Monthly request counters per licence | Cost control and spotting abuse | Our subscription server | Rolling monthly totals |
| Approximate location from your internet connection (country) | To apply country rules on camera and police alerts, and to count active installs per country | Derived at Cloudflare's edge for that request | Only as a daily total per country; never stored against your install id or licence |
| API keys, media-service tokens, Strava tokens, if you add them | To use those services | Your phone only. Sent only to the service each belongs to; never in the cloud backup | Until you remove them |
We do not sell your data, we do not show ads, we do not use third-party trackers, and we do not share your data for advertising. We keep no history of your movements.
3. Location, in detail
Navigaze uses your phone's location to show your position, give directions, read the speed limit and find what is nearby. A lookup carries the coordinates it is about, and nothing else identifies you unless the row above says so. Where each kind of request goes:
- Straight from your phone to an open provider, free: map tiles (OpenFreeMap); map data, places, speed limits where the road is mapped, and camera locations (OpenStreetMap and Overpass, plus the public camera feeds listed in the app); search (Photon and Nominatim); routing (Valhalla, OSRM); weather (Open-Meteo); EV chargers (Open Charge Map); transit departures (Transitous). Those services see your IP address and the request, under their own terms.
- Through our server, on every install: address search and posted speed limits from TomTom. Our server adds the TomTom key so you do not need one, tags the request with your random install identifier, and passes it on. It keeps no log of where you searched. For Pro users it holds your last speed-limit position for up to an hour so that a repeat lookup on the same road is not billed again.
- Through our server, with Pro: traffic-aware routing (TomTom), live community traffic reports (OpenWebNinja, which receives the area of the map you are looking at), voice search, shared bikes and scooters, and cloud backup.
- With your own API key: the request goes straight from your phone to that provider (for example TomTom, HERE, Google Routes, Mapbox), under its terms. Your key stays on your phone.
Predicted destinations are worked out on your phone from your own trip history, which is never uploaded. You can turn prediction off, or clear the history, in Settings. If you paste a Google Maps share link, our server opens that link to read the coordinates out of it and returns them; it does not keep the link.
The country your connection arrives from is used for two things: to switch camera and police alerts off where the law forbids them (see the next section), and to count how many active installs there are per country. It is never stored against your install identifier.
4. Community alerts and nearby drivers
Community alerts are on by default. While the app is open, it sends your position about every 60 seconds so that the reports near you can be shown. That beacon carries a random id created fresh each time the app launches, so sightings cannot be linked across sessions. It stops when the app is closed or in the background.
Showing your own position to other drivers is off by default. If you switch "Show me on the map" on, your dot is stored in memory only, rounded to about 110 metres, shown to others only once it is at least 90 seconds old, and dropped after 10 minutes. At most two points per id ever exist, so there is no trail. If sharing is off, your position is not stored at all: you still see others.
Reports you submit contain the type, the position, the time and a random reporter id: no name, account or contact details. They expire on their own: police reports after 30 minutes, traffic after 30 minutes, collisions after 90 minutes, hazards after 2 hours, closures after 4 hours, and camera reports after 90 days. Confirming a report renews its life for the same period.
Camera and police alerts are off by default, and our server does not send or accept them for connections from France, Switzerland, Germany, Austria, Cyprus, North Macedonia, Turkey, Ireland, Slovakia, Bosnia and Herzegovina or Belarus, where warning services of that kind are unlawful. This is keyed on the country your connection comes from and applies to every version of the app. It does not make such alerts lawful anywhere else; that is your responsibility (see the Terms).
5. Cloud backup (Pro)
Cloud backup is a Pro feature and is on by default, because a lost phone used to mean setting the whole app up again. It copies your home and work, favourites, recent destinations, saved routes and settings to our server, retrievable only with your licence key. It does not contain your trip history, workouts or Health Connect data (our server removes those rows even if an older build sends them), and never your licence, API keys, media-service tokens, Strava tokens or install identifier.
Switch backup off in Settings and the server copy is deleted. Otherwise each new backup renews a two-year expiry, so a backup nothing has written to for 2 years expires on its own. You can also ask us to delete it at any time, including after your subscription has ended, and you can restore it with your key after a lapse.
6. Voice search and the microphone
The microphone is used only while you run a voice search or a voice command. Navigaze does not record, store or listen in the background.
- Pro: the short clip goes through our server to a commercial speech-to-text provider, which transcribes it and hands the text back. Our server adds the key and passes the audio through; it does not keep it.
- Your own key: the clip goes straight from your phone to the provider you picked in Settings (Groq, OpenAI, Deepgram, Soniox, AssemblyAI, Speechmatics, Gladia, Rev AI or Google STT), under that provider's terms.
- Local Vosk: recognition runs on your phone and nothing leaves it.
7. Shared bikes, scooters and transit
With Pro, Walk and Transit modes can show the nearest shared bike or scooter. Your approximate position goes to our server, which reads the operators' public GBFS feeds and CityBikes on your behalf and returns what is nearby. Your phone never contacts an operator, and no operator learns anything about you. Turn it off in Settings, under Bikes and scooters.
Transit departures and routes come from Transitous, straight from your phone. If you add your own HERE or Google key, transit requests go straight to that provider instead.
8. Convoy (group rides)
Convoy is opt-in. While a ride is running, your position and chat messages are encrypted on your phone with a key derived from your group's password and passed through our Convoy relay to the others in the group; the relay forwards that traffic and cannot read it. Push-to-talk voice is different: the relay mixes the audio streams of the group, so it handles voice unencrypted in memory while the ride runs. Nothing is stored. Leaving the group stops all sharing. Only share a Convoy with people you trust, and never use it to follow someone without their knowledge.
9. Workouts, Health Connect and Strava
Completed workouts are saved on your phone. On Android, with AppsBridge and your Health Connect approval, Navigaze can read recent Health Connect totals and workouts and write Navigaze workouts back to Health Connect; that data stays on the phone and is excluded from the cloud backup. If you connect Strava (Pro) and choose to send a ride, Navigaze uploads that ride's GPX track straight from your phone to Strava under Strava's terms; your Strava tokens stay on your phone.
If you connect Spotify, Navidrome, Music Assistant or Apple Music, those tokens are stored on your phone and used only to show and control playback. Signing in to Spotify goes through a Navigaze-hosted redirect page that only hands the sign-in code back to the app and stores nothing.
10. App usage counts and diagnostics
Navigaze sends a periodic heartbeat to our server carrying a random install identifier and which HUD mode you have open, and nothing else. From it we count how many installs are active each day, which modes people use, and, from the country your connection arrives from, how many active installs are in each country, so we know where to improve maps and speed limits. Those are kept as running daily totals; no country and no location is ever stored against your install identifier.
There is no automatic crash or error reporting. If you tap "Send debug log", Navigaze opens your email app with a technical log, and nothing is sent unless you send that email.
11. Pro, payments and email
Pro is optional. Checkout runs through PayPal, which is an independent controller of what you give it; we never see your card or bank details. Our subscription server stores your licence key, plan, subscription status, PayPal subscription id and the email address PayPal reports, so your Pro access can be checked and your key emailed to you. Your licence key is kept on your phone and sent only to our server, where it works like a password.
We use your email address for two kinds of mail:
- Account mail you cannot opt out of while you are a customer: your licence key, trial and billing notices (including when a renewal payment fails), and replies to your support messages.
- Product news and tips to Pro subscribers and trial users: occasional emails about what has changed, including a few during and after your trial. Every one carries a one-click unsubscribe link and the sender's identity; you can also reply "unsubscribe" or email us. Unsubscribing stops all marketing mail.
Our email provider records whether a message was delivered, bounced or opened (a standard invisible pixel), which is how we tell whether an announcement reached anyone. We do not build profiles from it.
12. Service providers
These are the companies that process data for Navigaze. Each receives only what the request it answers needs, and each is bound by its own terms.
| Provider | What it does for Navigaze | Privacy policy |
|---|---|---|
| Cloudflare | Hosts this website, runs our servers, and stores licences and cloud backups | cloudflare.com/privacypolicy |
| TomTom | Address search and posted speed limits (every install); traffic-aware routing (Pro) | tomtom.com/privacy |
| OpenStreetMap and OpenFreeMap | Map data and map tiles; Photon, Nominatim, Overpass, Valhalla and OSRM are services built on OpenStreetMap data | osmfoundation.org privacy ยท openfreemap.org |
| OpenWebNinja | Live community traffic reports (Pro): receives the map area, not your identity | openwebninja.com |
| A commercial speech-to-text provider | Voice search on Pro, through our server | Named in the app under Settings, Privacy and legal |
| Open-Meteo, Open Charge Map, Transitous, GBFS operators and CityBikes | Weather, EV chargers, transit, shared bikes and scooters | Their own sites |
| PayPal | Takes the payment and manages the subscription. PayPal is an independent controller of what you give it | paypal.com privacy |
| Resend | Sends our email | resend.com/legal/privacy-policy |
Map data is © OpenStreetMap contributors, under the Open Database Licence. If you bring your own API keys, your requests go straight from your phone to the provider you chose (TomTom, HERE, Google, Mapbox, or one of the speech providers listed above), under their terms, and we never receive them. If you connect Strava, Spotify or another media service, that service receives what you send it.
13. International transfers
We are in the United States and our servers and providers are mostly in the United States, so if you are outside it your data is transferred there. Where that transfer needs a legal mechanism, our providers offer the European Commission's standard contractual clauses (and the UK addendum) in their data processing terms, and several are certified under the EU-US Data Privacy Framework. Ask us and we will tell you what applies to a particular provider.
14. Legal bases (UK and EU)
- Performance of a contract: running Navigaze for you: search, routing, speed limits, alerts, backup, your licence and billing.
- Legitimate interests: keeping the service secure and working, preventing abuse of the paid data, understanding which features are used, applying country rules on alerts, and telling existing customers about changes to the product. You can object at any time.
- Consent: showing your position to other drivers, Convoy, Health Connect, Strava, and cloud backup where local law requires consent for it. You can withdraw consent by switching the feature off, which stops the processing from then on.
- Legal obligation: keeping tax and accounting records of what you paid.
15. Your rights and deletion
Wherever you live, you can ask us to:
- Tell you what we hold about you, and give you a copy.
- Correct anything wrong.
- Delete it: your cloud backup, your licence record, your usage record. Places, routes, history and workouts can be deleted in the app yourself. Uninstalling the app does not delete the records on our server: email us and we will. You can ask even if your subscription has ended.
- Export it: ask us and we will send what is on our side.
- Object to processing based on legitimate interests, and withdraw consent for anything you switched on.
Email help@navigaze.org. You do not need to cite a law and we will not charge you or make it difficult. We answer within 30 days, usually much sooner. If you are in the UK or EU you can complain to your national data protection authority. If you are in California, you may ask what we collect and ask us to delete it, and we do not sell or share personal information for cross-context behavioural advertising. If you are in Brazil, the LGPD gives you equivalent rights.
16. Children
Navigaze is for adults. You must be 18 or older to use it, we do not knowingly collect data from anyone under 18, and if we learn that we have, we delete it. If you believe a child has used Navigaze, email help@navigaze.org.
17. Security
Everything travels over HTTPS. Server-side data sits in Cloudflare's storage and a backup is reachable only with your licence key, which works like a password: keep it to yourself, and tell us if you think it has leaked and we will issue a new one. Your API keys and service tokens never leave your phone except to the service they belong to, and are excluded from the cloud backup. Convoy positions and chat are encrypted on your phone before they reach our relay. No system is perfect; if you find a security problem, email help@navigaze.org and we will treat it as urgent.
18. Changes to this policy
If this page changes in a way that affects what we do with your data, we update the date at the top and email subscribers. We will not quietly widen it. What has changed so far:
- August 2026: in-app policy first published.
- 11 September 2026: first published on the web, rewritten. Who we are and where; every retention period stated; searches and speed-limit lookups correctly described as passing through our server on every install; the server's one-hour last-position record disclosed; cloud backup described, with trip history, workouts and health data removed from it; community beacon cadence, delay and defaults stated; camera and police alerts made off by default and switched off by country on the server; Convoy voice correctly described as not end-to-end encrypted; named service providers; legal bases, your rights, deletion after uninstall; the age limit set at 18.
19. Contact
Questions, a deletion request, or anything unclear: help@navigaze.org. We answer within 30 days and usually the same week.
Navigaze is sold by Sufi Plugins (Lucas Crowley), Maryland, USA, and built with Dawson Margeson. Postal address available on request at help@navigaze.org. Navigaze is not affiliated with Even Realities. · Terms · Accessibility · Navigaze