Yachting Europe
Yachting
Europe
Taking Yachting To The Next Level
  • Yacht Services
    • Yacht Management
    • Refit & Projects
    • Crew Recruitment
    • Racing & Regattas
  • Brokerage
    • Buy a Yacht
    • Sell a Yacht
    • Charter a Yacht
    • Luxurious Lifestyle
  • Academy
    • New to Yachting
    • Experienced Crew
    • Courses & Programmes
    • The Crew Club
  • About
    • About Yachting Europe
    • Contact & FAQ
    • Vacancies
+44 751 110 2293
  • Yacht Services
    • Yacht Management
    • Refit & Projects
    • Crew Recruitment
    • Racing & Regattas
  • Brokerage
    • Buy a Yacht
    • Sell a Yacht
    • Charter a Yacht
    • Luxurious Lifestyle
  • Academy
    • New to Yachting
    • Experienced Crew
    • Courses & Programmes
    • The Crew Club
  • About
    • About Yachting Europe
    • Contact & FAQ
    • Vacancies
+44 751 110 2293
Yachting Europe

Privacy Policy

Yachting Europe OOD · YEA App

Contents
  1. 1. Who we are
  2. 2. Who this policy covers
  3. 3. What personal data we collect
  4. 4. Legal bases for processing
  5. 5. What is shared with others, and when
  6. 6. Processors and third parties
  7. 7. AI features and Anthropic
  8. 8. Data retention
  9. 9. Your rights
  10. 10. Self-service data export
  11. 11. Account deletion
  12. 12. Yacht workspaces and guest data
  13. 13. Children
  14. 14. Security
  15. 15. Changes to this policy
  16. 16. Contact

Last updated: 28 September 2026

1. Who we are

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.

2. Who this policy covers

  • Crew and captain users who create an account in the app.
  • Captains and referees who receive a reference request by email and complete the reference form on our website, without holding an account.
  • Visitors who open a public CV link shared by a crew member.
  • Guests of vessels, to a limited extent: see Section 12.

3. What personal data we collect

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.

3.1 Account and profile data

  • Name, email address, and password (held by our authentication provider in hashed form).
  • Optional profile details: phone and WhatsApp number, LinkedIn URL, profile photo, current location (a city and country you type in yourself; the app does not use your device's GPS location), date of birth, nationality and citizenships, passport countries held, seaman's book number, tax country, current rank and department, personal statement, hobbies.
  • Personal characteristics relevant to yacht recruitment, if you choose to enter them: swimming ability, driving licence, smoker status, and tattoo status/description.
  • Your account type (crew or captain/manager), which is a self-declared persona and grants no special access.
  • The date and version of the terms you accepted at registration, and your notification preferences.
  • A push notification token, if you enable notifications (see Section 3.10).

3.2 Career and CV data

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.

3.3 Health data (special category data under Article 9 GDPR)

Some documents you can store in the app are health data:

  • Seafarer medical certificates such as the ENG1 and ML5, stored as "medical" documents in the Document Wallet or as medical certificates in the Certificate Vault.
  • Vaccination records, including vaccine name, date administered, country, batch/lot number and administering clinic, stored as "vaccination" documents.

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:

  • They are never included in your public CV link (Section 5.1), in crew search results or search filters, in connection previews, or in the certificate roster visible to your vessel's officers. The mere existence of a seafarer medical is itself health data, so it is excluded from every public or shared surface by design.
  • The only way another person can ever see an ENG1 document is through a dedicated, consent-gated flow: a captain or manager of your current vessel can request access, and nothing is shared unless you explicitly approve that specific request. Each approval is tied to that requester, that document and that employment, every viewing is logged, and the viewing link expires after five minutes. You can decline or revoke without giving a reason.

3.4 Reference data

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].

3.5 Financial and compliance data

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.

3.6 AI conversation data

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.

3.7 Analytics data (opt-in only)

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.

3.8 Moderation data

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.

