DPDP for travel and hospitality, from booking to checkout
Take only the guest data each stay or trip needs, keep what a law requires, and know where every booking travels.
An illustration of the Travel & hospitality pack's tasks in the platform.
This is general information, not legal advice. For your own situation, speak to a lawyer.
Where DPDP bites in Travel & hospitality
Identity documents
Collect only what the purpose needs, protect it with reasonable security safeguards, and keep copies only as long as the purpose or a law requires.Source: s.6(1) · s.8(5); R.6 · s.8(7)Agents and booking partners
A partner that processes bookings on your instructions is your Data Processor, under a valid contract; one that decides its own purposes is a Data Fiduciary.Source: s.8(2) · s.2(i)Data sent abroad
Transfers abroad are allowed except to countries the government restricts by notification, subject to its requirements for foreign states, and to stricter Indian laws.Source: s.16(1) · R.15 · s.16(2)Breaches on the clock
Every personal data breach goes to the Board and each affected guest, with the detailed report within 72 hours; CERT-In wants listed incidents within 6 hours.Source: s.8(6) · R.7(2)(b)
The Travel & hospitality pack
Added to the DPDP tasks every client gets, and kept up to date as data.
- Obligations by journeyDPDP tasks for booking, check-in, the stay, loyalty and feedback.
- Retention rulesGuest and booking record periods you set from the laws that apply.
- Transfer registerEach foreign partner and country, checked against the government's notifications.
- Travel data categoriesGuest, identity document, booking, payment reference and preference records.
- Readiness questionsQuestions for travel and hospitality, added to your readiness assessment.
Key modules
Data inventory & mapping
Each system, its personal data, purposes and one legal basis per purposeVendors & processors
Each processor's contract, due-diligence checks and withdrawal and erasure instructionsRetention & erasure
Retention rules per purpose, erasure when they end, and proof of every stepBreach response
Every breach recorded, with the 6-hour and 72-hour clocks and the Board report
Questions
Can we keep copies of guests' identity documents?
As long as the purpose or a law needs them, then erase them. Where a law requires a guest record, your team sets that period in the platform and the record is kept for it.
Source: s.8(7)
Does DPDP apply to a foreign booking platform?
Yes, where it processes personal data outside India in connection with offering goods or services to people in India. Its partners in India have their own duties too.
Source: s.3(b)
Who reports a breach at a booking partner?
Where the partner is your processor, you do, as the Data Fiduciary, to the Board and each affected guest. Your contract should make the partner tell you at once.
Source: s.8(6); R.7
Official texts: MeitY's data protection page, the Gazette of India, CERT-In.
See the platform with Travel & hospitality data
We show you the platform with sample data from your sector and talk through how your team would use it.