How long should a UK hotel keep guest records in its PMS?
Set separate retention rules for reservations, invoices, registration records and guest preferences, then check whether your software can carry them out.
A UK hotel should keep each category of guest data only for its justified purpose and applicable legal period. Required hotel registration records have a minimum 12-month retention requirement; financial records follow separate tax rules. Preferences and marketing records need their own review dates. Your PMS should support this separation: keeping an invoice does not justify keeping every guest note or keeping someone on a marketing list.
Which retention periods actually apply?
UK hotel guest data retention starts with purpose. The ICO’s storage limitation guidance sets no universal GDPR retention period. Document why each record is needed and delete or anonymise it when that purpose ends.
For premises covered by the Immigration (Hotel Records) Order 1972, Article 5, required registration records must be kept for at least 12 months. The 1982 amendment changes a nationality definition, not that minimum. This concerns the statutory register, not every PMS field. Using departure as the operational trigger avoids expiring a record while a guest is still staying; it is a policy choice, not wording specified by Article 5.
- Limited companies: GOV.UK requires accounting records for six years from the end of the last company financial year they relate to, with longer retention in specified cases.
- Self-employed operators: business records generally need at least five years after the relevant 31 January submission deadline. Very late returns have different rules.
- VAT-registered businesses: VAT records generally need at least six years; OSS/MOSS records have a ten-year rule where applicable.
Ask your accountant to confirm which financial rules apply together. Keep necessary transaction evidence; do not extend the same period to unrelated preferences.
Build a retention matrix by record type
Use this matrix as your working structure. The access assignments are suggested roles; your hotel must approve the purpose, lawful basis and exact review or disposal date for each category.
| Record | Purpose | Data source / rule | Trigger and retention | Access | End action |
|---|---|---|---|---|---|
| Reservation | Deliver the stay; resolve booking queries. | PMS, booking channel; documented operational and claims policy. | Check-out or cancellation; review against remaining queries and justified claims periods. | Reception while active; manager for retained evidence. | Remove unnecessary contact details and notes; retain only justified transaction or dispute evidence. |
| Invoice and payment record | Accounts, tax and reconciliation. | PMS and accounting system; applicable HMRC rules above. | Relevant financial year or tax deadline, not simply departure; apply all relevant minimum periods. | Finance and authorised accountant. | Preserve required invoice details until expiry; securely delete when no obligation or hold remains. |
| Statutory guest registration | Meet the hotel registration obligation. | Guest register; Article 5 of the 1972 Order. | At least 12 months; document the trigger, for example departure. | Authorised manager; lawful official inspection. | Securely delete after the minimum and any justified extension; remove duplicate exports. |
| Preference or service note | Fulfil a request or provide justified repeat-guest personalisation. | Guest request; hotel purpose and review policy. | Review at departure; retain longer only for a documented continuing purpose. | Staff delivering that service. | Delete expired notes; review sensitive details separately. |
| Marketing permission and suppression | Demonstrate permission and respect objections. | Opt-in form, consent wording and withdrawal log; ICO marketing guidance. | Review while used; act on withdrawal immediately. Keep only necessary evidence afterwards. | Marketing administrator; restricted compliance access. | Stop campaigns; remove unneeded profile data and preserve minimal suppression information. |
| Incident or dispute evidence | Investigate an incident or establish, exercise or defend a claim. | Case file and relevant communications; provider deadlines and legal advice. | Incident or dispute opening; dated hold and review after resolution and applicable claims periods. | Named manager, adviser or insurer as appropriate. | Release the hold when justified; delete unrelated data and expired evidence. |
For marketing, record what the guest agreed to, when and how. The ICO’s marketing planning guidance requires justified retention, not an indefinite mailing list. This matrix does not authorise collecting additional identity documents.
Make deletion work across every copy
- Assign one owner to review due records and approve exceptions. Record the reason, scope and next review date for each hold.
- Map copies in accounting software, marketing tools, inboxes, exports and paper files. Assign a deletion action to each system owner.
- Test a fictional record: confirm what disappears, what remains for a legal purpose, and whether a later import recreates deleted details.
- Log the category, action date, rule and approving role without creating another full guest-data archive.
Backups need an explicit rule. Under the ICO’s erasure guidance, backup data may remain temporarily until scheduled overwrite if it is put beyond use. Agree the overwrite cycle and a restore procedure that reapplies deletions.
Illustrative example: one stay, three disposal decisions
A fictional 20-room hotel in England operates as a limited company. A guest leaves on 10 October 2026; the relevant financial year ends on 31 December 2026. Assume no open dispute, investigation or other reason to extend retention.
At departure
Delete the fulfilled extra-pillow note if there is no continuing need. It does not inherit the invoice’s retention period.
11 October 2027
Under this hotel’s departure-based policy, review the statutory register entry for deletion after its 12-month minimum.
1 January 2033
Review the accounting record for disposal after keeping it through 31 December 2032: financial year-end plus six years.
These are separate record decisions. A justified hold on the invoice would not automatically preserve the pillow note or permit marketing.
Test the retention workflow in a RoomRaccoon demo
RoomRaccoon’s UK PMS page describes reservation details, guest lists, invoicing and automated guest communication. When assessing its hotel property management system, ask how those records can follow different retention rules.
Request a demonstration of removing an expired preference while preserving a required invoice, restricting access to retained evidence, and recording the outcome. Confirm whether each control is standard, package-dependent, manual or support-assisted. Automatic retention schedules and deletion across connected systems must be verified for your proposed setup.
For hotel software integrations, check which data each named UK connection receives and who handles deletion. A directory listing does not establish that a deletion request propagates.
Bring your retention matrix and a fictional booking. Ask: “Can you show what is deleted, what remains and why, including copies in our accounting and marketing tools?”
Discuss guest data controls in your demoQuestions about keeping guest records
Does an erasure request mean deleting every invoice?
No. Necessary retention for a legal obligation or legal claims can limit erasure. Assess each category, remove data no longer needed and explain what you retain and why. Do not reject the entire request just because one invoice must remain.
Should unsubscribing delete every trace of an email address?
Stop the marketing covered by the withdrawal. The ICO recommends a minimal suppression record to prevent accidental recontact. Keep it separate from active marketing profiles; it is not permission to continue campaigns.
Is removing a guest’s name enough to anonymise a record?
No. An email address, booking reference or other linkable details may still identify the guest. Retain genuinely anonymous statistics only when identification is no longer possible; a reversible identifier remains personal data.
Sources and scope
Checked on 10 November 2026. The ICO marks its storage limitation and erasure guidance as under review following the Data (Use and Access) Act. Recheck applicable guidance when approving your hotel’s schedule.
- ICO: storage limitation, erasure, marketing retention and suppression.
- UK legislation: 1972 Hotel Records Order and 1982 amendment.
- GOV.UK: company records, self-employed records and VAT records.
- RoomRaccoon: UK PMS and integrations pages linked above; capability checks are demo criteria, not a compliance guarantee.












