Hotel Activity Agent privacy policy

Prepared 23 October 2026. Operated by ASTROBLASTER LTD. Privacy and support: michalcilekaps@gmail.com.

What we process

To provide the programme, personal plan and reception workflow, we process your chosen hotel, room label, stay dates, random stay identifier, selected activity IDs, reception messages/replies, request states and chronological interaction timestamps. Private credentials and server-side hashes control access. Room numbers and public hotel codes alone do not grant access to other guests. Use fictional details in the demonstration; do not send sensitive personal information.

Authorised reception staff can access their own hotel's cases. Hotel-scoped summaries use stay activations, saved plans and request interactions. These are not proof of attendance, confirmed bookings, all installations or people active now. We do not implement cross-app advertising tracking or sell data to data brokers.

Your device and optional features

A private stay authority is stored in device-only Keychain. A protected copy can prove ownership for deletion after the ordinary access session expires; it does not extend access to messages or other guest functions. Appearance choices and pending request drafts are stored locally; selected plan activity IDs are also saved on the server. Optional QR scanning uses the camera. Search is local. Voice and paid AI are disabled; no audio is uploaded.

Calendar export uses the system editor for the event you choose and does not read your private calendar. Reminders are local notifications. Saved Calendar events remain under your control in Calendar.

Retention

The approved target schedule is30days from demo stay activation and15minutes for application authentication-attempt records. Automatic enforcement of these targets is not enabled; stored demonstration records are not guaranteed to be automatically removed at those ages. Use confirmed own-stay deletion or contact us to request deletion. Unknown-age legacy records require manual review. Session expiry and signing out do not erase records. Non-identifying capacity counters may remain for their applicable day.

Deletion and privacy requests

In Your data, choose the saved stay and explicitly confirm deletion. The operation targets only that stay's plan, requests, replies/history, associated operational events, action caches and credentials. Other guests and hotels are unaffected. A short-lived deletion acknowledgement permits a safe retry after a lost network response; it contains no message text or room label and has a15-minute retry window. Expired acknowledgements may remain stored while automatic cleanup is disabled. Previously used invitation digests remain non-reusable anti-replay markers without a stay link.

If normal access expired, the device-held ownership proof can initiate deletion only; it cannot read or reopen the old stay. If the private proof was removed, contact michalcilekaps@gmail.com. We must verify ownership before acting; hotel/room alone is insufficient. Never email passwords or private access tokens. Support will explain verification and the specific scope before completing a request.

Hosting and recovery copies

Cloudflare provides hosting and storage. Its SQLite Durable Objects documentation describes point-in-time recovery of prior storage for up to 30 days. Removing active records does not instantly remove every historical recovery copy. Recovery copies are not used for ordinary hotel service. We will not reopen a pre-erasure restored dataset unless erased records can be excluded; otherwise a clean demonstration must be used.

The 15-minute application limit is not a promise that every Cloudflare infrastructure log disappears in 15 minutes. Provider operational/security metadata and recovery handling follow the applicable service settings and terms. The reviewed Worker has Logpush disabled and no tail consumers; an explicit Observability setting was not returned, so we do not claim that no provider logs exist. No EU-only or zero-retention claim is made.

Demonstration scope

This release includes synthetic hotels and sample programmes. All hotel names, venues, activity descriptions and schedules are original fictional examples. Requests do not reach a real hotel and do not create real bookings/payments. This is not an emergency channel.