DemoNothing here is real, and it all resets every night. Pay with the test card 4111 1111 1111 1111, any future date and any CVC.

See the company side

Privacy Policy

Last updated 2026-07-20 · Version 1

DRAFT — for legal review. First draft reflecting how the Platform actually handles data. Not legal advice; not binding until reviewed and approved by a qualified lawyer (note KSA PDPL — Personal Data Protection Law — requirements). Bracketed items `[…]` need decisions.

Last updated: [DATE] · Effective: [DATE]

1. Who we are

Rihla (the "Platform") is operated by [LEGAL ENTITY NAME], [CR number], [address]. We are the data controller for personal data processed through the Platform. Contact: [privacy email].

2. What we collect

  • Account data: name, email, phone number, password (stored hashed), preferred language, and role (traveler / provider / staff).
  • Booking data: the Trips you view and book, participant details you provide for a booking (e.g. names, dates of birth, and any fields the Provider requires such as nationality), booking history, and support messages.
  • Payment data: payments are processed by our payment provider ([Moyasar]). We receive a payment status and reference; we do not store your full card number or CVV.
  • Provider data (for Providers): company details, verification documents, bank/payout details, and commission settings.
  • Technical & usage data: device information, IP address, app/version, and how you use the Platform (for security, analytics, and fraud prevention).
  • Communications: OTP codes (SMS), emails we send, and notifications.

3. How we use your data

  • To create and manage your account and authenticate you.
  • To process bookings and payments and to share the details a Provider needs to deliver a Trip.
  • To send transactional messages (OTP, booking confirmations, trip updates, support replies) and, where you have opted in, other notifications.
  • To operate, secure, and improve the Platform, prevent fraud and abuse, and enforce our Terms.
  • To comply with legal obligations (e.g. tax/invoicing, lawful requests).

4. Who we share it with

  • Providers: when you book, we share the booking and participant details the Provider needs to deliver and manage that Trip.
  • Service providers: our payment provider ([Moyasar]), SMS provider ([Twilio]), email provider ([SendGrid]), and file/image storage ([Backblaze]) — each only for the purpose of providing their service to us.
  • Legal & safety: authorities or third parties where required by law or to protect rights, safety, or prevent fraud.
  • We do not sell your personal data.

5. Payment data

Card details are entered into and handled by our PCI-compliant payment provider. Rihla stores only what it needs to reconcile a booking (payment status, reference, amount, and the last-4 / brand where provided) — never full card numbers or security codes.

6. Data retention

We keep personal data for as long as your account is active and as needed to provide the service, then for the period required to meet legal, tax, accounting, and dispute-resolution obligations [specify periods with legal], after which we delete or anonymize it.

When you delete your account. You can delete your account in the app or on the website at any time when you have no upcoming trip. We then:

  • remove your name, email, phone number and photo from the service, and delete your saved travellers, favourites, trip alerts and linked Google or Apple sign-ins.
  • remove the identity numbers, contact details, health information and other details from the traveller entries on your past bookings. The names of the people who travelled with you stay on those bookings.
  • keep your past bookings and payments, without your details, because payment records must be kept and trip organisers need their trip history.
  • keep a separate, locked record of your name, email, phone number and which bookings were yours for two years [confirm period with legal], so that we can respond to a dispute, a chargeback, a legal claim or a request from an authority about one of those bookings. Only staff with a specific permission can open it, every access is logged, and it is deleted automatically when the two years end.

7. Your rights

Subject to applicable law (including PDPL), you may request to access, correct, or delete your personal data, object to or restrict certain processing, and withdraw consent where processing is based on consent. Contact [privacy email]. We may need to verify your identity and may retain data where we have a legal basis to do so.

8. Security

We use technical and organizational measures to protect your data, including encryption in transit, hashed passwords, secure token storage on mobile devices, access controls, and audit logging of privileged actions. No system is perfectly secure, but we work to protect your data and to notify you and the regulator of breaches where required.

9. Cookies & similar technologies

The web app uses cookies/local storage necessary for login and core functionality, and [analytics — specify]. [Cookie banner/consent approach — confirm with legal.]

10. Children

The Platform is not directed to children under [18]. Where a booking includes minors, it must be made and supervised by a responsible adult, who is responsible for the minors' data provided.

11. International transfers

Some service providers may process data outside the Kingdom of Saudi Arabia. Where they do, we take steps required by applicable law to protect your data. [Confirm transfer mechanism with legal per PDPL.]

12. Changes & contact

We may update this Policy and will post the new effective date; material changes will be notified [in-app / by email]. Questions or requests: [privacy email] · [company address].