Last updated: 28 September 2026
The YEA App ("the app") is operated by:
"YACHTING EUROPE" LTD (also written "Yachting Europe OOD")
UIC/EIK: 208548876
Registered address: 7 Han Asparuh St., floor 2, office 4, Triaditsa District, Sofia 1463, Stolichna Municipality, Bulgaria
Email: [email protected]
Website: https://yachtingeurope.eu
In this policy, "we", "us" and "our" mean Yachting Europe OOD. We are the data controller for the personal data described in this policy, except where this policy says otherwise (see Section 12 on yacht workspaces and guest data, where the vessel is the controller and we act as a processor).
We have not appointed a Data Protection Officer, because our size and processing activities do not require one under Article 37 GDPR. All privacy questions and requests should be sent to [email protected].
This policy is written to comply with the EU General Data Protection Regulation (GDPR) and, for users in the United Kingdom, the UK GDPR and Data Protection Act 2018. Where this policy refers to the GDPR, the equivalent provisions of the UK GDPR apply to UK users.
We collect the data you put into the app. The app is a career and compliance tool for yacht crew, so much of this data is professional in nature, but some of it is sensitive. You control what you add; most fields are optional.
Certificates and qualifications (name, category, issuing authority, certificate number, issue and expiry dates, uploaded files and notes), sea service entries and vessel details, work experience, education, languages, interior/deck career progression records, cover letters, and watchkeeping logs.
Some documents you can store in the app are health data:
We only process this data with your explicit consent (Article 9(2)(a) GDPR). Before you first save a medical or vaccination document, the app asks for a separate, explicit consent per category; nothing is stored without it. You can withdraw consent at any time by deleting the documents concerned. We keep a record of the consent itself (category, timestamp) as evidence that consent was given; this record is deleted with your account.
Health documents receive stricter treatment throughout the app:
When you request a captain's reference, we process the referee's name, email address and role (which you provide), the vessel and period concerned, and your note to them. When the referee responds via the secure emailed link, we store their structured ratings, narrative comments and any corrections they make. Reference links are secured by a secret token (we store only a cryptographic hash) and expire after 14 days.
If you are a referee: we process your name, email and role because the crew member asked us to contact you for a reference; the legal basis is our legitimate interest in facilitating the reference the crew member requested. Your submitted reference is stored with the crew member's records. You may request deletion of your reference details at any time via [email protected].
Earnings entries, receipt photos and expense records, charter records, tax residency day-counting entries, visa and Schengen entries, rest hours records, and rest hours sign-off signatures (drawn signatures with signer name snapshots). The app never collects card or bank details.
Conversations with the AI features (CV interview, career planning, interview preparation, cover letters, and similar) are stored in your account so you can continue them. See Section 7 for what is shared with our AI provider. We also record AI usage metering (feature used, model, token counts) to operate fair-use allowances; metering records contain no conversation content.
Analytics are off by default and only run if you opt in, either at onboarding or later in Settings. If you opt in, we record a small set of first-party product events (app opened, screen viewed, onboarding started/completed, CV export completed) with the screen name and a timestamp, linked to your user ID when you are signed in. Screen identifiers are scrubbed so that record IDs never leave the device. Our analytics records no IP address, no advertising identifier and no device tracking identifier, and we use no third-party analytics service. The only device-linked identifier we hold at all is the push notification token described in Section 3.10: it is a delivery address for notifications you switched on, it is never used for analytics, advertising or tracking, and it is the reason our App Store privacy label reports a "Device ID" as collected and linked to you. We do not track you across other companies' apps or websites. Events generated before you have made a choice are discarded, not queued. You can opt out at any time in Settings, which also discards any unsent events. Analytics data is deleted with your account and is automatically pruned after 24 months in any case.
If you report content, we store your report (content type, reason, optional note) together with a server-captured excerpt of the reported content so that evidence survives later edits. If you block a yacht or an officer who approached you, we store your block list. See the Terms of Service for how moderation works.
Your membership status, plan, billing period and renewal state, and the identifiers that link your account to the service that bills you.
We use subscription data to give you access to the membership, to prevent you from being charged twice through two different channels, and to keep the accounting records the law requires.
If you enable notifications, the app stores an Expo push token, which is a routing address for delivering notifications to your device. It is not used for advertising or tracking. You can control notification categories (certificate expiry, document expiry, vaccinations, visas, Schengen, tax residency) in Settings, and these preferences are honoured server-side. The app does not access your GPS location, contacts or calendar.
| Processing | Legal basis |
|---|---|
| Providing the app: your account, CV, certificates, sea service, compliance trackers, yacht workspace membership, subscriptions | Performance of a contract (Art. 6(1)(b)) |
| Health documents (ENG1, ML5, vaccinations) and ENG1 sharing | Explicit consent (Art. 9(2)(a) with Art. 6(1)(a)) |
| Sending your data to our AI provider when you use an AI feature | Consent (Art. 6(1)(a)), collected once via the in-app AI disclosure before first use |
| Publishing your public CV link; appearing in Open to Work crew search | Consent (Art. 6(1)(a)); both are off by default and switched on only by you |
| Product analytics | Consent (Art. 6(1)(a)), opt-in |
| Contacting referees you nominate; transactional email (reference links, certificate expiry reminders) | Legitimate interests (Art. 6(1)(f)): providing the service you asked for |
| Content moderation, abuse prevention, rate limiting, security logging | Legitimate interests (Art. 6(1)(f)): keeping the service safe and lawful |
| Retaining billing event records after account deletion | Legal obligation (Art. 6(1)(c)): Bulgarian accounting and tax law |
| Recording your acceptance of the Terms and your consents | Legal obligation (Art. 6(1)(c), Art. 7(1) GDPR: demonstrating consent) |
Subscription data from Plug&Pay and from Apple is processed to perform our contract with you (Article 6(1)(b) GDPR) and to meet our accounting and tax obligations (Article 6(1)(c) GDPR).
Where we rely on consent, you can withdraw it at any time (Section 9); withdrawal does not affect the lawfulness of processing before withdrawal.
Nothing in your account is visible to anyone else by default. Every sharing surface below is opt-in and reversible.
You can enable a public CV page at an unguessable link (yachtingeurope.eu/cv/...), for example behind a QR code on a paper CV. It is off by default. When enabled, the page shows your professional CV: name, photo, rank, department, personal statement, location, nationality, languages, sea service (including vessel names and particulars), work experience, education, qualifications, and your non-health certificates. It shows your birth year, never your date of birth, and it never shows your email, phone or WhatsApp number, date of birth, seaman's book number, passport details, or any medical or vaccination document. Anyone with the link can view the page, so share it deliberately. Disabling the toggle invalidates the link immediately. A view counter records how often the page was opened.
If you switch on Open to Work, captains and managers of vessels with an active subscription can find you in crew search. Results show an allowlisted card only: name, photo, desired positions, department, availability, coarse location, nationality, languages, non-health certificate codes, visa type, and a sea service summary. Your contact details are never shown in search. A vessel can send you an approach message; only if you accept it are contact details unlocked. Switching Open to Work off removes you from all future searches instantly. You can additionally hide vessel names in your sea service from viewing captains with the "share vessel names" setting.
The referee you nominate receives your name and email, the vessel and period, your claimed role, and your note, so they know who is asking. They do not see your CV, certificates or any other data.
If you join a vessel's workspace, its current active members can see your name and photo in the crew list. Officers (captain/manager) can additionally see a certificate roster with your certificate names and expiry dates, excluding all health certificates. Rest hours peer visibility is off by default and, where a captain enables it, shows only a coarse weekly compliance status, never your underlying hours. Leaving the vessel removes this visibility immediately.
We use a small number of service providers (processors) to run the app. We do not sell personal data, and no third party receives your data for its own advertising or marketing purposes.
| Provider | What it does | What it processes |
|---|---|---|
| Supabase | Database, authentication, file storage and server functions. Hosted in the EU (AWS eu-west-1, Ireland). | All app data described in Section 3 |
| Anthropic | AI model provider powering the AI features | Only the data you submit to an AI feature (see Section 7); nothing is sent without your prior consent |
Railway (yea-app-backend) | Hosts our backend service that relays AI requests and payment webhooks | AI request content in transit; subscription events |
Railway (hopeful-magic-production-0530) | Hosts our document rendering service, which generates the PDFs the app produces: vaccination booklet, earnings log and year-end summary, reference report, rest hours report, sea service records and testimonials, CV, and seasonal report. Hosted in the EU (EU West, Amsterdam, Netherlands). | The contents of the document being generated, in transit and for the duration of the request only. Depending on the document, this can include your passport number and date of birth, your vaccination records, your earnings and financial records, your CV and career records, and reference data. The document is rendered in memory and returned to your device; this service stores no copy. |
| Plug&Pay B.V. (Netherlands) | Plug&Pay B.V. (Netherlands) — our payment processor, used to handle checkout and subscription billing. Plug&Pay's exact server hosting region has not yet been confirmed; we have requested their Data Processing Agreement (DPA) to obtain this detail and will update this policy once received. | Your name, email and payment details at checkout; we receive billing events, never your card number |
| Apple Distribution International Ltd. (Ireland) and Apple Inc. (App Store) | Sells and bills memberships bought in the iOS app. Apple acts as an independent controller for your App Store purchase under its own privacy policy (apple.com/legal/privacy), not as our processor. | Apple handles your payment and Apple Account. We receive the purchase record and renewal notifications described in section 3.9. |
| Expo (EAS) | App builds, over-the-air updates, and push notification delivery | Push token and notification content in transit |
| Resend | Transactional email (reference links, certificate expiry reminders, report notifications) | Recipient email address and message content |
| Sentry | Crash and error reporting in production builds | Technical error details and stack traces only; we deliberately send no user ID, device ID or account data with error reports |
| WordPress (our own website) | Serves the public CV pages and the captain reference form | The public CV data (Section 5.1) and reference form submissions |
| Brevo (Sendinblue SAS, France) | Sends you membership and account emails, and, if you opted in via the marketing checkbox at registration, marketing email. Keeps our contact list. | Your email address, name, membership status, plan, billing source, and the relevant subscription and trial dates |
Some of these providers (Anthropic, Sentry, Expo, Resend, Railway) are US companies or may process data outside the EU/UK. Plug&Pay B.V. is a Netherlands-registered company; their server hosting region has not yet been confirmed and will be added here once their DPA is received. Where personal data is transferred outside the European Economic Area or the UK, we rely on the European Commission's Standard Contractual Clauses, the EU-US Data Privacy Framework where the provider is certified, and the UK Addendum or International Data Transfer Agreement for UK data, as applicable. Our primary data store is in the EU.
Several features are powered by AI models from Anthropic: the Jamie chats (CV interview, career planning, interview preparation), cover letter drafting, sea service and work experience reframing, receipt scanning, seasonal report narratives, charter preparation and provisioning lists, and certificate text extraction.
Before you use any AI feature for the first time, the app shows a disclosure naming Anthropic and describing what will be sent, and asks for your permission. Nothing is sent to Anthropic until you agree, and your agreement is recorded with a timestamp and the version of the disclosure you saw. If the disclosure changes materially, you will be asked again.
What is sent depends on the feature: for example, the CV interview sends your CV, sea service, certificates and career details; the receipt scanner sends the receipt photo you take; the charter generators send the charter details you enter. Your health documents are not sent to Anthropic unless you yourself submit such a document or its contents to an AI feature. AI conversations are stored in your account until you delete them or your account. AI output can be wrong; always check anything important before relying on it.
Under the GDPR and UK GDPR you have the right to:
We respond to requests within one month. We may need to verify your identity before acting on a request. Exercising your rights is free of charge.
Settings contains a one-tap data export. It assembles, on your device, a ZIP archive containing every category of your data as machine-readable JSON files plus your uploaded files (avatar, certificates, receipts, documents), with a manifest and a README. The export covers your profile, career records, health data consents, references, financial and compliance records, AI conversations, moderation records, subscription history and analytics events. It is built entirely on your device and shared through the standard system share sheet; no copy is retained on our servers. For records involving two parties (for example a vessel's approach to you), the export contains the rows that are about you. Content that belongs to a vessel's workspace (boards, ship's log, vessel documents) is not part of your personal export because it is the vessel's data, not yours.
You can delete your account in Settings at any time. Deletion:
What survives deletion: redacted billing event records (Section 8), redacted content report records where your content was reported (Section 8), and content you contributed to a vessel's workspace (tasks, log entries, handovers and similar), which belongs to the vessel and remains with your name detached.
Before your data is erased, we ask our payment provider to cancel the subscription attached to your account, so you are not billed again. This has to happen first, because the record linking you to the payment provider is erased along with everything else. If that cancellation cannot be completed at the time (for example the payment provider is unreachable), the erasure still goes ahead and the failed attempt is recorded so we can complete the cancellation by hand; it is never a reason to delay or refuse your erasure request.
Deleting your account does not cancel a membership you bought through the App Store. Only you can cancel it, in your Apple Account settings under Subscriptions. The app reminds you of this before you delete your account.
Vessels can run a paid workspace in the app (task boards, ship's log, drills, documents, handovers and similar). For crew members' own personal data, we remain the controller as described in this policy. For guest information that vessel crew enter into the workspace (guest preferences such as cabin setup, food and drink likes and dislikes, routines), the vessel is the data controller and we act as its processor, storing and displaying that data on the vessel's instructions. Vessels are responsible for informing their guests. By design, durable guest profiles cannot contain health information: allergy and medical dietary information can only be recorded against a specific charter; see Section 12.1 for how long it is kept.
This subsection explains how the app treats information about a vessel's guests, who are not our users and do not hold accounts.
Crew record what the boat needs in order to look after its guests: cabin and service preferences, food and drink likes and dislikes, routines, and, where a guest tells the crew about them, allergies, intolerances and medical dietary requirements. Allergy and medical dietary information is health data, which is special category data under Article 9 GDPR.
How this information reaches us. Guests disclose it voluntarily and directly to the crew, for a purpose they state at the time: so that the galley and the interior can cater for them safely. A guest who tells the chief stew about a shellfish allergy is asking the boat to act on it. The crew member records it in the app to serve that same purpose. We never obtain guest information from any other source.
Legal basis. The explicit consent of the guest under Article 9(2)(a) GDPR for the health element, together with Article 6(1)(a) consent for the ordinary personal data in the same record, such as the guest's name and their relationship to the party. That consent is bound to the purpose it was given for.
Because the guest is not a user of the app and cannot record anything in it themselves, the app asks the crew member instead. Before allergy or medical dietary information can be saved for the first time, the app asks the crew member to confirm that the guest disclosed it to them for this purpose, explains that information the guest did not give them must never be entered, and records that confirmation with a timestamp. Nothing is stored if they decline. That record is our evidence under Article 7(1) that the guest's consent was obtained; it is not a substitute for the guest's own consent, and it does not affect any of the guest's rights below.
Who is the controller. For guest information recorded for a vessel's charter, the vessel is the data controller, acting through its captain and officers, and Yachting Europe OOD acts as its processor, storing and displaying the information on the vessel's instructions. This is the case whether crew record it in the vessel's workspace or in their own Charter Log inside the app. The vessel is responsible for having a lawful basis for the guest data its crew enter and for informing its guests; our role is to hold the data securely and to enforce the limits below.
How long it is kept. Guest allergy, dietary and preference information is erased automatically by a nightly process. It is not kept for as long as the charter record itself:
How a guest can correct or delete their information. A guest may ask at any time, and does not have to give a reason:
The app is not intended for anyone under 16 years of age, which reflects the minimum working age at sea under the Maritime Labour Convention. By creating an account you confirm you are at least 16. We do not knowingly collect data from children under 16; if you believe a child under 16 has created an account, contact [email protected] and we will delete it.
All data is transmitted encrypted (TLS) and stored with per-user access controls enforced at the database level, so that each user can only reach their own rows and files. Session credentials are stored in your device's secure keychain. File storage is private by default; time-limited signed links are used where a file must be displayed. Join codes and reference tokens are stored only as cryptographic hashes. Access to sensitive surfaces (ENG1 viewing, crew search) is additionally rate-limited and audited.
We may update this policy as the app evolves. We will post the updated version with a new "Last updated" date, and for material changes we will notify you in the app or by email before they take effect.
"YACHTING EUROPE" LTD (Yachting Europe OOD)
7 Han Asparuh St., floor 2, office 4, Triaditsa District, Sofia 1463, Bulgaria
UIC/EIK: 208548876
Email: [email protected]
This policy applies to the YEA App and the parts of yachtingeurope.eu that serve it. See also our Terms of Service. Questions about your data go to [email protected].