Privacy

Last reviewed: 21 August 2026.

Operator and scope

This fictional demonstration is published by Tamaga, currently operated through BlueMelon. Privacy questions can be sent to talk@tamaga.systems.

Tamaga Hotel is not a real property. The public journey demonstrates hotel information, Room Fit, a conditional late-arrival request, accountable Host work and representation inspection without completing a reservation.

Information used by the guided demonstration

The guided journey uses check-in and checkout dates, adult and child counts, the selected room category and an expected arrival time. Every person counts toward occupancy. The Demo does not ask for names, children’s ages, relationships, email addresses, phone numbers, account credentials or payment details.

Synthetic records created

The system may create an opaque availability-query reference, a synthetic draft Commerce cart and booking snapshot, a stay-level late-arrival request, an Attention Item, an isolated demonstration scenario and append-only operational evidence. These records contain the fictional stay context and governed Promise evidence. They do not create a placed order, reservation, room allocation, visitor-owned guest profile, account, receipt, payment or external message.

Browser and server data

The current browser session must own its opaque query and scenario references. The application does not store the browser session identifier or IP address in scenario, request or Attention records. As with an ordinary website, hosting and security infrastructure may process request metadata such as IP address, user agent, requested path and timestamp in technical logs.

The browser may store the selected colour theme and analytics choices locally. Clearing this site’s browser storage removes those preferences.

Why the information is used

The limited stay context is used to evaluate room suitability separately from date inventory, preserve the expected-arrival condition, expose the resulting work to the Host view, enforce session isolation, prevent abuse and prove that the demonstration does not consume shared room availability.

Retention and reset

Availability-query contexts and signed demonstration scenarios have a fixed lifetime of no more than one hour. Reset or expiry immediately revokes their authority. Scenario-owned synthetic carts, requests, Attention Items and transition evidence are deleted after the separate 48-hour Demo retention window. Promise Cards, publication receipts and general governance history are not scenario data and are not removed by that purge.

Optional measurement

If a public counter is configured, basic aggregate measurement and its browser opt-out are described in Privacy choices below. Session replay, click maps, link tracking and form-interaction analysis require a separate browser opt-in and are limited to approved read-only Demo routes. Query-bearing workflow pages are excluded. Measurement data is processed by Yandex under its privacy terms and the retention settings of the separate Demo counter.

Your choices

You can reset the current demonstration, turn off optional analytics, clear this site’s browser storage or contact talk@tamaga.systems with a privacy question. Do not submit personal, medical, identity-document, payment-card or real reservation information anywhere in this fictional demonstration.

Fictional Guest Memory

Guest Memory is active only with five pre-seeded fictional CRM Contacts, one synthetic Orchard Room stay and two namespaced preference records. It receives no visitor data, creates no visitor profile and does not infer a preference from public requests or browsing.

Not part of this release

Live messaging, payment, real booking completion, live channel acquisition and AI processing are not active Hotel Demo capabilities.