Private by design, from discovery through travel.

Information you choose to provide

Akale records the details needed for the service you use. Required fields are shown at the point of collection. Your private account remains separate from any limited social profile you explicitly choose to enable.

• Email, name, phone and preferred language
• Origin, travel style, accessibility and dietary preferences
• Booking party and traveller details for a selected departure
• Support messages, cancellation requests and trip feedback
• Optional future-trip interests, circle messages, polls, memories and social profile details
• Trusted contacts, safety check-ins and location shares you start for a limited time
• Consent, policy acceptance and account activity records

How the information is used

Information is used to operate accounts, plan demand, create and service bookings, coordinate eligible trip groups, match overlapping travel interests, provide safety and customer support, prevent misuse and meet legal obligations. Private traveller details are not used for public stranger browsing.

Community, matching and live location

Social visibility is optional and limited to the fields you choose. Confirmed trip circles are restricted to eligible travellers, assigned hosts and authorised staff. Live location sharing is off by default, visible only to the assigned host and authorised Akale care staff, expires automatically and can be stopped early. It is never shown to the trip circle. Do not post passport, payment, health, home-address or other sensitive information in chats, polls or shared memories.

Payments and sensitive travel records

A configured payment provider processes payment credentials. Akale stores booking totals, transaction references, status and refund records, not full card or bank credentials. Passport, identity, health or emergency details should be requested only when a confirmed trip genuinely requires them, through a protected workflow with a stated purpose and retention period.

Storage, access and sharing

Akale uses Supabase for account and application data. Row-level access controls separate traveller, host and operations access. Only the minimum necessary details should be shared with assigned hosts, responsible suppliers and service providers for the applicable trip, support request, payment or legal requirement.

Retention, security and your choices

Operational and security records should be retained only for their stated purpose or a documented legal need. You can hide the social profile, stop a location share and unsubscribe from marketing without losing essential booking messages. Akale will publish verified operator and privacy contact details before payments open, including a process to request access, correction or deletion where applicable.