Reference

Privacy Policy For Your hut55 Account

Our Privacy Policy explains what we collect when you open a hut55 account, sign in, verify your phone, or use DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record contextPhone access controlsIndonesia policy path
hut55 Privacy Policy For Your hut55 Account
CONTACT ROUTES

Get Privacy Policy Help Through Support

A direct support path helps you resolve a Privacy Policy question without repeating your account story across unrelated channels. Tell us whether your request concerns a phone record, cookie choice, wallet reference, sign-in event, or correction to account details. Include the email or phone linked to your account, but never send a password or wallet PIN. Our support team can explain the next verification step before discussing personal data, and you can ask for a status check if your request concerns DANA, OVO, GoPay or QRIS.

Team online

Account data request

Ask support for the personal data connected with your hut55 account. We may confirm your phone or account detail first, then explain the available access route and any limits that depend on local law.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference appears unclear, share the date and reference shown in your account. We use that detail to locate the status without asking you to send a wallet PIN.

Correction or deletion

You can contact us when an account detail needs correction or when you want to ask about deletion. We explain what can change, what must remain for security or legal duties, and the next account check.

DATA PRACTICE

Six Practical Privacy Policy Commitments

The way we handle Privacy Policy requests follows the same account steps you already know: sign in, confirm the account detail, describe the request, and wait for a…

Purpose-based collection

We collect account details because they support a stated task, such as phone verification, sign-in protection, support handling, or matching…

Cookie choices

Cookies can keep your session active and remember the page state needed for account access.

Account security

Phone verification and sign-in checks help us distinguish your account activity from an unusual device event.

Retention decisions

We retain records for account operation, security checks, unresolved disputes, or legal duties, then remove or de-identify them when that…

Request tracking

When you ask for access, correction, or deletion, we record the request, the account check, and the response so the…

Policy contact

Support is the starting point for Privacy Policy questions about your account, cookies, device activity, or payment references.

Privacy Policy Questions About hut55

These Privacy Policy answers address the account situations you are most likely to meet before opening an account or while checking a wallet reference. We keep the route practical: identify the account, describe the data question, and use support for the next step. The policy applies to browser access on your phone or computer, including sessions that open casino pages or payment screens. Eligibility and access depend on local law.

It covers account details, phone verification, sign-in and device signals, cookies, support messages, and payment references from DANA, OVO, GoPay or QRIS. It also explains purposes, retention, security checks, your request options, and the local-law conditions that may affect access.

Contact support and describe the data you want to access, such as account details, sign-in events, cookie use, or a QRIS reference. Include the linked phone or email, complete the account check we request, and do not send a password or wallet PIN.

Yes. The Privacy Policy covers payment references and status records connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity. These records help match an account action and resolve a status question; they do not include your wallet PIN.

Yes, you can ask support to correct an inaccurate account detail. Tell us which field is wrong and provide the account contact needed for verification. We explain whether the change is possible and whether a record must remain for security or legal duties.

Cookies may keep your sign-in session active and preserve the account state needed while you move between policy, wallet, and lobby pages. You can restrict cookies in your browser, but that may require another sign-in or affect the request process.

We keep data while it serves account operation, security, a dispute, or a legal duty. Temporary session data may end sooner than a payment reference. When the relevant purpose ends, we remove or de-identify records where local law permits.

You can ask support about deletion and explain which data you want removed. We first confirm the account, then identify records that can be deleted and records that must remain for security, dispute handling, or legal duties. The outcome depends on local law.