Hotel guest data protection: GDPR, PCI DSS, and NIS2
A 5-step operational framework for hotels and hospitality groups
Every day, the front desk handles some of the most sensitive data any business collects: passports, payment cards, and personal preferences that can reveal a guest's health or religion. Together, these records often build a fuller profile than a bank holds, yet they rarely get the same level of protection.
The real question isn't which policies a hotel has adopted. It's where guest data ends up after check-in, and what protects it once it gets there.
The cases analyzed in the white paper all point to the same pattern:
- In 2023, MGM Resorts estimated a roughly $100 million impact after a social engineering attack that started with a call to its IT help desk (source: MGM Form 8-K)
- In summer 2025, more than 100,000 scanned ID documents stolen from 12 Italian hotels went up for sale on the dark web (source: CERT-AGID, Italy's government CERT)
- PMS platforms, channel managers, OTAs, and outside vendors multiply the entry points to guest data
- High staff turnover and shared workstations leave credentials active and no record of who did what
A stolen passport scan never expires. It fuels identity theft and fraudulent bank accounts, and it gets resold again and again, long after the original breach.
This isn't a future scenario. It's happening now, at properties run just like yours.
Download the white paper and learn how to govern guest data with protection that follows it wherever it goes.
WHITE PAPER – HOSPITALITY DATA PROTECTION
What's inside the hotel guest data protection white paper
-
What data a hotel actually holds: ID documents, payment cards, reservations, behavioral data, and HR records
-
How the regulations stack up: GDPR, PCI DSS, mandatory guest registration with the police in Italy, and NIS2
-
How long a hotel may keep a copy of a guest's ID, according to Italy's Data Protection Authority
-
Where the industry is most exposed: PMS and channel managers, staff turnover, shared workstations, and outside vendors
-
What three recent breaches reveal: MGM Resorts, Caesars Entertainment, and 12 Italian hotels
-
A 5-step operational framework, from data inventory to breach notification within 72 hours
Free PDF. No spam. GDPR-compliant. Unsubscribe anytime.
Who is responsible for guest data in a hotel?
CISOs and IT leaders
They run the PMS, networks, access controls, and technology vendors. The white paper shows where risk concentrates and how to apply encryption, role-based access, and audit trails.
Hotel general managers and owners
They answer for service continuity and the property's reputation. The white paper explains why a breach shuts down reservations, payments, and check-in, not just IT systems.
DPOs and compliance teams
They answer for compliance with GDPR, PCI DSS, and NIS2. The white paper clarifies the rules on ID retention, breach notification, and vendor management.
From check-in to breach notification: the risks to hotel guest data
A hotel stores ID documents, payment card data, reservations, and preferences that can reveal health or religion. Combined, they form a complete profile that can be resold and used for identity theft.
Front-desk scanners, email, the PMS, online check-in, chat, shared folders, and personal devices. Every copy of an ID that sits outside core systems is an exposure point no one is watching.
In Italy, only until the data has been sent to the police through Alloggiati Web. Once the receipt comes back, the copy must be deleted or destroyed, and only the receipt is kept, for 5 years. Italy's Data Protection Authority confirmed this on April 29, 2026.
PMS platforms tied to dozens of integrations, seasonal staff on shared accounts, and vendors with remote access to the CRM, Wi-Fi, and smart locks. Any access without a named user or an expiry date stays open long after anyone uses it.
At MGM Resorts (2023), the attack began with a phone call to the help desk and took down reservations, payments, and digital room keys. At 12 Italian hotels (2025), attackers stole scans of guests' IDs. The biggest cost is service disruption, and the cause is almost always a person or a vendor.
1. Inventory and minimize data. 2. Classify documents automatically. 3. Encrypt each file so it stays protected after it leaves the hotel. 4. Grant access by role and shift, with instant revocation. 5. Log every access and notify the regulator within 72 hours.
Free PDF. No spam. GDPR-compliant. Unsubscribe anytime.
Frequently asked questions about hotel guest data protection
ID documents, payment card data, reservations, and preferences that can reveal a guest's health or religion, plus employee records. Together they form a complete profile that, once stolen, fuels identity theft and gets resold many times over.
PCI DSS applies wherever a hotel accepts payment cards. In the US, every state has its own data breach notification law. In Europe, GDPR covers all personal data and national rules such as Italy's police guest registration apply locally. NIS2 does not apply to hotels directly, but it can reach them if they run activities in covered sectors or supply services to NIS2 entities.
In Italy, only as long as it takes to send the data to the police through Alloggiati Web. Once the receipt is issued, the copy must be deleted or destroyed, and only the receipt is kept, for 5 years. Italy's Data Protection Authority confirmed this on April 29, 2026.
It depends on the jurisdiction. Under GDPR, within 72 hours of becoming aware of it, to the data protection authority (Article 33). In the US, 20 states set a fixed deadline for notifying affected individuals, as short as 30 days in California, Colorado, Florida, New York, and Washington. The others require notice without unreasonable delay.
PMS platforms and channel managers tied to dozens of integrations, seasonal staff on shared accounts, shared front-desk workstations, and vendors with remote access. Any access without a named user or an expiry date stays open long after anyone uses it.
By encrypting each file, so protection stays in place wherever the document is copied or sent. Add role- and shift-based access with instant revocation, plus an audit trail of every time the file is opened.