Privacy, clearly explained

Updated 15 October 2026. The public trip planner stores language and trip previews on this device. Hotel accounts, catalogues, suppliers, requests and operation history in v0.9 are stored on the server in the eXperyence database at Hostinger.

Accounts and sessions

Staff accounts use email and a protected password hash. Essential HttpOnly cookies identify staff sessions (8 hours) and guest sessions per hotel (7 days). Guest requests can be followed in the same browser while the session remains available. Clearing cookies removes access to that session, but does not delete requests held by the hotel. Access is limited by account and hotel; global administrators manage the platform.

Payments use Stripe only when explicitly enabled for an offer and configured by the operator. No advertising analytics or tracking pixels are included. Hosting may process technical logs. Do not enter sensitive information in descriptions. Activation links are confidential and expire after 24 hours.

Supplier access

Supplier accounts use a separate essential session cookie lasting 8 hours. Each account sees orders assigned to its supplier and can respond to availability. Operational notes are visible to hotel staff and platform administrators, not guests. Operational emails use Resend when configured. Payment records and encrypted backups are held on the server; backups require a separately protected key.

Pilot operation

The initial catalogue contains fictional examples. Requests are stored and handled by the hotel; they do not take payment or automatically confirm supplier availability. Contact your hotel administrator regarding account access or request data. Controller identification, contact details, retention periods and applicable rights procedures must be completed before wider commercial use.