1. Parties and instructions
A processing agreement must identify the legal parties, subject matter, duration, purposes, data categories and people affected. It should state the hotel’s documented instructions and the circumstances in which the provider acts as processor.
2. Confidentiality and security
The agreement should define confidentiality, authorised access and appropriate technical and organisational measures. Responsibilities for account administration, incident cooperation and changes must be clear. No certification, service-level commitment or absolute security guarantee is created by this page.
3. Subprocessors and transfers
Subprocessor arrangements require the agreed authorisation process, relevant legal entities, purposes, locations and contractual obligations. Any required international-transfer safeguards and change-notification procedure must be documented.
4. Assistance and accountability
Terms should cover assistance with individual rights, security incidents, data protection impact assessments and information needed to demonstrate the agreed obligations. Audit arrangements, contacts and responsibilities must be proportionate and explicit.
5. End of the relationship
The parties must agree deletion or return, required legal retention, backup handling and confirmation procedures. Access revocation alone does not delete retained records.
6. Before processing on a hotel’s behalf
Verify the operator and hotel identities, instructions, security schedule, provider register, retention, transfers and incident contacts. Appropriate agreements and notices must be approved before real guest data is introduced. A separate corporate website privacy notice does not replace that agreement.
AI processing addendum — pending execution
The parties must specify authorised AI features and instructions, guest and staff data categories, purposes and duration, confidentiality, security, rights-request and impact-assessment assistance, incident escalation, audit support and deletion or return including backups. Identify provider roles, subprocessor approval and change notice, processing and support locations, transfer safeguards, retention, training settings and evidence. Optional voice and transcription need their own assessment. Separate-controller purposes must be identified rather than assumed to be covered by processor clauses. This review draft does not execute a DPA or authorise a provider.
See the AI Terms of Use, AI Privacy Notice and AI Acceptable Use Policy drafts. Legal and language review, real business identities and actual provider-contract evidence remain required before use.