Terms draft

Yaalah service terms

These terms are a production-readiness draft. They describe the intended service boundary for the static preview and future live booking platform, and must be reviewed by qualified legal counsel before public launch.

Static preview is not live ticketing Fares require provider or staff confirmation Payment instructions follow approved review

Service boundary This draft keeps live booking, ticketing, and payment claims gated until provider, finance, and legal approval are complete.

Customer clarity Fare, payment, and ticketing language must stay customer-facing and accurate until Yaalah is fully approved for public production use.

Operational handoff Refund, change, and disruption outcomes should be confirmed through approved staff workflows before customer commitments are made.

Booking Requests

Submitting a booking request does not guarantee availability, fare, ticketing, baggage allowance, seat assignment, or travel eligibility until Yaalah staff or connected providers confirm the request.

Fares And Availability

Flight fares, taxes, rules, baggage, schedules, and availability may change until confirmed and ticketed. Yaalah should show clear customer-facing messages when fares require staff review or provider confirmation.

Payments

Payment features remain unavailable for live use until approved payment credentials are connected and tested. In production, payment instructions should only be issued after fare review and must be verified before ticketing.

Changes, Cancellations, And Refunds

Changes, cancellations, refunds, and no-show rules depend on airline, provider, fare, and payment conditions. Customer-facing terms should clearly explain when fees or restrictions may apply.

Travel Responsibility

Travellers remain responsible for valid passports, visas, health requirements, transit rules, names matching travel documents, and arrival at the airport on time.

Preview Boundary

The current hosted version is a static preview. It does not provide live flight inventory, live booking, live payment processing, ticket issuance, automated refunds, or real account authentication.

Customer Support

Support channels should help customers understand booking status, payment status, ticketing status, and next steps. Production support details must be approved before public launch.