Navigate Boats is a free, non-commercial personal project run by Blaz Umek, Slovenia, who is the data controller under the EU General Data Protection Regulation (GDPR). This policy covers all three ways to use it: the website navigate.boats, the Navigate Boats iPhone app and the Navigate Boats Android app (package boats.navigate.app). Contact for anything privacy-related: contact@navigate.boats.
You can use every weather and trip-planning feature without signing up, on the website and in the iPhone app. In that case we collect no personal data on a server. No analytics, no advertising, no tracking cookies. Saving trips to “My trips” is the one feature that needs an account (§3).
On the website, your setup (language, home location, boat type and size, whether kids are aboard), your saved spots, mooring corrections, dropped map pins, map-layer choices and whether you have dismissed the sign-in offer are kept only in your own browser's local storage and never sent to us. To show forecasts and maps, your browser contacts Open-Meteo and the map tile services in §5 directly, and DHMZ through our own host. It asks Open-Meteo for the weather at the places you see, at fixed points on the sea in their DHMZ sea regions (the same points for everyone, so the verdict reads the whole area) and at up to 24 points along a route you draw on the map. It fetches DHMZ's wind warnings through our own host, which asks for the same files for every visitor and sends no coordinates. Like any website, the services it contacts see your IP address and the map area or coordinates being requested.
In the iPhone app, these stay on your phone and are never sent to us, except inside a trip you save to your account (below):
The others are in the phone's backups. Saving a trip to your account sends its base and its stops (§3), so a trip you plan from Where I am sends your phone's position as its base, which we keep, to about 100 m, in the base's name.
The iPhone app calls Apple Maps, Open-Meteo and DHMZ directly from the phone, not through navigate.boats, and sends them no account data (§5). It asks Open-Meteo for the same kinds of points as the website: the places it shows you, the fixed points on the sea in their regions and up to 24 points along a trip you plan. The start of a trip from Where I am is never one of them: the iPhone app never sends the phone's position to Open-Meteo, and only looks up on the phone which sea region it lies in. It has no analytics, advertising or crash-reporting code.
The Android app has no account, and its Sign in with Google row in Settings is refused before anything is sent. It has no location permission and never reads where your phone is. The Android app sends nothing until you have accepted the not-for-navigation notice and kept a boat and a mooring in Setup.
After that, Now asks Open-Meteo for the forecast of one place, your destination if you have set one and otherwise your mooring, and sends the latitude and longitude of that place at full precision. You pick it from the coastal towns the Android app carries, or by pasting coordinates, and the place search runs on the phone, so what you type is never sent. The same request carries the latitude and longitude of fixed points on the sea in that place's DHMZ sea region (the same for everyone, so the verdict reads the whole area). Now also asks DHMZ for its public wind-warning files, which are the same for every phone, and sends no coordinates with that request.
The Android app calls Open-Meteo and DHMZ directly from the phone, not through navigate.boats. Both services see your phone's IP address. The Android app's requests to Open-Meteo carry a User-Agent that starts with NavigateBoats/ and ends with (boats.navigate.app), the same on every phone and not an ID. Its requests to DHMZ set no User-Agent of their own, so they carry Android's standard one, which names the Android version and the phone model.
The Android app keeps your boat, your units and text size, that you accepted the notice, and your mooring and destination on the phone, and sends none of them to us: only the coordinates of the place Now shows go out, to Open-Meteo. It keeps the forecasts and wind warnings it fetched, each in a file on the phone, and asks Android not to back up its data. The Android app has no analytics, advertising or crash-reporting code, and it does not read the advertising ID.
Signing in (with Google, Apple, or a one-time link sent to your email) gives you one account for the website and the iPhone app. On the website it syncs your setup across devices, and your trips show on both. Then we store:
We do not collect phone numbers, addresses or payment details, and we do not track your location: your position, and the trips earlier versions of the iPhone app recorded, stay on the phone (§2), apart from the base of a trip you save from Where I am. Dropped map pins, map-layer choices and the dismissed sign-in offer stay in your browser even when you are signed in. The website keeps a sign-in session token in your browser's local storage, and the iPhone app keeps its own in the phone's keychain. This is strictly necessary to keep you signed in, so it is not used for tracking and needs no consent.
Accounts are for people aged 16 or older.
Your data is never sold, shared for marketing, or used for profiling or automated decisions.
| Provider | Purpose | Data | Location |
|---|---|---|---|
| Supabase Inc. | Database and sign-in | Account data, setup, trips, security logs | EU (Frankfurt, Germany) |
| Resend | Delivering sign-in emails | Your email address and the sign-in email | EU (Ireland) |
| Google LLC | “Sign in with Google”, only if you choose it | Google account identifiers | USA (EU–US Data Privacy Framework) |
| Apple | “Sign in with Apple”, only if you choose it | Apple account identifier, email or private relay address | EU (Ireland) / USA (EU–US Data Privacy Framework) |
| Apple (Apple Maps) | The chart on Plan in the iPhone app (MapKit), loaded from the phone | IP address, the map area shown (on Plan around a trip that can start where you are), no account data | EU (Ireland) / USA (EU–US Data Privacy Framework) |
| Cloudflare, Inc. | Website hosting, DNS and the DHMZ proxy | IP address, request logs | USA / global CDN (EU–US Data Privacy Framework, SCCs) |
| Open-Meteo | Weather and sea forecasts and place search, called directly from your browser, the iPhone app or the Android app | IP address; the coordinates of the places you see weather for, of fixed points on the sea in their DHMZ sea regions (the same for everyone) and of up to 24 points along a route you draw or a trip you plan, never the start of a trip from the phone's position (the iPhone app never sends your phone's own position); the text you type in a place search. The Android app sends only the latitude and longitude of the one place Now shows, at full precision, and of the fixed points on the sea in its DHMZ sea region, and no typed text; no account data | EU / various |
| DHMZ (Croatian Meteorological and Hydrological Service, meteo.hr) | Croatian marine observations on the website, and the wind warnings (its public CAP warning files) that raise the verdict on the website, in the iPhone app and in the Android app | On the website, fetched through our own host (Cloudflare), not by your browser. The iPhone app fetches the warning files directly from meteo.hr, which then sees the phone's IP address. The Android app fetches them directly from meteo.hr as well. The Android app sets no User-Agent of its own on that request, so Android's standard one goes with it, which names the Android version and the phone model. The files are the same for everyone: no coordinates and no account data are sent | EU (Croatia) |
| Esri, OpenStreetMap, OpenTopoMap, OpenSeaMap | Map tiles on the website | IP address, map area, no account data | Various |
The website's “Buy me coffee” link opens Ko-fi only if you click it. Ko-fi's own privacy policy applies there.
Account data, setup and trips are kept until you delete your account. Spots you delete are marked deleted so the deletion reaches your other devices, and are erased together with your account. Trips you delete are marked deleted the same way and erased completely by a weekly clean-up once they are 90 days old, so within 97 days. From version 2.2.1 you can also delete a saved trip in the iPhone app, not only on the website. Either way, it goes from the website and the account's other devices. When you sign out, the copy of your trips in that browser is removed. The Navigate Boats iPhone app keeps a copy of your trips on the phone while you're signed in, so they show without a connection. That copy is left out of the phone's backups and deleted when you sign out. The sign-in session is kept until you sign out. The iPhone app's session stays in the phone's keychain even when the iPhone app is deleted, so sign out first. Security logs are kept only for the short period set by our providers. Deleted data can remain in provider backups for a limited time until they rotate out.
In the iPhone app, a trip you plan while signed out, or one not sent yet, waits on the phone. It stays there when you sign out, and is sent to the next account that signs in on that phone. From version 2.2.0 it is that trip's only copy, so it is in the phone's backups, unlike the copy of your saved trips. Your places, the destination, the place you leave from and your mooring stay until you remove or replace them. A recorded trip stays until you delete it or the iPhone app. From version 2.2.0 you delete it on the Trips tab, under Recorded: swipe the row, then confirm. It goes with every point of its track, and nothing is sent anywhere. A trip an earlier version left open is listed there too, ended at its last point, and deletes like any other. Your boat and your settings stay until you delete the iPhone app, and the sign-in method goes sooner, when you sign out or delete your account on the phone.
The Android app keeps its forecasts and wind warnings in files on the phone. A forecast is shown for up to 24 hours after it arrives, and the files stay until a later fetch replaces them or you delete the Android app. Your boat, units, text size, mooring and destination stay until you change them or delete the Android app, and the accepted notice stays until you delete the Android app. We hold none of this.
You can at any time:
For anything the website, the iPhone app or the Android app doesn't cover, email contact@navigate.boats. We reply within one month. You also have the right to complain to a supervisory authority, in Slovenia the Information Commissioner (Informacijski pooblaščenec), Dunajska cesta 22, 1000 Ljubljana, www.ip-rs.si, or the authority where you live.
Data is encrypted in transit (HTTPS) and at rest by our database provider. Database access rules make each account's data readable and writable only by that account. If a breach ever risks your rights, we notify the supervisory authority within 72 hours and affected users without undue delay.
If this policy changes in a meaningful way, we update the date above and show a notice on the website before the change takes effect, and in the next version of the iPhone app.