GDPR and Hotel Software: Obligations, Deadlines, Checklist
Few small businesses process as much personal data as a hotel: names, addresses, dates of birth, passport numbers of foreign guests, payment details, length of stay, and sometimes notes on allergies or travel habits. The General Data Protection Regulation (GDPR) applies with no minimum threshold: a six-room guesthouse has to follow the same principles as a chain with sixty properties.
That sounds more daunting than it is. Most of the GDPR obligations of an accommodation business can be met with clear responsibilities, a good choice of software and a few documents you set up once. This article sorts out what really needs to be done, without the legalese but with the articles and deadlines you should know. It is not a substitute for legal advice; for special cases, a data protection consultant or your data protection authority can help. And although fines can in theory be substantial, authorities usually take an advisory approach with small businesses at first. The real risk is ignoring the topic altogether.
What data your property collects, and on what legal basis
Good news first: you don't need your guests' consent for your core business. The GDPR recognizes several legal bases, and in a hotel three of them matter most:
- Performance of a contract: booking details, billing address, stay data: anything needed to handle the stay can be processed without further permission.
- Legal obligation: guest registration requirements, tax retention rules for invoices, tourist tax: here the authorities actually require you to process the data.
- Legitimate interest: for example, a guest database with stay history for returning guests, as long as the guests' interests are respected.
You mainly need consent for marketing, typically your newsletter. It must be given actively (no pre-ticked boxes) and can be withdrawn at any time. In practice, that means keeping booking and newsletter sign-up clearly separate, including in the booking process on your website, such as your booking engine.
Be careful with specially protected information: if your team notes a guest's allergies or intolerances, that is health data, a special category of personal data. Only record such information if the guest shares it for their stay, keep internal notes factual, and delete them once they are no longer needed. Also keep in mind that guest comments in your software are covered by access requests, so never write anything a guest shouldn't read.
Data processing: the agreement with your software provider
As soon as your guest data is stored in cloud hotel software, the provider processes that data on your behalf. Article 28 of the GDPR requires a data processing agreement (DPA) for this: a written contract that sets out what the provider may do with the data, how it protects it, and that it will not use it for its own purposes. Without this agreement, using the software is formally a data protection violation, and you are the one responsible, not the provider.
Fortunately, in practice this is straightforward: reputable providers offer a standardized DPA. With Casona, you can conclude it directly in the software, so the obligation is taken care of in a few minutes. When comparing providers, also check the server location: if the data is stored in the EU, you avoid the complicated questions around transfers to third countries that come up with providers hosting outside the EU. Casona runs its own servers in Germany, and all data is transmitted with TLS encryption. What these terms mean is explained on the data protection and hosting page.
Storing and deleting: your deletion policy
The GDPR requires that personal data is not kept longer than its purpose requires. In a hotel, this seems to clash with tax retention obligations, but in fact the two fit together into a simple framework:
| Type of data | Retention | Reason |
|---|---|---|
| Invoices and accounting records | several years (tax retention periods) | statutory retention obligation |
| Guest registration forms (where required) | as long as local law prescribes, then destroy | local registration requirements |
| Guest database / master data | as long as a business relationship is plausible | legitimate interest; review regularly |
| Newsletter data | until consent is withdrawn | consent |
What matters is that your property not only knows these periods but also acts on them: at its core, a deletion policy is a table like the one above plus the answer to who deletes what, and when. Good software helps by monitoring retention periods automatically instead of hoarding data indefinitely.
Data subject rights: when a guest asks
Every guest has GDPR rights toward your property, and you must be able to respond, generally within one month:
- Access: What data do you hold about me? Software with a central guest database helps here: in Casona, a guest's personal details, addresses, reservations and documents are all collected in the guest profile, instead of having to be pieced together from emails and folders.
- Rectification: Incorrect data must be corrected.
- Erasure: Data with no retention obligation must be deleted on request. Invoices, on the other hand, may and must be kept despite a deletion request, and you can explain this to the guest.
- Objection and withdrawal: particularly regarding marketing; an unsubscribe link in your newsletter is mandatory.
Your required documents and deadlines at a glance
- Record of processing activities (Art. 30 GDPR): a structured overview of the data processing that takes place in your property (reservations, guest registration, video surveillance, newsletter …). Small businesses usually need one too, because guest data is processed on a regular basis. Once created, it just needs to be kept up to date.
- Privacy policy: on your website and as a notice or in the guest information folder. It tells guests what happens to their data.
- Data processing agreements: with every service provider that processes guest data for you: hotel software, newsletter service, your accountant's platform, web host.
- Reporting data breaches: if a laptop with a guest list is lost or data becomes accessible to unauthorized people, you generally have to report the incident to your data protection authority within 72 hours (Art. 33 GDPR). Decide in advance who in your team will handle this if it happens.
- Data protection officer: under the GDPR, appointing one is mainly required when your core activities involve large-scale monitoring of people or large-scale processing of special categories of data. Some countries add their own thresholds, for example based on headcount, so check your national data protection law. Most small properties won't need one, but they remain responsible for data protection all the same.
Data protection at the front desk: the simple measures
The GDPR calls for "appropriate technical and organizational measures". In everyday hotel life, this unwieldy phrase mostly comes down to habits that cost nothing:
- Individual user accounts: every team member works with their own login to the hotel software, no shared password on a sticky note. That way it's always clear who changed what, and when someone leaves, you deactivate their account instead of passing a password around.
- Screens and printouts: waiting guests can't see the front desk screen, and arrival lists don't lie openly on the counter.
- Discretion: don't say room numbers out loud, and as a rule never give out information about guests ("Is Mr. Smith staying with you?").
- Separate networks: guest Wi-Fi and your business network should be strictly separated.
- Dispose of paper properly: old lists and registration forms belong in the shredder, not the recycling bin.
How to recognize privacy-friendly hotel software
Since most guest data lives in your hotel software, your choice of software largely determines your level of data protection. These questions are worth asking when evaluating providers:
- Where are the servers located: in the EU?
- Is there a data processing agreement under Art. 28 GDPR, and how quickly can it be concluded?
- Is data transmission encrypted all the way through?
- Does the software support guests' access and data export requests?
- Are statutory retention and deletion periods (for registration forms, for instance) taken into account automatically?
- What happens to your data if you cancel? Is there a complete export?
These points belong in every vendor comparison, on an equal footing with price and features. For a structured decision guide, see our in-depth hotel software comparison.
Conclusion: data protection is about organization, not rocket science
The GDPR doesn't require a small hotel to have a legal department, just good order: knowing which data is stored where; agreements with the service providers that process it; deadlines for deletion; and one person who takes responsibility. If you also use software that hosts in the EU, provides the DPA out of the box and has export and deletion processes built in, the technical side is largely taken care of, and you can get back to what really brings guests back: being a great host.

