How Rahi protects traveller data
Rahi handles traveller locations, phone numbers and identity documents. This page explains what we collect, why, who can see it, and how we protect it. Rahi is designed with the DPDP Act 2023 and DPDP Rules 2025 in mind.
Updated
What we collect and why
- Traveller profile: name and phone number, to let travellers log in with a one-time password and to let the operator manage their trip.
- Emergency contact: so an SOS can reach someone outside the app.
- Trip data: itinerary, stays, rooms, check-ins and announcements, to run the trip.
- Location: only during the trip window, for the live map, headcounts and SOS.
- Documents: ID or passport copies the traveller uploads for the operator, such as for hotel check-in or permits.
- Payment status: amounts recorded by the operator. Rahi does not collect payments or card details.
We use this data only to run the trip it was collected for.
Location
- Location is shared only during the trip window.
- Travellers can pause sharing at any time.
- Sharing turns off automatically when the trip ends.
- Location history is deleted within 7 days of trip end.
- Only authorised operator staff can see the live map. Travellers never see each other's location.
Documents
- Documents are private by default: only the traveller and operator staff the operator authorises can view them.
- Files are encrypted at rest.
- Files are opened only through short-lived signed links, so a forwarded link stops working.
Who can see what
| Role | Can see |
|---|---|
| Traveller | Their own trip, itinerary, room, documents and payment status. Never other travellers' phone numbers, documents, payments or location. |
| Trip Captain | The travellers on the trips they lead: headcounts, announcements, the live map during the trip and SOS alerts. |
| Ops Manager | Departures, rosters, itineraries, rooming and traveller details for their company. |
| Company Admin | Everything in their company, plus billing, staff and templates. |
Tenant isolation
Every record in Rahi belongs to one operator company, and trip data also belongs to one trip. Every query is scoped by company, and by trip where relevant, so one operator can never read another operator's data.
Minors and guardian consent
For trips with travellers under 18, Rahi captures guardian consent, and precise location is visible to staff only during itinerary hours. Operators remain responsible for their own consent forms and school agreements.
Your rights
Travellers can ask to access, correct or erase their personal data. Because the operator decides why traveller data is collected, requests usually go to the operator first. You can also write to hello@rahi.club and we will help, or pass your request to the right operator.
Operator and Rahi roles
For traveller data, the operator decides why and how it is processed and acts as the Data Fiduciary. Rahi processes that data on the operator's behalf as a Data Processor. For data about operator staff and for enquiries sent to us through this website, Rahi decides how that data is used.
If something goes wrong
If a personal data breach affects data we process for an operator, we will inform that operator without undue delay, with the details they need to meet their own obligations to notify affected people and the Data Protection Board.
Infrastructure and service providers
We use a small number of service providers to run Rahi:
- Microsoft Azure, to host the Rahi API and database.
- Cloudflare, to host this website and the operator dashboard.
- An Indian SMS provider, to send one-time passwords, invites and SOS messages.
- Expo push notifications, to deliver app notifications.
- Google Maps, to show maps and locations.
- Sentry, for error monitoring, configured to strip personal data from reports.
Report a security issue
If you think you have found a vulnerability, email hello@rahi.club with the subject “Security”. Please give us a reasonable time to fix it before disclosing it publicly. See also our privacy policy.