This notice describes personal data handled when you use My Cadetship Tracker, a personal training organiser operated by James Oliver Phillips trading as TheShipYard Studios. It explains how we handle personal information in the free public-beta release.
1. Who is responsible
The controller of the personal data described in this notice is James Oliver Phillips, sole trader trading as TheShipYard Studios. You can write to [email protected].
Geographical business establishment: Unit 4, Little Castle Business Park, Raglan, Usk, NP15 2BX, United Kingdom. Postal correspondence: James Phillips / TheShipYard Studios, Unit 176345, PO Box 7169, Poole, BH15 9EL, United Kingdom.
2. Personal data we handle
When you create an account, we process your email address, account ID, training discipline, email-verification and sign-in information, the version/date of the legal notices acknowledged on registration, and your declaration that you are at least 17 (we do not ask for your date of birth). Authentication and password security are managed through Supabase Auth; we do not receive your plaintext password.
If you choose optional cloud backup, we process the workspace you upload, which may include vessel names, voyage and placement dates, watchkeeping days/hours, tasks, progress, notes and any additional information you enter. Please avoid adding special-category or other highly sensitive personal data, or personal information about others, unless necessary.
If you email support, we process the email address and the information in your message. When the site or account services are used, our hosting and security providers can receive IP addresses, browser/device information, request timestamps, and technical or security logs needed to deliver and protect the Service.
If you actively select the ship lookup tool, the app sends the vessel name or IMO number you entered to public Wikimedia/Wikidata services to look for ship details. This is a direct request from your browser; do not use the lookup tool if you do not want that search information shared with Wikimedia.
The public-beta app does not collect card numbers or sell subscriptions. If a future paid checkout is introduced, a separate provider such as Stripe may process billing and payment information under an updated notice. Historic test or billing administration records, where present, may be retained as necessary for compliance.
3. Local storage and optional cloud backup
Cadetship workspace records are stored locally in your browser/device by default. Signing up or signing in does not automatically upload them. You choose whether to create or restore a remote cloud backup and whether to enable automatic uploads after linking your device.
A JSON export is a file you choose to download; it is not automatically sent to us. Data left on a shared device or in a downloaded file may be visible to someone else with access to that device.
Cloud backups are linked to your authenticated account and protected by access controls, including row-level database security. They are not end-to-end encrypted; authorised hosting systems may process them to operate the Service. Keep an independent export before a restore or import.
4. Purposes and lawful bases
To register and authenticate you, provide optional cloud backup and restoration, and operate your requested account features, we process account and workspace data because it is necessary to provide the Service under our contract with you or to take steps you request before it.
We rely on legitimate interests to keep the service secure, diagnose faults, prevent abuse and answer ordinary support enquiries; those interests are balanced against your privacy rights. Where your support request is about performing our contract or a legal obligation, that may instead be the relevant lawful basis. An optional Wikidata request is made only when you choose to use the vessel lookup feature.
Where an accounting or legal record must be kept, we rely on the applicable legal obligation. We do not use acceptance of Terms as consent to marketing and do not currently run targeted advertising or automated decision-making with similarly significant effects.
5. Service providers and disclosures
Our service providers include Supabase (account authentication and optional cloud workspace storage), Cloudflare (website and server functions), Resend (delivery of account-verification and related transactional email), and Google/Gmail (support correspondence). Where you request a vessel lookup, Wikimedia/Wikidata receives the query directly from your browser and handles it under its own privacy terms. Providers may use their own subprocessors.
We may disclose information when required by law, to protect legal rights, to investigate misuse or to authorised service providers with appropriate arrangements. We do not sell your cadetship records or provide them to advertisers.
6. International processing and transfers
Our configured primary Supabase database is in the London region, but the wider Service uses providers that may access or process some information outside the United Kingdom. A UK regional database does not mean that every supporting service or log remains in the UK.
Where personal information is transferred outside the UK in a way covered by UK international-transfer rules, the responsible provider or controller must rely on an applicable adequacy regulation or appropriate transfer safeguards (such as an approved contractual mechanism). Please contact us to request the relevant arrangements. For information about the applicable service providers and transfer arrangements, please contact our support address.
7. How long information is kept
Local workspace records remain on your device until you remove them or your browser/device clears them; we do not control copies that you export into separate files.
Optional cloud workspaces remain available while the account exists and the backup has not been deleted, subject to service changes and lawful retention requirements. Using the app's cloud-deletion and account-deletion controls removes the current online workspace, although provider disaster-recovery backups and technical logs may follow separate retention cycles.
We retain support correspondence only for as long as necessary to answer the enquiry, handle related follow-up or disputes, or comply with legal obligations. Hosting, authentication and security logs follow applicable provider retention arrangements and our documented security needs. We periodically review whether continued retention is necessary; you can request the specific criteria applying to your data.
If historic subscription or accounting records exist, we retain only what is necessary to meet tax, accounting, refund or dispute obligations for the relevant legally required period. You can ask support for the retention criteria relevant to a particular record.
8. Your rights and choices
Depending on the circumstances, you may request access, correction, deletion, restriction, portability, or object to certain processing of your personal data. Where processing is based on legitimate interests, you can object to that use; we will assess the objection as required by law.
You can export JSON records, delete an optional cloud backup and request account closure using the account tools or by emailing support. Removing an online account does not remove local records on each device, which you must clear separately. Historic billing records or other information may sometimes need to be retained for legal purposes.
We normally respond to UK GDPR rights requests within one month, subject to any permitted extension or exception. We may reasonably need to verify your identity before fulfilling a request. If we cannot meet a request, we will explain the reason and your complaint options.
9. Security
The Service uses HTTPS, Supabase account authentication, database access controls and server-side restricted keys. No internet or device-based storage can be guaranteed completely secure. Protect your password and devices, and maintain your own JSON exports for important records.
The Service does not produce or replace an official maritime training record.
10. Cookies and device technologies
The app uses necessary browser/device storage and cached files for offline operation, account sessions and selected backup preferences. These technologies are used to provide features you request, not for advertising.
At the date of this notice we have not intentionally integrated non-essential analytics, advertising or marketing trackers. If this changes, we will assess the applicable cookie-consent obligations before enabling them and update this notice.
11. Younger users
My Cadetship Tracker is intended for maritime cadets aged 17 and over. Cadets under 18 should obtain help from a parent, guardian or training provider if they need help understanding account privacy or uploading information about others.
The app uses high-privacy defaults: local records unless users opt into cloud backup, no user-to-user sharing, and no profiling or behavioural advertising. Because some maritime cadets are under 18, we recognise the ICO Children’s Code may apply, and its practical assessment is part of our operational compliance. Younger users should avoid entering personal details about other people or sensitive information without an appropriate reason.
12. Contact, complaints and updates
For privacy enquiries, rights requests and account closure, write to [email protected]. If you are unhappy with our response, you can complain to the UK Information Commissioner's Office via ico.org.uk.
This is Privacy Notice version 1.1-beta, effective 18 November 2026. We will update the version and date when we make material changes and provide further notice where required.