AI Privacy Notice
DRAFT — NOT APPROVED. Complete all controller and provider facts and obtain review before publication.
1. Who is responsible
[HOTEL LEGAL OPERATOR, ADDRESS AND PRIVACY CONTACT] determines why guest-service AI is used and ordinarily acts as controller. HOSVERA processes information on its documented instructions where it acts as processor. HOSVERA or a provider may have separate controller purposes only where independently identified and disclosed. Contract labels do not override actual roles. Contact the hotel for rights requests and a staffed alternative.
2. Information and recipients
The text assistant sends your question, up to six recent conversation turns, selected published information from this hotel, and language instructions to the configured AI provider. It does not deliberately include your room PIN, session token, stay identifier or private guest records in the model request. Anything you type may nevertheless contain personal information. Avoid names, room details, health information, card data, passwords and identity documents. Optional voice sends audio for inference and transcription to the configured voice provider; microphone access begins only when you choose to start. Browser, hosting and security systems also process technical connection data. [VERIFIED PROVIDER ENTITIES, PURPOSES, REGIONS AND SUBPROCESSOR LIST].
3. Purposes and lawful basis
The hotel uses AI to answer requested hotel questions; access validation and proportionate security controls protect the service. The controller must document a GDPR Article 6 basis for each purpose, for example contractual necessity where genuinely necessary or legitimate interests following necessity and balancing assessment. AI use is optional and ordinary hotel service remains available through staff. This notice is not consent. Additional Article 9 conditions are needed before intentionally processing special-category information. AI chat does not authorise marketing; Irish electronic marketing rules and applicable opt-in or limited customer exceptions must be assessed separately.
4. Retention and security
The text request uses store:false, which disables application response storage at the inference API; it is not a promise of zero provider retention. [APPROVED HOTEL, HOSVERA, PROVIDER, AUDIO, LOG AND BACKUP RETENTION PERIODS OR CRITERIA, DELETION PROCESS AND LEGAL HOLDS]. Access expiry at checkout does not erase all records. Authorisation is hotel-scoped and prompts must be treated as untrusted. Human access must be limited, justified and logged. The current text handler logs fixed error categories rather than conversation bodies; deployed infrastructure logging needs independent verification.
5. Transfers and training
[VERIFIED INFERENCE/SUPPORT LOCATIONS, TRANSFER MECHANISMS, SAFEGUARDS AND HOW TO OBTAIN THEM]. Database hosting location alone does not determine AI processing location. Provider account settings, contractual terms, training opt-ins, abuse-monitoring exceptions and subprocessor arrangements require verification. No guarantee of zero retention, EEA-only inference or non-training is made solely from source code.
6. Your choices and rights
You may use hotel staff instead. Subject to GDPR conditions you may request access, correction, erasure, restriction, portability and object to relevant processing. Consent, where actually used, may be withdrawn prospectively. Ask the hotel about human review of a disputed response and how information is deleted from relevant systems. The assistant is not authorised to make legally or similarly significant decisions. You may complain to the Irish Data Protection Commission at www.dataprotection.ie. Contact [VERIFIED HOTEL PRIVACY CONTACT].