Privacy notice

Roles

For information a vessel operator or captain collects about their passengers and crew (for example briefing acknowledgements, crew duties and contact details), the vessel operator generally decides the purposes and is likely the controller, with the platform acting on their behalf. For captain and crew accounts, the platform provider decides how accounts work. The final allocation depends on the contracts in place and is still being confirmed.

What we process

Accounts: email address, password (stored hashed by the authentication service) or Google sign-in identity, display name and chosen role, preferred language.

Vessel profiles: content the captain enters, such as vessel name, captain display name, contact details, Wi-Fi details, safety rules, deck plans and uploaded files.

Crew: invitations (invitee email and a hashed, single-use token), membership status, position, reporting lines, assigned duties, contacts, acknowledgements, watch confirmations, issue reports and an audit log of changes.

Passengers: the name you enter when opening a vessel guide, your language, a device token that keeps your session, and the time and content version of briefings you acknowledge and messages you confirm.

Notifications: if push notifications are enabled on a device, the browser's push endpoint address and encryption keys for that device.

Why and on what legal basis

To provide the service you requested (accounts, vessel guides, crew hub): performance of a contract or steps before one.

To record safety briefing acknowledgements and message receipts for the vessel: the operator's legitimate interest in running safe operations, and any legal obligation that applies to the operator.

To keep the service secure and prevent misuse: legitimate interests.

We do not use your data for advertising or profiling. We do not ask for consent as a condition of using safety information.

Who receives data

Our backend and hosting provider, which stores the database and files.

An AI translation service, which receives vessel content text (not passenger acknowledgements) when a captain requests translations.

Google, only if you choose to sign in with Google.

Browser push services (such as Google, Apple, Mozilla or Microsoft), which receive an encrypted message and the device endpoint when a notification is sent.

The captain and authorised crew of the vessel you interact with.

Storage location and retention

The storage region, any transfers outside the European Economic Area and their safeguards, and the retention periods for each category are still being confirmed and will be stated here before launch. The app does not currently delete data automatically.

Your rights

You can ask for access to your data, correction, erasure, restriction, portability, and object to processing based on legitimate interests. You can also complain to your data protection supervisory authority, for example the Hellenic Data Protection Authority in Greece.

Requests are currently handled manually. A privacy contact address will be published here before launch.

Legal information

Operator

[Pending]

Address

[Pending]

Registration

[Pending]

Privacy contact

[Pending]