Your Booking is the commercial reference
The terms recorded on your Booking are what matter — not later edits to public content.
Booking policy
How cancellation, Booking changes and refund review fit together across Malaka.
This prototype defines the structure and user experience of Malaka’s Cancellation Policy. Final cancellation windows, refund entitlements, fees, timing, provider obligations and jurisdiction-specific consumer rights must be supplied and legally and commercially approved before publication.
Policy at a glance
The terms recorded on your Booking are what matter — not later edits to public content.
A cancelled Booking does not by itself determine whether, or how much, is refunded.
Date, Boat, skipper or other material changes may require review against the recorded Booking.
Where a case cannot be resolved through the standard flow, it can be routed to Support.
These are product principles that describe how the interface works — not statements of refund entitlement.
Cancellation does not automatically mean refund.
A Booking can carry a cancellation state while any refund is determined separately, according to the applicable recorded terms and the final policy. This page explains the process — it does not calculate or promise entitlement.
This policy explains how Malaka presents cancellation, change and refund workflows across sailing holidays and Skipper-only Bookings. It describes where the applicable terms are recorded, how a request moves through the platform, and where to go next — so you always know what a cancellation means for your Booking before anything happens.
It is written to sit alongside Malaka’s Terms and the other policies listed at the end. The final legal scope, applicability and the relationship between this policy and your specific Booking will be confirmed in the approved text.
[Final legal scope and applicability wording to be provided.]Malaka supports several ways to book. This policy is structured to apply across all of them, while the exact commercial rules for each remain subject to the final approved terms.
Any Bookings, products or arrangements that fall outside the scope of this policy will be identified in the final text.
[Exclusions and out-of-scope arrangements to be provided.]A Booking preserves the commercial terms recorded for that transaction at the time it was made. Later edits to the Experience, the Departure, the price, an accepted Offer or public content must not silently rewrite the terms your Booking already recorded.
Your recorded Booking is the reference point for any cancellation or change review. If public content changes later, the historical snapshot recorded on your Booking is preserved rather than overwritten.
A Booking may reference the policy and terms applicable to it. How policy versions apply to existing Bookings — including which version governs a given Booking — will be defined in the approved text.
[How policy versions apply to existing Bookings to be legally defined.]When a customer requests to cancel, Malaka reviews the request against the Booking. The steps below describe the shape of that review. The specific cancellation windows, conditions and outcomes are not defined in this prototype.
Not every person associated with a Trip has the same commercial authority. In particular, not every Crew member can cancel a Whole Yacht Booking, and a Group Leader is not automatically the Booking Owner. These are distinct, contextual roles.
The account context that holds the commercial Booking. Cancellation and refund actions normally sit here.
A contextual coordinating role for a party. Not automatically equivalent to the Booking Owner.
A participant on the Trip. For a Berth or Cabin they may hold their own Booking; for a Whole Yacht, participation and commercial authority can differ.
For an Individual Berth or Cabin, a traveller may have their own Booking and party context. For a Whole Yacht, Crew participation and the commercial Booking may be held differently. The final authority rules will be confirmed.
[Final authority rules for cancellation to be provided.]A change is not always a cancellation. Changes can touch dates, skipper, Boat, departure point, booking mode, party or capacity, or the commercial terms — and not every change is equivalent. Some are minor; others may affect the recorded Booking and require review.
Whether a change is “material”, and what follows from it, is defined by the final policy — not here. Where a change may affect your Booking, the interface can flag it: “This change may affect the recorded Booking and requires review.”
Editing reusable Experience content — the public description skippers reuse across departures — must not silently alter already-booked terms. If the public description changes later, the historical Booking snapshot remains preserved.
A Departure may hold the exact dates, Boat, skipper, price, capacity and meeting logistics. If a Departure changes after you booked, the interface should show a comparison rather than overwrite your recorded Booking:
Sometimes the service cannot be provided as booked. This section sets out the structure for provider-side cancellations. It does not state the remedies, refunds or replacement rights that may apply — those are defined in the final policy.
If Malaka later supports an alternative Departure, a replacement skipper or rescheduling, those options are not promised here. Their availability and terms will be defined before publication.
Not every change to a Trip is a commercial change. Day-to-day operational adjustments are related to, but distinct from, the commercial Booking terms. The exact line between the two is set by the final policy.
The classification of any given change remains subject to the final policy.
Sailing is weather-dependent. Routes and day-to-day plans may need to adapt to weather, sea state, port availability and safety considerations. An itinerary is a plan, not a guaranteed sequence of stops, and specific islands or ports are not promised.
A skipper may need to adjust the operational plan where conditions require it. This policy does not undermine that safety judgment — and it does not, on its own, create cancellation rights or financial consequences from a weather adjustment. Those rules are defined separately.
[Weather-related cancellation and change rules to be legally and commercially defined.] [Legal implications of route flexibility to be provided.]Any refund follows a review process rather than an automatic calculation. The steps below show how a request is assessed. There is no calculator here and no promised outcome — entitlement is determined by the applicable recorded terms and the final policy.
A request is submitted from an authorized account context and recorded.
The terms recorded on the Booking are examined.
The policy version applicable to the Booking is applied.
The recorded payment history for the Booking is checked.
The result of the review is recorded against the Booking.
Where a refund applies, its status is tracked and visible to you.
Payment status and cancellation status are tracked separately. A Booking can be cancelled while its payment or refund status moves through its own states. The statuses below describe what the interface can display — not timings or amounts.
How refunds are issued, how long they take, and how fees, deposits and any future installments are treated all depend on the final commercial and payment-provider rules. Nothing here should be read as a promise on any of these points.
[Refund method and processing rules to be provided.] [Expected refund processing and settlement timing to be provided based on payment-provider and policy rules.] [Any applicable fee treatment — cancellation, platform, processing or skipper-related — to be provided.] [Deposit treatment to be provided for applicable Booking structures.] [Treatment of future installments after cancellation to be provided.]Cancelling a group Booking has operational consequences for the people on the Trip, but their commercial and personal situations are handled carefully and separately.
Cancellation of one Booking on a shared Departure must not automatically affect other, unrelated Bookings on the same Departure.
A Skipper-only Booking is created from an accepted Offer. The accepted Offer version stays associated with the Booking, and later edits to the Offer must not silently rewrite the accepted commercial record.
The Booking preserves the recorded skipper fee, dates, travel-cost assumptions, accommodation assumptions, inclusions, exclusions, conditions and the Offer version.
For a Skipper-only Booking, the skipper fee may be separate from travel, accommodation, onboard expenses and charter costs. These are not implied to be a single refundable total.
The treatment of a no-show, late arrival or missed embarkation is defined by the final policy. This prototype does not set any penalty. The exact meeting point and embarkation details belong to your Trip and Holiday Hub, not to this public page.
[Rules for no-show, late arrival or missed embarkation to be provided.]Situations such as flight cancellations, visa issues, personal illness or transport delays are not covered by any promise here. Malaka does not provide travel insurance. Any recommendation or insurance-related terms, and how traveller-side disruption is treated, will be provided in the final policy.
[Treatment of traveller-side disruption to be provided.] [Any travel-insurance recommendation or insurance-related terms to be provided.]Exceptional circumstances and force-majeure provisions are drafted by legal counsel and are not invented here.
[Exceptional circumstances / force majeure provisions to be drafted by legal counsel.]This policy neither waives nor invents statutory rights. Any mandatory consumer cancellation or withdrawal rights, and the legal classification of Malaka and its Bookings, will be confirmed in the approved text and are not asserted here.
[Applicable mandatory consumer cancellation / withdrawal rights to be provided according to relevant jurisdictions and service classification.] [Legal classification, including any package-travel status, to be confirmed.]The flow below is conceptual — it shows where a request begins and how it is tracked. Submitting a request is not the same as a completed cancellation, an approved refund or a sent refund.
Go to your holidays and select the relevant Holiday.
Open the Booking and payment context for that Holiday.
Start a cancellation or change request and review the recorded terms.
See the terms recorded on your Booking before you submit.
Submit the request for review.
Follow the request and any refund status from your account.
Submitting a request does not by itself mean the Booking is cancelled, a refund is approved, or a refund is sent. A request can move through several states before it is resolved:
These states are shown only where the final workflow supports them.
If a request needs help, it can be routed to Support. Support can explain and coordinate, but it is not the source of truth for payment and refund records — financial operations remain separate.
Where a cancellation relates to a serious safety concern, Support may route the matter to Trust & Safety. Restricted Trust & Safety details are not exposed on this public policy, and a Trust & Safety case does not automatically determine any refund.
The dispute and escalation process, and the legal rights attached to it, are defined in the final policy.
[Dispute / escalation process and legal rights to be provided.]This policy may be updated over time. How a given version applies to existing Bookings, and how any change is communicated, will be set out in the approved text. The current version, effective date and last-updated date are shown at the top of this page and in the metadata below.
Questions about a cancellation or change are best started from your Booking, where the recorded terms and current status are visible. Contact routes will be confirmed before publication.
Support and contact route:
[Support / contact route to be provided.]For legal matters relating to this policy:
[Legal contact to be provided.]Cancellation workflows may involve Booking, payment and account information. This is handled in line with the Privacy Policy, and personal data is not shown in the public examples on this page.
Where do I go next?
Start here to find the right place in Malaka for what happened. This guide points you to the next step — it is not a statement of refund entitlement.
Product navigation guide — not a statement of refund entitlement.
Illustrative scenarios
These are non-binding structural examples. They show how the pieces relate. They do not show percentages, amounts or entitlement.
A Whole Yacht Booking Owner submits a cancellation request from their Booking.
A traveller cancels their own Berth Booking on a Departure shared with others.
An accepted Offer created a Skipper-only Booking, and the customer requests cancellation.
A Departure’s Boat changes after a Booking was made.