Skip to content
18+ UK · Free social casino gamesFree virtual chips · No cash prizesPlayer Care

PRIVACY / YOUR INFORMATION

What stays in the guestbook.

How Chao Hostel uses account, game, Keyring and support records, with practical information controls.

A free account connects your requested features: games, saved choices and support. This notice explains the records behind those features. We do not sell personal information or run advertising or analytics trackers.

Why records are used.

Account details, game continuity and requested preferences are used to provide the service under our Terms, on the basis of performance of a contract. An account and synchronised play cannot work without those records.

Eligibility declarations, security checks, voluntary breaks and support correspondence support legitimate interests in protecting accounts, preventing abuse, operating an adult service and resolving issues. Data-protection duties may require processing on the basis of legal obligation. Reading or accepting this notice is not marketing consent.

Account access and eligibility.

Registration records a name, email, creation time and an Argon2id password hash. Plain-text passwords are not stored. Session credentials are hashed and expire after fourteen days. Account security shows coarse device names and last activity, and provides password and session controls.

The service records your UK-residency and age-18+ declarations and acceptance of the policy version. Guest players declare eligibility before playable guest access; the browser remembers it for thirty days. These declarations do not verify identity or location. The flow does not request a date of birth or identity document.

One-time email links expire after sixty minutes and recovery links after thirty minutes. Tokens are hashed; queued link content is encrypted until sent. Where transactional email is sent, the delivery provider receives the recipient and message. These messages are not marketing.

Game continuity and saved choices.

Account play records fictional-chip balances, round identifiers, outcomes, bonus progress, preferences and credit activity. These records support a shared balance and recovery of an interrupted request. A public recent-award feed contains game names and fictional-chip amounts, with no player name, email, account identifier or private round detail.

Favourites, ordered lists, up to twelve recent visits with timestamps, avatar and frame choices, comfort settings and saved collection preferences belong to the account. The personal Keyring stores up to six game identifiers, their order and private notes of up to 100 characters, with a revision and update time. Notes are not published. Earlier compatible profile, game-save and private planning records may also be retained with the account.

Guest slot visits use a random identifier and server-held balance, rounds and bonus state for seven days. The latest 120 guest activity entries are retained. Local guest favourites and device preferences remain in the browser. Preview demonstrations do not create account results or use credits.

A shared collection has limited contents.

If you publish a collection through an available sharing control, the public link contains the chosen title, selected games, avatar and frame. It does not include account identity, email, credit balance, Keyring notes or private play records. Anyone with the link can view it.

Unpublishing removes access through that link; publishing later creates a new link. Shared pages request no indexing and are omitted from the sitemap. Copies saved by other people are outside these controls.

A conversation with reception.

A support request stores its reply email, topic, message, reference, timestamps, status and subsequent messages. Signed-in requests are linked to the account. A guest request uses a private browser receipt lasting ninety days; knowing a reference alone is not enough to read it.

Keep passwords, payment details, identity documents and unnecessary sensitive information out of requests. A report-preparation tool formats text in the page and copies it only when you choose; it does not submit a request automatically.

Notification queues retain the request reference, delivery destination, status and retry count. Support notifications contain the reference rather than the message body. A saved request is not proof of external email delivery.

Cookies, security and service providers.

First-party essential cookies keep sign-in, request protection, guest eligibility and private support access working. Requested browser preferences are described in the Cookie Policy. Fonts and game assets are served from this site. No payment service, advertising network or analytics script is connected.

Hosting systems may log URLs, timestamps, browser details and IP addresses for operation and security. Rate limits use short-lived hashed keys. Application errors retain a random reference, route template, status and time, limited to 1,000 records and thirty days, without request contents. Administrator action records keep account ID, action and target reference for 180 days; deletion removes the actor association. Security measures reduce risk but cannot promise perfect protection.

Retention and deleting an account.

Account and game records remain while an account is active. Account privacy provides a password-protected download and permanent deletion. Deletion removes linked sessions, credits, progress, Keyring notes, saved collections and account-linked support messages. Only the deleted account number and deletion date are retained for ninety days to prevent accidental restoration.

Open support requests remain while being handled. Closed ordinary requests are retained for 180 days; closed privacy requests for one year. Guest receipts expire after ninety days. Successful notification entries are removed after thirty days; pending or failed entries remain with the request for review.

Guest visits expire after seven days. Adult declarations expire after thirty days unless a longer selected browser break applies. Relevant account operations and retention jobs remove expired sessions, limits, guest visits, support records and security links. Recovery backups must be restricted to thirty days, and deleted accounts must not be reactivated during restoration.

Access, correction and other requests.

Depending on the circumstances, you may request access, correction, erasure, restriction or portability and object to processing based on legitimate interests. We do not send marketing messages or make solely automated decisions with legal or similarly significant effects about you.

Use Contact for a privacy request, including when sign-in is unavailable. We normally respond within one month and explain any proportionate identity check, clarification or lawful extension. The account export is optional and does not limit an access request.

You can complain directly to the Information Commissioner’s Office about use of your information. You do not need to contact us first. Clearing browser storage is different from deleting account records; choose the control that matches the change you want.

Updated 15 October 2026

Use your privacy controls.

Download your account records or delete your account. You can also send a privacy request, including without signing in.

You may complain to the Information Commissioner’s Office. You do not have to contact us first.

Imaginary chips. Clear boundaries.

No purchases, cash prizes or redemption. Every chip belongs to the fiction.

One recorded round at a time.

Return to an interrupted game to recover its recorded result without another charge.

Your room, your choices.

Private keys, useful account controls and a pause whenever you need one.