3.9 Subscription data

Your membership status, plan, billing period and renewal state, and the identifiers that link your account to the service that bills you.

  • If you subscribe on our website, our payment provider Plug&Pay handles checkout. We receive billing events (for example "payment received" or "subscription cancelled") and store them with your account. We never see or store your card number.
  • If you subscribe in the iOS app, Apple bills you through the App Store. When you buy or restore a membership, the app sends us the signed purchase record Apple gives it, and Apple sends our server notifications about renewals, cancellations, billing problems and refunds. From these we store: the product you bought, Apple's transaction identifiers, purchase and expiry dates, whether auto-renew is on, any refund or revocation date, and the App Store country, currency and price. To link a purchase to your account, the app gives Apple a random account identifier that we created for you; Apple returns it with the purchase record. Apple does not share your name, email address, Apple Account or payment details with us, and we do not receive them.

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.

3.10 Push notifications and device data

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.

4. Legal bases for processing

ProcessingLegal basis
Providing the app: your account, CV, certificates, sea service, compliance trackers, yacht workspace membership, subscriptionsPerformance of a contract (Art. 6(1)(b))
Health documents (ENG1, ML5, vaccinations) and ENG1 sharingExplicit consent (Art. 9(2)(a) with Art. 6(1)(a))
Sending your data to our AI provider when you use an AI featureConsent (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 searchConsent (Art. 6(1)(a)); both are off by default and switched on only by you
Product analyticsConsent (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 loggingLegitimate interests (Art. 6(1)(f)): keeping the service safe and lawful
Retaining billing event records after account deletionLegal obligation (Art. 6(1)(c)): Bulgarian accounting and tax law
Recording your acceptance of the Terms and your consentsLegal 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.

5. What is shared with others, and when

Nothing in your account is visible to anyone else by default. Every sharing surface below is opt-in and reversible.

5.1 Public CV link

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.

5.2 Open to Work and crew search

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.

5.3 References

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.

5.4 Yacht workspace visibility

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.

6. Processors and third parties

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.

ProviderWhat it doesWhat it processes
SupabaseDatabase, authentication, file storage and server functions. Hosted in the EU (AWS eu-west-1, Ireland).All app data described in Section 3
AnthropicAI model provider powering the AI featuresOnly 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 webhooksAI 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 deliveryPush token and notification content in transit
ResendTransactional email (reference links, certificate expiry reminders, report notifications)Recipient email address and message content
SentryCrash and error reporting in production buildsTechnical 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 formThe 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.

7. AI features and Anthropic

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.

8. Data retention

  • Your account data (profile, CV, certificates, documents, sea service, compliance records, AI conversations): kept until you delete the item or your account.
  • Analytics events and AI usage metering: automatically deleted after 24 months, and deleted immediately with your account.
  • Reference links: expire 14 days after sending. Completed references are kept with your records until account deletion.
  • Consent and terms acceptance records: kept for the life of the account as evidence of consent; deleted with the account.
  • Billing event records: retained after account deletion in redacted form (event type and dates only, with the payload scrubbed and the link to you removed) to satisfy Bulgarian accounting and tax retention obligations, which can require retention of accounting records for up to 10 years.
  • Apple purchase records are kept like billing event records: for the life of your account, and after account deletion in redacted form (dates and event type only, no link to you) for as long as Bulgarian accounting law requires.
  • Content reports: if a report was filed about your content, the report record survives your account deletion for moderation integrity, but your identity link is removed and the captured content excerpt is redacted.
  • Backups: Supabase, our database provider, maintains automatic daily backups of our database with a 7-day retention window. When you delete data or your account, the deleted data may still be present in these backups for up to 7 days before it is fully purged, after which no copy remains.

9. Your rights

Under the GDPR and UK GDPR you have the right to:

  • Access your data (Art. 15): use the in-app export (Section 10) or contact us.
  • Rectification (Art. 16): edit your data directly in the app, or ask us.
  • Erasure (Art. 17): delete individual items in the app at any time, or delete your entire account (Section 11).
  • Portability (Art. 20): the in-app export delivers your data in a structured, machine-readable format.
  • Restriction (Art. 18) and objection (Art. 21): contact us at [email protected].
  • Withdraw consent at any time: analytics via the Settings toggle; health documents by deleting them; public CV and Open to Work via their toggles; AI features by declining or ceasing to use them, or by contacting us to withdraw the recorded AI disclosure acknowledgment.
  • Complain to a supervisory authority: in Bulgaria, the Commission for Personal Data Protection (CPDP, www.cpdp.bg); in the UK, the Information Commissioner's Office (ICO, www.ico.org.uk); or the authority of the EU country where you live or work.

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.

10. Self-service data export

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.

11. Account deletion

You can delete your account in Settings at any time. Deletion:

  • permanently removes your profile, CV, certificates, documents (including all medical and vaccination documents), sea service, compliance records, AI conversations, analytics events and uploaded files;
  • removes your push token and clears app data stored on your device;
  • is immediate and cannot be undone.

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.

12. Yacht workspaces and guest data

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.

12.1 Charter guest data (allergies, dietary requirements and preferences)

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:

  • By default, 90 days after the charter ends. Where no end date has been recorded, the 90 days run from the last logged day of the charter, or failing that from its start date, so that an open-ended or forgotten charter cannot hold the information indefinitely. Standing dietary sheets in a vessel's workspace expire 90 days after the day they describe.
  • Up to 24 months where the guest has asked to be remembered. A guest, typically an owner or an owner's family sailing the same boat every season, may ask the crew not to make them repeat themselves at every embarkation. Where the guest has asked for this, the crew can switch on "remember this guest for future visits" against that guest's record. The 90-day rule then does not apply, and the information is erased 24 months after it was last confirmed as current. Sailing with the vessel again refreshes that date; a guest who stops sailing simply ages out. This is a longer period, never an indefinite one, and it is never switched on by default, by an import, or by inference. It is set only on the guest's own stated wish.
  • What survives. Only the guest-disclosed free text is erased: allergies, dietary notes, preferences and dietary flags. The guest's name and the rest of the charter record remain, because they are the crew member's own record of their work and are ordinary personal data rather than health data.
  • After erasure, the "remember" choice resets. Recording the information again requires the guest to be asked again.

How a guest can correct or delete their information. A guest may ask at any time, and does not have to give a reason:

  • Ask the crew. The quickest route is the captain, the chief stew or the crew member who took the details. They can correct or delete the information in the app immediately, and can switch "remember this guest for future visits" off, which returns the record to the 90-day rule at once.
  • Ask us. Write to [email protected]. Where the vessel is the controller, we will act on the vessel's instructions and will pass the request to the vessel without delay, and we will tell the guest that we have done so. Where we hold the information as processor and the vessel cannot be reached, we can still erase it.
  • Opting out of being remembered is a distinct request from deletion, and a guest can make either or both: switching the choice off returns the record to the 90-day retention rule, while deletion removes the information straight away.

13. Children

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.

14. Security

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.

15. Changes to this policy

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.

16. Contact

"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].

Yachting Europe Yachting
Europe
Taking Yachting To The Next Level

Boutique yachting services for owners, captains and crew across Europe.

Academy
Yacht Services
  • Yacht Management
  • Refit & Projects
  • Crew Recruitment
  • Racing & Regattas
Brokerage
  • Buy a Yacht
  • Sell a Yacht
  • Charter a Yacht
  • Luxurious Lifestyle
Academy
  • New to Yachting
  • Experienced Crew
  • Courses & Programmes
  • The Crew Club
Contact
  • +44 751 110 2293
  • Book a Consultation
  • About Yachting Europe
  • FAQ & Support
© Yachting Europe 2026. All rights reserved.
PrivacyTermsCookies