TRAVEL STANDARDS
Trust should be designed before bookings open.
These standards describe what must be clear before a departure opens. They do not claim that every operating process is active for every pilot concept.
Clarity before payment
A departure should not ask for payment until the itinerary, responsible partners, full price, inclusions, exclusions, minimum group conditions and customer terms can be reviewed in plain language.
Hosted, with defined responsibility
A host should have a clear role, appropriate preparation and an escalation path. Hosting can improve coordination and support, but it cannot remove every risk or control every traveller decision.
- A named role and pre-departure briefing
- Supplier and route checks appropriate to the trip
- A documented incident and escalation process
- Clear boundaries between Akale, suppliers, hosts and travellers
The right group, described honestly
Each departure should state who it suits, expected activity level, rooming options, broad group context and whether it is suitable for children. Not every trip will be right for every traveller.
Private by default
Akale does not expose private account or booking records for public stranger browsing. A traveller may separately choose a limited social profile for matching and trip introductions, control the details it contains and hide it again. Exact location, contact details, documents, accessibility information and emergency records are never part of that profile.
Respect and conduct
Future departures should use a clear code of conduct, respectful rooming practices and a way to raise concerns. Cultural familiarity should never excuse exclusion, pressure or unsafe behaviour.
Before any trip becomes bookable, Akale will replace concept language with the specific standards, responsibilities and terms that apply to that departure.
Browse departures