Malaka

Booking policy

Cancellation Policy

How cancellation, Booking changes and refund review fit together across Malaka.

Effective date: To be provided Last updated: To be provided Version: To be provided

This is a product prototype, not final policy.

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

Four principles behind every cancellation

Your Booking is the commercial reference

The terms recorded on your Booking are what matter — not later edits to public content.

Cancellation and refund are separate

A cancelled Booking does not by itself determine whether, or how much, is refunded.

Changes need context

Date, Boat, skipper or other material changes may require review against the recorded Booking.

Support can review exceptions

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.

The core principle

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.

Section 1

About this Policy

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

Which Bookings it covers

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.

  • Hosted Experience Bookings — a place on a departure published by a verified skipper.
  • Whole Yacht — a Booking that reserves the full sellable inventory of a departure.
  • Individual Berth — a single place on a shared departure.
  • Cabin Booking — a cabin on a shared departure.
  • Skipper-only Bookings — a Booking created from an accepted Offer for a skipper on a yacht you already have access to.

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

Your recorded Booking terms

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.

Booking terms snapshot

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.

Your Booking snapshot
Illustrative example — not a live Booking
Ref MLK-000000
Booking referenceMLK-000000 (sample)
Booking modeWhole Yacht (sample)
Trip datesSample departure window
Experience / Offer sourceSample Experience reference
PriceSample amount
CurrencySample currency
Payment structureSample structure
InclusionsSample inclusions
ExclusionsSample exclusions
Cancellation policy referencePolicy version [to be provided]
Fields shown are synthetic placeholders to illustrate structure. No live Booking, payment or personal data is displayed.

Policy version reference

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

Customer cancellation

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.

  • Who can request — a cancellation request is made from an authorized account context.
  • Booking Owner authority — commercial cancellation actions are normally associated with the Booking Owner.
  • Request date — the date the request is submitted is recorded.
  • Booking state — the current state of the Booking is taken into account.
  • Applicable recorded terms — the terms recorded on the Booking are reviewed.
  • Refund review — any refund is determined separately (see Refund review).
  • Trip / Crew implications — the operational effect on the Trip and Crew is considered.
[Customer cancellation rules to be provided.]

Who can cancel — Booking Owner, Group Leader, Crew

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.

Booking Owner

The account context that holds the commercial Booking. Cancellation and refund actions normally sit here.

Group Leader

A contextual coordinating role for a party. Not automatically equivalent to the Booking Owner.

Crew member

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

Booking changes

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.

Material change

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

[Definition and consequences of material changes to be provided.]

Experience vs Departure changes

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:

Recorded Booking
BoatSample yacht A
SkipperSample skipper
DatesSample window
PriceSample amount
Current Departure
BoatSample yacht B
SkipperSample skipper
DatesSample window
PriceSample amount
Values are synthetic and illustrate a comparison only. A difference does not by itself determine any outcome — the recorded Booking is not overwritten automatically.
Section 6

Skipper / provider cancellation

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.

  • Skipper unavailable.
  • Boat unavailable.
  • Departure cancelled.
  • Other operational inability to provide the booked service.
[Provider cancellation remedies, refund and replacement rights to be provided.]
Replacement or alternative

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.

[Alternative / rebooking options, if any, to be defined.]
Section 7

Operational changes to a Trip

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.

Operational (may adjust)
  • Meeting-point refinement
  • Route adjustment due to conditions
  • Checklist or briefing updates
Commercial / potentially material
  • Date
  • Boat
  • Skipper
  • Price
  • Booking mode
  • Capacity / inventory
  • Other legally significant terms

The classification of any given change remains subject to the final policy.

Section 8

Weather & sailing conditions

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

Refund review

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.

1

Cancellation or change request

A request is submitted from an authorized account context and recorded.

2

Booking terms reviewed

The terms recorded on the Booking are examined.

3

Applicable policy reviewed

The policy version applicable to the Booking is applied.

4

Payment record reviewed

The recorded payment history for the Booking is checked.

5

Outcome recorded

The result of the review is recorded against the Booking.

6

Refund status tracked

