Privacy Policy

Account & profile:name, email, password (or passkey — we never see or store the passkey itself), photo, cover photo, bio, the level you’re heading for, an optional nationality (shown as a flag beside your town), membership number, location, an optional emergency contact, and an optional public web address (a short, resettable link and QR code to your profile) if you choose to set one.

Trip data: dates, times, duration, distance, vessel, crew and their role on the trip, weather and wind conditions, dictated or typed trip notes, photos you attach, and — only for trips logged via Quick Log — a GPS track of the route.

Vessels & crew:vessel details (name, type, make, model, length, photo) and crew details — either a name, photo, relationship, and optional contact email you type in yourself, or a direct link to another Saltlogger’s real account if you find and add them instead.

Training and qualifications:the courses and qualifications you add — the organisation, the course, whether you’re interested, have completed it or have had it checked, the dates, and an optional certificate number and expiry. If you upload a certificate for checking, the file itself is stored privately and can be seen by you and by Saltlog’s own reviewer; nobody else.

Boat costs: the costs you record against a boat — supplier, date, amount, VAT, currency, category, notes, reminder dates, and for fuel or servicing the litres or engine hours — and any invoices, receipts, PDFs or spreadsheets you upload to add them. The documents are stored privately and can be seen only by you.

Messages:direct messages between you and another Saltlogger, and messages in a Group’s chat rooms, including anything you attach such as a trip. Messages are stored on our servers so they reach the people you send them to and appear when you come back; they are not end-to-end encrypted. A Group’s admins can remove any message in their own rooms.

Live trip location:collected while you are actively using Quick Log to record a trip, for the sole purpose of building that trip’s route. If a boat has a SignalK navigation system connected, Quick Log may also use its own position data, blended with your phone’s GPS, taking whichever gives the better fix. If you turn on Automatic Log Start (optional, off by default, only available once a boat’s SignalK server is connected), Quick Log may use your background location before a trip has even started, purely to detect that you’ve genuinely got underway so a trip is never missed. We do not track your location at any other time — this is separate from the optional Launch Location described below.

Launch Location (optional):if you choose to add one to a vessel, a name, address, postcode, and GPS coordinates for the place that boat usually sets off from. Never collected automatically — you either search for it or use your device’s current location yourself, once per vessel, and can change or remove it at any time.

Your public profile:by default, your profile — name, photo, bio, primary vessel, a summary of your Vessels/Crew/Groups/Network counts — and your trip history are visible to anyone, including people who aren’t signed in. That is what makes Saltlog useful: it’s how people find crew, passages, schools and clubs. One setting in Settings (“Private account”) turns all of it off at once: with Private on, nobody but you can see your profile or your trips, including people who already follow you. If you’ve set a public web address or QR code, it’s reachable by anyone with the link while your account is open, and shows nothing once it’s Private.

Groups:if you create or manage a Group (for example a marina, club, or training school), the details you add — name, description, address, phone number, opening hours, amenities, photos, fleet, events, and any documents you upload — are visible to any signed-in Saltlogger, and the Group’s member list is visible to anyone viewing its page. If you join a Group, your own membership is visible there too.

Payment data:if you subscribe to Saltlog Plus or Founding membership, your payment is handled entirely by Apple (App Store) or Google (Google Play). We never see or store your card details. We receive, through RevenueCat, which plan you have, when it renews or ends, and whether a payment has failed — enough to switch your plan’s features on and off.

Basic technical data: the session information needed to keep you signed in.

• To provide the Service itself — this is necessary to perform our contract with you (our Terms & Conditions).
• To process subscription payments and manage your plan — contract necessity, via Apple or Google and RevenueCat.
• To send you account and billing emails (e.g. confirming sign-up, password resets, subscription changes) — contract necessity.
• To auto-fill weather when you use Quick Log — with your action (starting a trip) as the trigger; see “Third parties” below.
• To pre-fill your starting point when logging a trip against a vessel with a saved Launch Location — your own explicit action (adding one) as the trigger.
• To let you connect with other Saltloggers — your profile and trips are visible to other users by default, and Crew, Follow and Groups build on that. This is the open setting you agree to when you sign up; you can switch it off at any time with the “Private account” setting described in Section 1.

We do not sell your personal data to third parties. We may use information you provide — such as your location, your target qualification, or the vessels you own — to show you relevant recommendations or sponsored content within the app, including from affiliate partners. Your personal data is never handed to those partners; if you choose to click through to a partner’s site, their own privacy policy governs what happens from there.

Launch Location and marinas/clubs: we may also use the marina, club, or mooring names and addresses people record in Launch Location, aggregated across users rather than tied back to your individual account, to help us identify and build relationships with marinas and clubs about Saltlog. This is never used to reveal to a marina or club which of their visitors has a Saltlog account.

