Privacy notice

The platform is operated for the client organisation carrying out the review — the reviewing party. The data controller is The World of Superyachts Ltd. A registered address and a named data protection contact are provided as part of client onboarding.

For each provisioned account the platform stores:

• full name, as supplied when the account is created;
• email address, which is also the sign-in identifier;
• company name, where one is recorded;
• role — marine superintendent, administrator, or vessel operator;
• for vessel operators, the list of vessel names the account is permitted to see (its scope);
• an authentication record held by the platform's authentication service: a hashed password, timestamps for account creation, email confirmation and last sign-in.

Passwords are never stored or visible in readable form, and are not accessible to the application.

The platform records what each named person did during a review. Every one of these records carries the acting user and a timestamp:

• review decisions — accepting, overriding or deferring a finding — together with the comment the reviewer wrote;
• confirmations that a value was checked against its source document;
• clarification questions raised, and the answers given to them;
• changes to the status of a case, with the previous status and any comment;
• documents uploaded, with the original filename and the time of receipt.

The "request a demonstration" form on the public landing page collects the name, work email address, company or organisation, and — where given — the role or title, phone number and message of the person enquiring. It is stored, together with the time of submission and basic technical details of the request used to identify automated submissions, and is used only to respond to the enquiry. It is not linked to any review case and is not visible to platform users.

Review decisions, clarifications, confirmations and case status changes are append-only. They cannot be edited or deleted through the application by any role, including administrators — the database grants no update or delete permission on those records. A correction is made by recording a further action, so the earlier one remains legible. This is deliberate: the value of the record is that it shows what was known and decided at the time.

Review decisions form part of an immutable audit record and are retained as such. Retention periods, and the handling of an erasure request against personal data within that record, are agreed with each client as part of onboarding.

• Every user can read their own profile.
• Marine superintendents and administrators can read all user profiles, so that decisions can be attributed to a named person in the audit trail.
• Vessel operators cannot read other users' profiles, and cannot see who raised a clarification or who recorded a decision.
• Vessel operators see only cases for the vessels in their own scope. They cannot see other operators' cases or documents.

These limits are enforced in the database, not only in the interface.

Application data, user records and uploaded documents are held in a managed PostgreSQL database and object store provided by Supabase, running on Amazon Web Services infrastructure in the US West (Oregon), us-west-2 region — this is the region of the database host this deployment connects to. Data is currently hosted in AWS/Supabase US West (Oregon). Where a client requires EU or UK data residency, or a data processing agreement and standard contractual clauses for cross-border transfer, these are put in place as part of onboarding.

Uploaded case documents are held in a private bucket. They are not publicly addressable and are served only through short-lived signed links generated for an authorised user.

There is no analytics, advertising or marketing tracking in this application. No Google Analytics, no tag manager, no advertising pixel, no session-recording tool, no cookie banner, because there is nothing to consent to beyond the sign-in session itself.

The only cross-service traffic from a signed-in browser is to the Supabase endpoint that serves the database, authentication and document storage.

The code also contains a hook that reports an unhandled interface error to the Lovable development platform, and it only sends anything where that platform has injected its reporter into the page — which is the case in the development preview. The published site at transberth.com does not include that reporter: its pages contain no injected reporting script, and the hook sends nothing there. The hook can be removed entirely on request.

The browser stores a sign-in session token so that a signed-in user is not asked for a password on every page. It is used for authentication only, is cleared on sign-out, and is not used to profile anyone.

Privacy requests can be directed to info@transberth.com. The applicable supervisory authority and formal response timescale are confirmed in the client service agreement.