Privacy policy
What we keep, why, and what you can ask for.
This policy explains which personal data MySeaBase handles when you use this website and the app, where it is kept, how long, and your rights.
Last updated: 11 October 2026
Who we are
MySeaBase runs the website myseabase.com and the MySeaBase app. To reach us, use the contact link on this page. A contact email address will be published here.
Two roles
For the records a boat keeps in the app, the boat (its owner or operator) decides what is entered and why: the boat is the controller, and MySeaBase processes that data for the boat, only to run the service.
For user accounts, trial requests, billing and this website, MySeaBase is the controller.
Your account
Your user name, role and boat; an email address if you or your admin add one; your password, stored only as a one-way hash that nobody can read back; the secret for two-step login and your recovery codes (stored hashed); and the devices you choose to remember, with a label taken from the browser (for example "Chrome · Android").
What a boat records
Whatever the boat's users enter: logbook and passages (including positions and GPS tracks), money (cash, expenses, receipts, supplier invoices and bank details), maintenance, defects, inventory, documents and safety reports.
Crew records, including pay, bank notes, emergency contacts and medical notes, which only the owner and admins see. Guest profiles, including allergies and diet, which can be health data; the guest pre-arrival form accepts medical details only when the guest ticks a consent box. Photos and documents users upload.
Trial requests
What you enter in the free trial form: boat name and type, your name, email, role, country, language and any referral code. With it we keep how you found us: the first page you opened on this site, the site that linked you here (as your browser reports it) and any campaign tags in that first link, so we can tell which pages bring boats. No cookie is used for this; the browser forgets it when the tab closes. To limit abuse we keep your IP address only as a salted one-way hash, never the address itself.
Billing
Each boat's billing email, contact name and country, its invoices and payments, and its referral code with what it earned. For partners and captains who refer boats: their name and email.
Technical data
The web server logs each request (IP address, time, the page or file asked for, browser details) to run and protect the service. The app server logs only the IP address, the method and the path: never what was sent, and never passwords or tokens. Each boat has an audit log of actions: who did what, and when.
For push notifications we keep the address your browser gives us for your device (an endpoint at Apple, Google, Mozilla or Microsoft) and its keys.
Where it is kept
On our own server in a Hetzner data centre in Helsinki, Finland, inside the EU. Every connection is encrypted and passes through Cloudflare, which protects and delivers the site and sees connection data such as IP addresses.
Push notifications travel through the push service of Apple, Google, Mozilla or Microsoft without any content: the app fetches the text itself. When email is switched on, notifications, monthly reports and trial links will be sent through an email provider; email is not switched on yet. Cloudflare, Apple, Google, Mozilla and Microsoft may handle connection data outside the EU.
Other services the app loads
This website serves its fonts from our own server and loads nothing from other sites. The app is not there yet: its pages (including the guest form and the guest balance page) load the typeface from Google Fonts, so Google sees the device's IP address when it sends the font.
The passage map loads its map library from cdnjs (run by Cloudflare) and its map tiles from OpenStreetMap and OpenSeaMap, which see the device's IP address and the map area shown. If a boat connects the public API or webhooks, its data goes to the addresses that boat chooses.
No tracking
No advertising, no analytics and no tracking scripts, on this website or in the app. We do not sell your data or share it for anyone's marketing.
We set no cookies of our own. This site remembers your language in your browser's storage; the app keeps your session, settings and offline copies on your device.
Why we use it
To provide the service a boat signed up for (contract); to keep the service secure, prevent abuse and fix faults (legitimate interest); and to keep invoices as tax law requires (legal obligation). A trial request is handled because you asked for it and ticked the consent box.
How long we keep it
A boat's records stay while its subscription runs. When a year or a trial ends without renewal, the boat becomes read-only (a paid plan after a grace period, normally 30 days; a trial on day 31): nothing is deleted, people can still sign in, read and export, and renewing opens it again.
When a boat asks us to delete its data, we take the boat out of the service at once and then remove its archived database and files from the server. Nightly backups are kept for 30 days and then deleted, so deleted data leaves the backups within 30 days.
Trial requests, server logs and audit logs are kept only as long as needed to run and protect the service. Invoices are kept as long as tax law requires.
Your rights
You can ask for access to your data, a copy to take elsewhere, correction or deletion, and you can object to how we use it.
Much of this is in the app: admins and owners export the accounts (Excel or CSV with receipts, on plans with the accountant export), print reports and download any photo or document; admins correct or remove records and users. On request we hand over a full copy of a boat's data as a machine-readable file.
For a boat's records the boat decides, so we pass your request to the boat or help it answer. To ask, use the contact link on this page. You can also complain to your data protection authority.
Security
Passwords stored only as one-way hashes, two-step login, each boat in its own database, encrypted connections and nightly backups. The details are on the security page.
Changes
When this policy changes we update this page and the date at the top.
Questions about your data? Talk to the maker. A contact email address will be published here.