A fictional hotel collection · local demo stays · no real reservation or payment. About this demo

Privacy · demo policy

Your details, clearly explained.

A straightforward guide to the data used by this demonstration.

Local demo data

Saved properties, collection notes, guest details, enquiry drafts, profile preferences and demo stays may be stored in your browser under the Canalure Stays namespace. They are not sent to a hotel or a remote account. Browser restrictions can prevent persistence.

Use fictional or non-sensitive details. Local data is inspectable by anyone with access to the browser profile. This template provides no encryption or secure authentication.

Optional real API tools

When you explicitly submit an authorized AI request, the displayed prompt and reviewed sample context go to Smart Routing. Text submitted for speech goes to Text to Speech. An address submitted for validation goes to Email Validator. Review each tool’s inputs before sending.

The public preview is token-free. Personalized downloads contain account-owned development configuration. Frontend credentials are inspectable, share the account’s quotas and do not create a secure production boundary.

Analytics and assets

No analytics, remote image hotlinks or external font requests are included. Optional AI calls use the documented platform endpoints, and generated speech plays the returned remote audio URL.

Managing local records

Edit or cancel individual demo stays from My stays. For a full local reset, use the reset control below. It affects only Canalure demo data and theme preferences, never unrelated site storage.

Reset requires an explicit confirmation in the completed demo.

For a real production service

Replace browser-local records with a secure backend, appropriate access control, verified hotel integrations and your own reviewed privacy policy before collecting real guest information.

Illustrative policy for this fictional demo · 11 November 2026.