Skip to content
ULTRAHOSPITALITY.AIGuest module

Ultra Guest

Data map

Each category of personal data on the platform, its purpose, default retention (tied to the live retention engine), deletion behavior, and whether it may be processed outside the EEA.

CategoryPurposeRoleDefault retentionDeletion / anonymizationProcessed outside the EEA?Implementation reference
Guest & session dataIdentify the guest, run the device session, and personalise the stay.ProcessorHidden from the hotel after 1095 days if the hotel switches this on; Ultra keeps a protected copy. Deleted only when the guest asks. (guest_stay)Hidden from the hotel after 1095 days if the hotel switches this on; Ultra keeps a protected copy. Deleted only when the guest asks. Session tokens expire on inactivity.Yesprivacy.py _erase_subject / guest_stay retention_policy
Stay dataMatch a guest to a reservation and tailor in-stay offers and fulfillment.ProcessorHidden from the hotel after 1095 days if the hotel switches this on; Ultra keeps a protected copy. Deleted only when the guest asks. (guest_stay)Hidden from the hotel after 1095 days if the hotel switches this on; Ultra keeps a protected copy. Deleted only when the guest asks.Yesprivacy.py guest_stay retention_policy
Order & cart dataProcess bookings and purchases of ancillary offerings and record acceptance.ProcessorRetained for tax and consumer-protection record-keeping (legal obligation).Contact name/email/notes erased on a guest erasure request; the financial record is retained where law requires.Yesprivacy.py _erase_subject (orders)
Concierge conversation dataRun the AI/staff concierge thread and book from the hotel's live offerings.ProcessorHidden from the hotel after 365 days if the hotel switches this on; Ultra keeps a protected copy. Deleted only when the guest asks. (conversation)Hidden from the hotel after 365 days if the hotel switches this on; Ultra keeps a protected copy. Deleted only when the guest asks.Yesprivacy.py conversation retention_policy; AI inference via Amazon Bedrock (AWS us-east-1)
Consent recordsRecord per-purpose consent and withdrawal to evidence the lawful basis.ProcessorAppend-only ledger retained as evidence of consent for the relationship's duration.Consent is set to 'withdrawn' on a guest erasure request; the audit event is retained.Yesconsent_state / consent_event (migration 0026)
Data-subject request recordsTrack access and erasure requests and their outcome.ProcessorRequest metadata retained as compliance evidence; never includes the export blob.Metadata retained to demonstrate the request was handled.Yesdsar_request (migration 0026)
Ledger & financial recordsMaintain the double-entry ledger, commission reconciliation, and payouts.ControllerRetained under legal-obligation (tax/accounting); NEVER swept by retention.Soft-deleted/retained on erasure; the financial record itself is preserved as required by law.Yeswallet_entry / ledger (retention_sweep excludes financial records)
Staff & admin dataManage hotel staff and platform-admin accounts and access.ControllerRetained for the duration of the account/relationship (independent-controller activity).Removed when the account is deprovisioned.Yesaccount / GoTrue identity (self-hosted on AWS)
Support, email & audit logsDeliver email, prevent abuse, and keep security/operational audit logs.ProcessorHidden from the hotel after 365 days if the hotel switches this on; Ultra keeps a protected copy. Deleted only when the guest asks. (email_outbox)email_outbox: Hidden from the hotel after 365 days if the hotel switches this on; Ultra keeps a protected copy. Deleted only when the guest asks. email_otp: Deleted after 30 days. stay_validation_attempt: Hidden from the hotel after 90 days if the hotel switches this on; Ultra keeps a protected copy. Deleted only when the guest asks. analytics_event: Hidden from the hotel after 730 days if the hotel switches this on; Ultra keeps a protected copy. Deleted only when the guest asks.Yesprivacy.py retention_sweep (email_outbox/email_otp/stay_validation_attempt/analytics_event)