Crew-based suggestions:if another user has logged you as crew using the same email address your Saltlog account is registered with, we may match that email to suggest you to each other as people to follow — for example, letting them know you’re already on Saltlog, or showing you the skippers who’ve logged you as their crew. We never reveal your email address itself this way — only your name, and only to someone who already independently had that email on file from a real trip together. You can turn this off at any time in Settings (“Crew Discovery”); this does not affect someone finding you by deliberately searching your exact name or scanning your QR code.

Saltlog is built to let you connect with other boaters, so your profile and your trips are visible to other users by default — never sold, and never handed to a company for their own use. This is separate from the processors listed in Section 4, which are companies that run parts of the Service for us, not people you’re connecting with. Turning on “Private account” in Settings stops all of the sharing described below, other than the anonymised crew entry noted at the end of this section.

• Crew.If you tag a real, signed-in Saltlogger as Crew on a trip you’re tracking with Quick Log, we may create a copy of that trip’s core details (dates, times, vessel, distance, weather — not your photos, GPS track, or dictated notes) in their own account, and notify them. This only ever happens for trips tracked with Quick Log’s own live GPS, since that’s what lets us avoid creating a genuine duplicate if they’ve already logged the same voyage themselves. If someone signs up using an email address you’ve already added as Crew with no linked account, we automatically link that Crew record to their new account.
• Crew invitations by email.If you add someone as Crew using their email address and they’re not yet a Saltlog user, we may email them to let them know you’ve logged a trip with them, so they can view it, add it to their own account if they sign up, or ask us to stop.
• Follow.Following another Saltlogger brings their trips into your own Trip Feed, unless they’ve turned on “Private account”. Only trips logged on or after the day you started following them appear in your Feed this way — visiting their profile directly shows their full history. The same applies in reverse for people who follow you.
• Comments and reactions.If you can see a trip — your own, or any trip on an open account — you can react to it or leave a comment; your name and photo show alongside anything you post, visible to anyone who can see that trip. Commenting is itself an act of disclosure: turning on “Private account” later does not remove your name from comments you’ve already left elsewhere.
• QR code and public link. Your profile carries a resettable QR code, and an optional public web address if you choose to set one, either of which lets someone add you as Crew, follow you, or (from a vessel picker) reference one of your own boats.
• Groups.Anything you post, join, respond to, or ask a question about in a Group is visible to that Group’s other members or admin as described in Section 1.
• The Routes map.If you leave “Routes map” switched on in Settings, each GPS-tracked passage is also drawn as a line on a shared map on Explore, visible to every signed-in Saltlogger and to nobody else. The line is the real route, including where it starts and ends — the same track an open trip card already shows — but nothing on the map carries your name, your vessel or a date, and there is no way to tell which lines belong to the same person. You have three ways to stay off it: switch it off in Settings, which removes your existing lines as well as future ones; mark a single vessel “keep off the Routes map” on that vessel’s own page, which removes every passage logged against it; or set your account to Private, which leaves you off regardless of what either switch says.
• The People map. Explore has a map of Saltloggers, and you are on it unless you switch it off in Settings. Your pin is worked out from the address on your Contact details and deliberately coarsened to about a kilometre — enough to show the area you sail from, never enough to point at a house — and your exact address never leaves our database. Other Saltloggers see the same name, photo, town and country your profile already shows. Switching it off removes you at once, and a Private account is off the map regardless.
• Messages.You can message any Saltlogger whose profile you can see. People you’ve sailed with and people you both follow reach your inbox directly; anyone else’s first message waits in Requests until you accept it. Messages in a Group’s chat rooms are visible to that Group’s members and admins.
• Your Résumé and Reports. Saltlog can turn your own log into a Résumé or a printable report. These are built from data you already hold, are visible only to you inside Saltlog, and go no further unless you save or send them yourself.
• If your account is Private.One thing a Private account does not hide: where another skipper has logged you as crew on their own trip, you still appear on that trip as an unnamed crew member. The trip stays truthful about how many people were aboard, but your name, your photo and any link to your profile are all removed. Saltlog cannot delete someone else’s record of a voyage you were genuinely on.

We use a small number of service providers (“processors”) to run Saltlog, each only for the purpose stated:

