Privacy & Data

VesselView

Last updated 28 September 2026

VesselView asks for as little as it can. Most of it needs no account at all, and the parts that do need only enough to tell one authorised person from another.

Your email, your password, your account

Your email address is used only for account verification and access control. Never sold, and never shared for anyone else's marketing. You may request account deletion and full data removal at any time. Email [email protected] from your registered address. This app never sees or stores your password. Authentication is handled by Supabase, which keeps only a cryptographic hash of it, never the password itself.

What is collected

For a signed-in account: your email address and, if you supply one, your name, so the service can tell one authorised person from another. It also keeps what you set up in the app: the routes and vessels you save, your display and alert settings, the crossing you are currently on, and, for staff, the notes you add and the exports you make, with your address as their author. There is no tracking profile, no advertising identifier and no browsing history.

Browsing without an account

The public pages need no account and set no analytics or advertising cookies. Choices you make on the Settings page (appearance, text size, whether location may be used) are kept in your own browser and are never sent anywhere.

Location

Your location is requested only at the moment you tap a control that needs it, such as working out the drive to a pier or finding your nearest port. It is used to answer that question and is not stored or transmitted. It is never tracked in the background.

Notifications

Turning on alerts stores a push endpoint supplied by your browser, the crossing you asked about and which kinds of alert you chose. That record belongs to a browser rather than to a person and no account is needed for it. Turning alerts off deletes it.

The assistant

The assistant is for signed-in accounts only. What you type is sent, with a summary of current ferry and fleet status, to Anthropic, whose AI model writes the reply. The conversation is not saved by this app, so do not type anything into it you would not want sent to that service.

How it is used

Solely to provide the service. Your data is never sold, never shared for marketing, and never passed to a third party for their own purposes.

Where it is held

In a Supabase database hosted in London, UK, with row-level security enabled on every table. Operational data is readable only by approved signed-in accounts; the public pages are served through a separate boundary that carries published information only.

Services that handle your data

Only to run the app, and never for their own purposes: Supabase (database and sign-in, London); Vercel (hosting, which sees your IP address in its request logs; its servers may be in the US); Resend (sends sign-up, password and approval emails, so it sees your email address; US); Anthropic (the assistant, as described above; US); and your browser's own push service, such as Google's or Apple's, which delivers alerts you turn on. Where a service is outside the UK, it is used under the data-protection terms that provider offers for transfers from the UK.

Who is responsible

VesselView is run by one person, named on the About page, who is responsible for your data (the data controller under UK data protection law). Contact: [email protected].

Your rights

You may ask for a copy of your data, ask for it to be corrected, or ask for your account and everything attached to it to be deleted. Email [email protected] and it will be done. If you are unhappy with how your data has been handled, you can complain to the Information Commissioner's Office (ico.org.uk).

Ferry information

Timetables, route listings and service notices are taken from publicly available sources and remain the property of their publishers. Operational data in the signed-in area is accessed under the legitimate working access of the organisations named in the Terms of Use.

Contact

Questions about any of this: [email protected].

Terms of Use·Back to the map