Privacy policy

Privacy policySeamark is a voyage log. This page says what it keeps about you, where it keeps it, and who else can see it. Last updated 7 October 2026.Who runs itThe line at the foot of this page names who operates this Seamark instance and how to reach them. Write to them with any question about your data, or to have your account deleted.What is stored

Your account: your email address, your name, your language and your choice of email notifications.

Your log: trips, legs with their times, places, positions, distances and weather, the GPX files you upload (kept as uploaded, beside the cleaned track), ships, charter details such as the company, contract and price, and your notes.

Your address book: the people you add as crew — a name and, only where you fill them in, birth date and place, citizenship, passport number and expiry, a contact note, an email address and your notes about them, plus a note on each crew place.

Sign-in and access: your sessions, API tokens and connected agents, each with when it was created and last used, and unused sign-in links. Of each secret only a one-way fingerprint is stored, never the secret itself.

The public share links you create and the crew invitations you send.

Where it is keptAll of it is in one SQLite database and a folder of GPX files on the server that runs this instance. Both are backed up every night; backups are kept for a limited time, and may also be kept away from that server. The administration screens show the operator your account — email address, name, language, when you signed up and were last active, which accounts are linked as whose crew — and how much you have stored, never your passport or birth details. The operator, who runs the server, could still read the database itself.The web server and the app log each request with the IP address it came from; the web server also logs the browser and the referring page. Sign-in, invitation and share secrets are removed from those logs.Cookies and your browserSeamark sets one cookie: the session cookie that keeps you signed in, for up to 90 days. Your browser’s local storage keeps your language, display choices such as the map’s sea-marks layer and the logbook’s view, and a few short-lived values the app needs while you sign in.If the operator has switched analytics on, visits are counted with Umami, a self-hosted analytics tool that sets no cookie. It is told the kind of page (such as /trips/:tripId, never the trip itself) and named actions such as importing a track — no names, email addresses or contents of your log. Like any website it also sees your IP address, your browser and the site that sent you.When you first arrive, the host name of the site that sent you and any campaign tags on the link (utm_…) — or, for a share or invitation link, just which kind it was — are kept in your browser’s local storage for 7 days. If analytics is on, they are sent to Umami with each sign-in and with your first trip and track, so those can be counted towards that link.Who else sees it

Crew: a person in your address book who accepts your invitation sees the voyages they crew on — the trip, its legs with their notes, tracks and the crew list with names, roles and crew notes — but not the charter details. The rest of your address book’s personal details stay with you.

Share links: a trip’s public link shows anyone who has it a read-only view — its name, description, dates, ship, legs and map — without the charter details, your notes or crew names (crew appear as initials). It exists only once you create it, and switching it off ends it at once.

Maps: your browser loads chart tiles straight from OpenStreetMap and, if you switch sea marks on, OpenSeaMap. Like any website, they see your IP address and which area you are looking at.

Weather: when you, or an agent acting for you, fetch a leg’s wind, the server asks Open-Meteo with a position rounded to about 1 km and the dates — no track, no name, nothing that identifies you. Nothing else on the server contacts a third party.

Email: Seamark sends you sign-in links. When you invite crew, it mails the address you enter an invitation with your name and the name, dates, ship and role of each trip it opens. When you announce a trip, it mails the linked crew, who can turn announcements off in Settings → Notifications.

AI agents (MCP)You can connect an AI assistant such as Claude or ChatGPT. It gets access only after you allow it on Seamark’s consent screen, and then acts as you: it can read and change your whole log, your address book’s personal details included, send invitations and announcements as you, and turn on a trip’s public link. It cannot download the data export, create API tokens or reach administration. An API token you create in Settings and give to an app acts as you without that screen, and can also download the export.What the assistant reads from Seamark, and what you write in the chat, is processed by the assistant’s maker — Anthropic for Claude, OpenAI for ChatGPT — under their own terms and privacy policy.Disconnect an assistant in Settings → API tokens with Revoke, or cut every token, agent and other signed-in device at once with Revoke everything. A connection also ends after 90 days unless you connect again.Getting it out, and deleting itSettings → Data export downloads your whole log as one ZIP archive: your profile, ships, address book, trips and every GPX file.You can edit or delete your trips, legs, tracks, ships and people yourself at any time.To delete your account, write to the operator. Your account and everything it holds are then deleted for good; copies in earlier backups go as those backups expire.When this policy changes, so does the date at the top.User manual