On 13 August 2025, Italy's digital agency, AgID, reported that identity documents stolen from Italian hotels were being sold online. The seller, using the name mydocs, claimed to have broken into hotel systems between June and August. On 9 and 10 August alone, listings appeared for more than 70,000 documents from four hotels. They were the passport and ID scans guests had handed over at check-in.
Indian front desks collect the same scans every night. A passport gets photographed for the foreigner report. An Aadhaar copy lands on the duty manager's WhatsApp because the guest arrived at 1 a.m. Ask a general manager where those copies live and the first answer is usually the property management system (PMS). The real answer takes a week of digging.
The Digital Personal Data Protection Rules, 2025 were notified on 13 November 2025 under the Digital Personal Data Protection Act, 2023. Rule 1(4) brings Rules 3 and 5 to 16 into force eighteen months later, in May 2027. Those rules cover notice, security, breach intimation, retention and children's consent. That leaves a hotel group about six months. None of those duties can be met for guest data the hotel hasn't found.
Every duty under the Act starts with a location
Rule 3 sets the floor for a notice. It must give an itemised description of the personal data and the specified purpose for processing it. A hotel can't itemise data it has never listed.
The guests already on file raise a second problem. Section 5(2) says that where a guest consented before the Act commenced, the hotel must send her a notice as soon as reasonably practicable. A loyalty base built over fifteen years is exactly that population. The hotel needs to know which systems hold those guests before it can write to them.
Erasure follows the same logic. Section 8(7) requires erasure once consent is withdrawn or once it is reasonable to assume the purpose is no longer served. Section 8(7)(b) extends that duty to data the hotel has handed to its processors.
Rights requests are the hardest test. Under Section 11(1)(b), a guest can ask for the identities of every Data Fiduciary and Data Processor that received her data. For most hotels that means naming an online travel agency (OTA), a payment gateway, a spa software vendor and a marketing agency. Rule 14(3) caps the grievance response period at ninety days.
So data discovery is the first workstream, ahead of any policy drafting. A policy describes a data estate, and discovery establishes what that estate really is.
Where guest data actually sits
A full-service property usually holds guest personal data in these places:
| System | What it usually holds | Easy to miss because |
|---|---|---|
| PMS and central reservations | Stay history, contacts, preferences, ID numbers | Free-text notes hold anything staff type |
| Booking engine and website | Booking forms, cookies, tracking tags | Tags pass data to ad platforms |
| OTA extranet and channel manager | Names, phone numbers, special requests | Data arrives through a vendor feed |
| Front-desk scanner and shared drive | Passport, Aadhaar and licence copies | Scans save outside the PMS |
| Form-III records | Foreign guests' passport and visa details | Copies kept locally after filing |
| Email and WhatsApp | Rooming lists, ID copies, card details | Personal phones, no retention rule |
| Guest Wi-Fi | Mobile numbers, device identifiers, session logs | Run by an outside provider |
| CCTV | Images of every guest, including children | The recorder's overwrite setting decides retention |
| Spa, F&B and point-of-sale | Allergies, treatment notes, dining history | Separate vendors, separate databases |
| Loyalty and CRM | Profiles, birthdays, companion details | Usually run at brand level |
The structured systems are the easier half. Vendor exports and scanning tools will find PMS tables and customer relationship management (CRM) records within days. The harder half is unstructured. Corporate bookers email rooming lists as spreadsheets. Wedding planners send guest lists, with ages, over WhatsApp. Sales managers keep both on their own phones.
Guest Wi-Fi is a regulated record in its own right. The Department of Telecommunications' February 2009 instructions to internet licensees name hotels among public hotspot locations. They also require registered, centrally authenticated access. So the login trail usually sits with the provider, and the hotel needs to know what that provider keeps.
Paper deserves its own pass. Section 3(a)(ii) brings data collected on paper and digitised later within the Act, so a scanned registration card counts. We covered this in more depth in how the Act treats paper records and scanned documents.
ID copies and Form-III: collected under one law, kept under another
The Immigration and Foreigners Act, 2025 came into force on 1 September 2025. Section 8 puts a reporting duty on the keeper of any accommodation. Under Rule 17(5) of the Immigration and Foreigners Rules, 2025, a hotel must transmit Form-III within 24 hours of a foreigner's arrival. Form-III replaced the old Form C.
A Dimapur Police notification published in February 2026 adds that Rule 17 records must be kept electronically for at least one year. Goa's information department has flagged a penalty of ₹50,000 per case for accommodation providers that fail to report.
That record is retention required by law. Section 8(7) doesn't force the hotel to erase it before the legal period ends. But the duty attaches to the record. It doesn't obviously extend to the passport photo saved on the reception PC or the copy forwarded to a staff phone. Map each copy to the rule that requires it. A copy that no rule requires has no retention basis under Section 8(7).
Indian guests raise a parallel issue. In December 2025, Business Standard reported that the Unique Identification Authority of India (UIDAI) had approved a registration rule for entities seeking Aadhaar-based verification. Hotels were named among them. PTI's report added that storing Aadhaar photocopies in physical form already contravenes the Aadhaar Act. As of 30 August 2026, Business Today still described the framework as proposed. Either way, Aadhaar images in a scanner folder are a liability under two laws.
Family stays and the child at the front desk
Section 2(f) defines a child as anyone who has not completed eighteen years. That includes the teenager on a family holiday and the school group in the banquet wing. Section 9(1) requires verifiable parental consent before the hotel processes any personal data of a child. Section 9(3) bars tracking, behavioural monitoring and targeted advertising directed at children.
The Fourth Schedule to the Rules exempts some classes from these duties. They include clinical establishments, educational institutions and crèches. Hotels aren't on the list. The Schedule to the Act sets the penalty ceiling for breaching Section 9 at ₹200 crore.
Rule 10 was written with online accounts in mind, but the front desk has one advantage. Rule 10(1)(a) lets the hotel check the parent against reliable identity and age details it already holds. At check-in, the hotel is verifying that parent's ID anyway. Our reading is that a recorded consent step, tied to that verification, is the workable route. Take advice on your own facts before relying on it.
Discovery then has to find where children's data already sits. Look for date-of-birth fields on companion profiles, kids' club registers and birthday offers keyed to a child's age. Check the property's social media accounts for photos from children's events. Each item needs a parental consent trail or deletion. Run a data protection impact assessment on the kids' club and on any family-targeted marketing before May 2027.
What can go at checkout, and what has to stay
Many hotel teams read Section 8(7) as an instruction to delete guest data when the guest leaves. The Rules make that reading unsafe.
Rule 8(3) requires every Data Fiduciary to retain personal data, associated traffic data and processing logs for at least one year from the date of processing. The floor serves the purposes in the Seventh Schedule, such as the State's functions under law. It covers processing done by a Data Processor too. Rule 6(1)(e) separately requires one year of logs and personal data for investigating unauthorised access.
The Third Schedule's three-year inactivity rule applies to only three classes. The first is e-commerce entities with at least two crore registered users in India. The other two are large online gaming and social media intermediaries. A large OTA should check the e-commerce threshold. A hotel's own booking engine below that line falls back on the general test in Section 8(7).
Other laws add their own floors. The Indian Computer Emergency Response Team (CERT-In) directions of 28 April 2022 require a rolling 180 days of information and communication technology (ICT) system logs, kept in India.
Card numbers need separate handling. The Reserve Bank of India (RBI) circular of 28 July 2022 states that from 1 October 2022, only card issuers and card networks may store card-on-file data. A full card number in a PMS notes field or an emailed authorisation form should go to your payments team the same day.
| Record | Minimum before erasure | Basis |
|---|---|---|
| Processing logs and related personal data | One year from processing | Rule 8(3), Rule 6(1)(e) |
| ICT system logs | Rolling 180 days, in India | CERT-In directions, 2022 |
| Form-III records | At least one year, electronic | Rule 17, Immigration and Foreigners Rules |
| Marketing profile after withdrawal | Stop using now, erase after the floor | Section 8(7), Rule 8(3) |
| Full card numbers | Escalate on discovery | RBI card-on-file circular |
So the retention schedule has layers. For each record type, find the longest legal floor and set an erasure date after it. A guest who withdraws marketing consent should drop out of campaigns at once, even while Rule 8(3) holds the log.
OTAs, gateways and the vendors in between
Section 8(1) makes the hotel responsible for processing done on its behalf, irrespective of any agreement to the contrary. Section 8(2) permits a Data Processor only under a valid contract. Rule 6(1)(f) requires that contract to provide for reasonable security safeguards.
OTAs are harder to place. A guest who books through an OTA gives her data under the OTA's notice. AMLEGALS argues that the hotel then processes on consent it did not collect. S.S. Rana, writing in Bar & Bench, suggests the OTA may be the fiduciary and the hotel its processor. The answer can change with the booking model. It decides whose notice covers the stay.
Discovery settles the facts even where the law is unsettled. List every feed that brings guest data in and every integration that sends it out. For each, record the counterparty, the fields and the governing contract clause. Our note on third-party and vendor compliance under the DPDP Act sets out the clauses worth renegotiating.
Management agreements add another layer. In February 2026, Sujjain Talwar of Economic Laws Practice told The Economic Times that many are 20 to 30-year agreements. He said they never contemplated privacy law.
Owners are waking up to the fact that they could be on the hook for violations they have no control over.
— Sujjain Talwar, Partner, Economic Laws Practice, in The Economic Times
The discovery register is the evidence in that negotiation. It shows whose systems hold which guests' data, and who decides what happens to it.
Breach reporting runs on the inventory
Rule 7(1) requires the hotel to tell each affected guest, without delay, what happened and when. It must also say how far the breach spread and what it means for her. Rule 7(2) requires an intimation to the Board without delay and a detailed report within seventy-two hours. That report covers causes, mitigation, findings on who caused the breach, remedial steps and the notices sent to guests.
The CERT-In clock is shorter. Body corporates must report listed cyber incidents within six hours of noticing them.
The Italian case shows why the inventory decides the outcome. The listings came in batches, hotel by hotel. A hotel in that position must establish within hours which folders held scans, from which dates and for which guests. Rule 7(1) then needs a registered contact for each person in those scans. Without a map, the hotel is guessing.
The penalties are steep. The Schedule sets a ceiling of ₹200 crore for failing to give breach intimation. Failing to take reasonable security safeguards carries a ceiling of ₹250 crore. If your IT team already keeps a CERT-In compliance runbook, extend it. The first hour should pull the data register as well as the network logs.
A six-month discovery plan for a hotel group
This sequence works for a single property or a fifty-hotel portfolio. Adjust the pace to the number of properties.
- Name an owner for each property. The Data Protection Officer or compliance head owns the programme. Each property also needs one named person, usually the front office manager or IT lead, who can open doors and drawers.
- Build the system list from invoices. Pull the vendor payment ledger and the IT asset register. Every recurring software invoice is a system that may hold guest data, including the ones IT never set up.
- Scan the structured stores. Run automated discovery across the PMS, CRM, central reservations, file shares and mailboxes. Classify passport numbers, Aadhaar numbers, card numbers, dates of birth and health notes.
- Walk the front desk at night. Sit with the night auditor for one shift. Check the scanner's save folder, the desktop, the counter phone's WhatsApp and the printed Form-III file.
- Interview sales, events and the spa. Ask where rooming lists, wedding guest lists and treatment forms go after the event. The answer is usually someone's inbox.
- Map every flow to a counterparty. Turn the findings into a data map that shows what goes to each OTA, gateway, Wi-Fi provider and brand system.
- Attach a basis and a retention floor to each row. Mark whether each record rests on consent, a legitimate use under Section 7 or a legal duty. Then set its erasure date.
- Fix the front door last. Rewrite the booking and check-in notices against Rule 3. Put consent management on the booking engine and at the desk. Then open a rights channel that can meet the ninety-day limit.
For the order in which the remaining work should land, see our working-back plan for May 2027.
The register comes first
Every hotel already keeps one register because the law demands it. The Form-III record is filed within 24 hours, kept for the period the Rules set and opened when the police ask. The DPDP Act asks for that same discipline across every system that touches a guest. Build the register before May 2027. The notices, erasure dates and breach reports will then have something to stand on.
This article is general information. It isn't legal advice for a specific situation.
Sources
- Legislative Department, India Code, "The Digital Personal Data Protection Act, 2023 (Act No. 22 of 2023)", as on 19 November 2025. Link
- Ministry of Electronics and Information Technology, "Digital Personal Data Protection Rules, 2025, G.S.R. 846(E)", Gazette of India, 13 November 2025. Link
- AgID, "Breach allegedly hits Italian hotels, compromising personal data of thousands of guests", 13 August 2025. Link
- Biometric Update, "Italy: Nearly 100,000 ID scans from hotel guests found on dark web", August 2025. Link
- DIPR Nagaland, "Dimapur Police notifies on reporting of foreigners' arrival and stay", 10 February 2026. Link
- Department of Information and Publicity, Government of Goa, "Online filling of C-forms under new immigration law", 10 December 2025. Link
- Business Standard, "UIDAI to mandate registration for entities using Aadhaar verification", 7 December 2025. Link
- Free Press Journal, "Hotels and event organisers cannot take customers' Aadhaar cards and store them in physical form, new rule to be issued soon", 8 December 2025. Link
- Business Today, "Do you still need Aadhaar for hotel check-ins? Here's what is changing", 30 August 2026. Link
- Taxguru, "CERT-In issues directions relating to information security practices", reproducing CERT-In directions of 28 April 2022. Link
- Reserve Bank of India, "Restriction on Storage of Actual Card Data [i.e. Card-on-File (CoF)]", 28 July 2022. Link
- Department of Telecommunications, "Instructions under the Internet Service Licence regarding provision of Wi-Fi Internet service under delicensed frequency band", 23 February 2009. Link
- Economic Laws Practice, "New Data Act puts Hotel Companies in a Spot of Bother", 9 February 2026. Link
- AMLEGALS, "From Check-In to Check-Out: DPDP Act, 2023 Compliance for Hotels Explained", 29 July 2026. Link
- Bar & Bench, "Privacy clauses at check-in: How data laws are reshaping hotel contracts", 28 July 2026. Link