• Supabase — hosts our database, authentication, and file storage.
• Vercel — hosts the website and app itself.
• RevenueCat, Apple and Google— process subscriptions bought inside the Saltlog app, through the App Store and Google Play. RevenueCat tells us which plan you have and when it renews or ends, linked to your Saltlog account’s id; we never receive your card or your Apple or Google account details.
• Resend— sends the emails we send you directly (welcome, subscription updates, Crew invitations) and, via Supabase’s own mail configuration, sign-up confirmation and password reset.
• Apple Weather (WeatherKit) and OpenStreetMap (Nominatim) — when you use Quick Log, your current coordinates are sent to these services to look up the weather and a place name, without your account details attached — they only ever receive a latitude and longitude. Map tiles themselves are fetched and cached through our own servers rather than sent directly from your device, so OpenStreetMap and OpenSeaMap never see your device or account at all for those.
• Your browser or device’s own speech recognition— if you choose to dictate a trip log or note, the words you speak are turned into text by your browser’s built-in speech recognition, or, inside Quick Log, by your phone’s own speech recognition (Apple on iOS, Google on Android). On an iOS device and language where Apple’s newest on-device recognition is available, this happens entirely on your phone; where it isn’t, or on Android, the audio is processed by Apple’s or Google’s own servers to produce the text. We never record or store the audio itself, and no paid transcription service is ever used. Dictation is always optional — typing works exactly the same as talking.
• Anthropic— provides the AI behind Deckhand. Only when you ask Deckhand to do something, we send Anthropic what that task needs: a photo or PDF of an invoice or receipt you want read, the headings and a few sample rows of a costs spreadsheet you import, a photo of a paper logbook page you want scanned, or the public text of a website you ask it to turn into a Group page. What comes back is always shown to you to check before anything is saved. For an invoice we also send your boats’ names, so it can tell which boat it’s for. Your name and account details are not sent, and under Anthropic’s commercial terms it doesn’t use what we send to train its models.

Sharing a trip outside Saltlog.If you generate and share a trip image (to Instagram, WhatsApp, or elsewhere), that image is created on your own device and handed to your phone’s or browser’s own share screen — we don’t send anything to those platforms ourselves. You control whether the image includes your exact location, in Settings, and can override that per trip too.

We do not share your personal data with any other third party for their own use, and none of the processors above are permitted to use your data for their own purposes. (This is separate from the affiliate recommendations described in Section 2 — those never involve handing your personal data to the partner.)

We keep your account and trip data for as long as your account is active. In line with treating your logbook as a genuine historical record, we don’t delete a vessel or crew member you’ve used on a trip — removing one from active use archives it rather than deleting it, so your past trips always keep an accurate record of what vessel or who was actually involved. A Group is kept for as long as it exists; if it’s ever deleted, its own fleet vessels are kept and moved into your own personal vessel list rather than deleted, for the same reason.

A certificate you upload is kept until you remove that qualification or your account. An invoice, receipt or other cost document is kept until you delete the cost or capture it belongs to, or your account. Messages are kept until your account is deleted, though a copy stays with the person you sent them to, in the same way as any other message.

Rows you upload via Bulk Import that don’t automatically process (“Exceptions”) are kept indefinitely until you either fix or explicitly discard them yourself — there is no automatic deletion.

Under UK data protection law, you have the right to:

• access the personal data we hold about you;
• correct inaccurate data — most of your own profile, trip, vessel, crew, and Group data can be edited directly in the app at any time;
• request erasure of your data;
• object to or restrict certain processing;
• request a copy of your data in a portable format.

Deleting your account. You can permanently delete your own account at any time, from Settings, without needing to contact us. This deletes your trips, vessels, Crew, photos, boat costs and the documents behind them, comments, reactions, and any Group memberships. Purchase and Founding Member redemption records are kept, with your name removed from them, for accounting and support purposes — everything else about them (price, date, what was purchased) stays as-is. This can’t be undone.

To request a copy of your data, or to exercise any of the other rights above, contact us at hello@saltlog.co.uk and we will action it directly. You also have the right to complain to the UK Information Commissioner’s Office (ico.org.uk) if you believe we have mishandled your data.

Your data is protected by row-level security in our database, meaning the system itself enforces exactly which rows you (or, where you’ve chosen to connect with someone, they) can access — this isn’t just a setting in the app’s interface. We use industry-standard encryption in transit and at rest via our infrastructure providers.

Saltlog is not directed at children. You must be at least 16 to create an account (see our Terms & Conditions).

There is one current policy, the one on this page, and the “last updated” date above tells you when it changed. If we make a change that materially affects your privacy — a new kind of data, a new reason for using it, or a new recipient — we will tell you in Saltlog itself, the next time you open it, before the change takes effect, rather than quietly updating this page. Where the law requires your consent we will ask for it rather than assume it.

hello@saltlog.co.uk

Or by post: Saltlog Ltd, 1 Chester Road, Branksome Park, Poole, Dorset, BH13 6DD.