1. Controllers and processors
A hotel normally decides why and how guest information is used for its hospitality services and acts as controller for that processing. Where a HOSVERA operator processes information solely on the hotel’s documented instructions, the processor relationship must be covered by an appropriate agreement. Actual decisions and responsibilities determine the roles.
Independent corporate website or account-security processing requires its own controller assessment and notice. HOSVERA LTD operates the corporate website. The company registration number, registered-office address and public contact details remain to be completed.
2. Information in hotel services
Depending on the services enabled by a hotel, records may include guest and stay verification details; pre-arrival contact and request information; dining orders, service requests, messages and feedback; staff accounts, roles and security events; and registered room-device information. Pre-arrival requests do not require an allocated room.
The hotel’s approved notice must identify the actual categories, purposes and lawful bases for its enabled services, rather than treating every optional feature as active.
3. Purpose and minimisation
Each hotel must define the information necessary for the service, provide appropriate notices and restrict access by authorised role. Payment, AI and other external services require their own provider and data-flow assessment before activation. The corporate website does not collect hotel guest records.
4. Retention and deletion
Stay-based access expiry is separate from deletion of business records. Retention must take account of service fulfilment, complaints, applicable financial obligations and proportionate security needs. The hotel must approve periods and procedures for orders, messages, feedback, pre-arrival information, account events and backups.
Deletion or anonymisation, legal holds, backup expiry and the end of a service relationship should be documented. No fixed retention period for hotel records is claimed in this draft.
5. Rights and assistance
People should direct hotel-record requests to the hotel controller. Applicable rights include access, correction, erasure, restriction, objection and portability, subject to legal conditions. The processing agreement should define assistance to the controller and the handling of requests within applicable time limits.
Corporate website requests require a verified corporate privacy contact. Concerns may also be raised with the Irish Data Protection Commission or another competent authority.
6. Providers and international transfers
Contracts must identify relevant providers, their purposes and processing locations, including support access. Where data is transferred outside the EEA, the responsible parties must establish the applicable transfer mechanism and safeguards. A database region does not describe every provider operation.
Read DPA information and Service providers and subprocessors. Those documents remain drafts until identities, contractual arrangements and safeguards are approved.