Privacy Policy

Last updated 15 October 2026 · The website's privacy notice links a short summary in its nine languages.

1. Who is responsible

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 both ways to use it: the website navigate.boats and the Navigate Boats iPhone app. Contact for anything privacy-related: contact@navigate.boats.

2. Using Navigate Boats without an account

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):

Your position: where the phone is, and how accurate that is. Nothing reads your speed, course or compass heading. The iPhone app takes it once per visit to Plan, and only while Plan leaves from Where I am, which it does until you pick another place: the first fresh fix within 100 m, then it stops reading your location. It stops too when you open another tab or leave the app. It never reads your location in the background, and it asks for your location only while you are using it. It also takes one fix when Setup asks where you keep the boat, and only compares it on the phone with the towns, harbours and anchorages the app carries (from OpenStreetMap), to offer the nearest. It isn't kept, except as the base of a trip you plan from Where I am.
Recorded trips: what earlier versions recorded on their Navigate tab — a trip's start and end time and its track, which is the time, position, speed, course and accuracy of each point. Version 2.2.0 has no Navigate tab: it records nothing, and writes nothing to the trips already on the phone. They stay there until you delete them (§6).
Your places (up to 200), the destination you pick, and the place you search for on Plan to leave from.
Your mooring: the town, harbour, anchorage or buoy field you pick in Setup (its name and position, which list it came from and its kind, such as marina or buoy field), a place you search for, or a point you drop on the chart, named by its position. Never your phone's position.
Your boat: type, size and whether kids are aboard, as you answer them on the Account tab. They stay on the phone even when you are signed in.
Settings: sounds and units, that you accepted the not-for-navigation notice, whether you skipped or finished the three tips on Now, and which sign-in method each account used on this phone. The sign-in method goes when you sign out of that account or delete it on the phone.
Forecasts for the places the iPhone app shows you, each with the time it arrived, so a verdict still shows without a connection for the next 24 hours. They aren't in the phone's backups.

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.

3. If you create an optional account

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:

Account data: your email address, an internal user ID, and, if you use Google or Apple, that account's ID and whatever name, profile picture or relay email address it returns. With “Hide My Email”, Apple gives us a private relay address instead of your real one.
Setup from the website: language, home location, boat type and size, kids-aboard setting, corrected mooring positions, and your saved spots (name, coordinates, exposure rating).
Trips you save to “My trips”, on the website or in the iPhone app: its name, its base, the place or places it goes to (coordinates and name), the cruise speed and distance when saved. We do not store the drawn route, dates, when you open a trip, or any notes.
A trip planned from Where I am in the iPhone app leaves from your phone's position, and saving it sends that position. The iPhone app names the base by that position, to three decimals, such as “43.940° N, 15.440° E”, and unless you type a name, the trip's name starts with it too. We keep both names as they are sent, and the base itself as one of the website's own locations when the trip leaves within 8 km of its mooring, or otherwise as the position rounded to about 100 m. So we keep your position to about 100 m even when the base is one of the website's own locations. If you open the trip on the website, the website switches to its base, as for any trip from another base, and that base becomes the home location in your setup.
Technical data: sign-in timestamps, and IP address and browser or iPhone app details in security logs kept by our database provider.

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.

4. Why we process it (legal basis)

Providing the account and sync you asked for: performance of a contract, Art. 6(1)(b) GDPR.
Keeping the service secure and preventing abuse (security logs, rate limits): legitimate interest, Art. 6(1)(f) GDPR.

Your data is never sold, shared for marketing, or used for profiling or automated decisions.

5. Service providers (processors and third parties)

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 or the iPhone 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; 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 and in the iPhone 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 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.

6. How long we keep it

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.

7. Your rights

You can at any time:

Access and export your data: on the website, My trips → Download my data (top right once signed in) gives you everything stored with your account as a JSON file (Art. 15, 20). What the iPhone app keeps only on the phone (§2) isn't in it, and the iPhone app has no download, so use the website with the same account.
Correct it: edit your setup, spots and trips on the website (Art. 16).
Delete it: My trips → Delete account on the website, or Account → Delete account in the iPhone app, permanently erases your account and all its data, trips included (Art. 17). A single saved trip can also be deleted: under “My trips” on the website, or (from version 2.2.1) in the iPhone app. If you signed in with Apple, the iPhone app (from version 2.2.0) first asks you to confirm on Apple's sheet, and Apple then revokes Navigate Boats' Sign in with Apple authorization. Only Cancel on that sheet stops the deletion: otherwise your account is deleted whatever Apple answers. On the website, if you signed in with Apple, you're asked to sign in with Apple once more, and Apple then revokes Navigate Boats' Sign in with Apple authorization. If you cancel at Apple or leave its page, nothing is deleted. Once Apple's one-time code is back, your account is deleted whatever Apple answers to the revocation. On the website and in the iPhone app alike, the tokens from Apple this takes are used once and never stored. Trips in the iPhone app still waiting to be sent aren't in your account yet, so they stay on the phone (§6).
Object to or restrict processing (Art. 18, 21) by emailing us.

For anything the website or the iPhone 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.

8. Security

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.

9. Changes

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.