Where a refund applies, its status is tracked and visible to you.

Section 10

Payment & refund status

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.

Payment statuses
Not started Payment required Pending Partially paid Paid Failed Cancelled / voided (where recorded)
Refund statuses
Refund pending Partially refunded Refunded

Refund method, timing, fees, deposit & installments

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

Group bookings & Crew

Cancelling a group Booking has operational consequences for the people on the Trip, but their commercial and personal situations are handled carefully and separately.

  • Whole Yacht cancellation may affect all invited Crew operationally — a cancelled Trip should no longer appear as an active upcoming holiday.
  • Crew data stays private. Cancellation workflows do not expose sensitive Crew information.
  • No automatic individual refunds. Crew do not individually receive commercial refunds unless their own Booking and payment context supports it.
  • Shared Departures stay independent. Individual Berth and Cabin Bookings may coexist on one Departure; cancelling one Booking should not automatically cancel unrelated Bookings.
  • Whole Yacht inventory may release only according to the platform and business workflow — immediate resale or relisting is not promised.
Shared Departure safeguard

Cancellation of one Booking on a shared Departure must not automatically affect other, unrelated Bookings on the same Departure.

Section 12

Skipper-only Bookings

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.

Skipper Request Offer Accepted Offer Booking Trip

The Booking preserves the recorded skipper fee, dates, travel-cost assumptions, accommodation assumptions, inclusions, exclusions, conditions and the Offer version.

No single all-in total

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.

[Cancellation terms specific to Skipper-only Bookings to be provided.]
Section 13

No-shows & missed departure

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

Traveller-side disruption & insurance

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

Exceptional circumstances

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

Consumer rights & legal classification

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

How to request a cancellation or change

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.

Step 1

Open My Holidays

Go to your holidays and select the relevant Holiday.

Step 2

Open the Booking context

Open the Booking and payment context for that Holiday.

Step 3

Request cancellation or change

Start a cancellation or change request and review the recorded terms.

Step 4

Review recorded terms

See the terms recorded on your Booking before you submit.

Step 5

Submit request

Submit the request for review.

Step 6

Track status

Follow the request and any refund status from your account.

A request is not a completed cancellation

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:

01 Request submitted 02 Under review 03 Action required 04 Resolved

These states are shown only where the final workflow supports them.

Section 16

Support & disputes

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

Changes to this Policy

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.

What changed

[Change summary to be provided. No version history is fabricated in this prototype.]
Section 18

Contact

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.

Questions about your Booking

Support and contact route:

[Support / contact route to be provided.]

Legal contact

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?

A quick navigation guide

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.

I want to cancel

  • Check your recorded Booking terms.
  • Submit a cancellation request from the Booking.

My Trip details changed

  • Compare the recorded Booking with the current Trip or Departure.
  • Review the change before taking any action.

My skipper or Departure was cancelled

  • Open the Booking.
  • Review the available options once the policy rules are defined.

I’m waiting for a refund

  • Open Payments.
  • Check the recorded refund status.

Product navigation guide — not a statement of refund entitlement.

Illustrative scenarios

How the model behaves — in outline

These are non-binding structural examples. They show how the pieces relate. They do not show percentages, amounts or entitlement.

Example A Whole Yacht

The Booking Owner requests cancellation

A Whole Yacht Booking Owner submits a cancellation request from their Booking.

Outcome depends on the recorded Booking terms and the final Cancellation Policy.
Example B Individual Berth

One traveller cancels on a shared Departure

A traveller cancels their own Berth Booking on a Departure shared with others.

Unrelated Bookings on the same Departure remain separate and are not automatically cancelled.
Example C Skipper Only

A cancellation follows an accepted Offer

An accepted Offer created a Skipper-only Booking, and the customer requests cancellation.

The review uses the accepted Offer version and the recorded Booking terms.
Example D Departure change

The Boat changes after Booking

A Departure’s Boat changes after a Booking was made.

The current Departure should be compared with the recorded Booking rather than silently overwriting it.
Prototype only — no Booking, cancellation or refund record was changed. Effective date, last updated and version are “To be provided”. This is not final, legally approved policy.