Reference

hut123 Privacy Policy For Your Account

hut123 Privacy Policy explains what we collect when you open an account, use Live Baccarat Table, or check DANA and QRIS status, and why each detail is needed.

Clear data purposesWallet record contextAccount access requestsCookie choices
hut123 hut123 Privacy Policy For Your Account
CONTACT ROUTES

Three Ways To Ask About Privacy

A clear contact route helps when a data question is tied to an account step. Start from the account help path and include the phone number on your hut123 account, the relevant date, and the type of request. If your question concerns a DANA receipt, QRIS reference, or sign-in record, we can direct it to the right handling queue without asking you to post private details in a public message.

Team online

Account help path

Use the signed-in account help path for an access, correction, or deletion request. Include your account phone number so we can match the request safely before discussing personal records.

Cashier record question

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, send the payment reference through account support. We use the reference to locate the relevant transaction detail.

Sign-in concern

If a device, phone verification, or login event looks unfamiliar, contact account support from the account help path. We may ask for a verification step before changing access details.

HANDLING DETAILS

Six Practical Privacy Commitments

Privacy work is part of each account action, from phone verification to a request about an old wallet record.

Data we collect

We collect account details you submit, phone verification results, sign-in events, device signals, support messages, and payment references. We do not need the contents of your private wallet account to match a DANA or QRIS reference.

Why we use it

We use personal details to create and protect your account, verify requested changes, connect a cashier reference, answer support questions, detect suspicious access, and meet duties that apply where local law permits.

Cookies on your device

Cookies can remember a session, preserve a selected setting, and help us understand sign-in errors. You can manage cookies in your browser settings, although turning some off may require another login step.

Account protection

Phone verification is used before account access and sensitive changes. If a new device or unusual sign-in needs checking, we may pause the requested change until you complete the account verification step.

How long records stay

We retain records for as long as needed for the stated purpose, support resolution, security checks, or a legal duty. When a record no longer has a valid purpose, our process can remove or de-identify it.

Changes and questions

Ask for a copy, correction, or eligible deletion through account support. Tell us which record you mean, such as a phone detail or payment reference, and we will check your identity before responding.

Privacy Policy Questions About hut123

These Privacy Policy answers focus on the searches we hear around account access, device records, cookies, and local wallet references. If your question concerns a specific account event, include its date and reference through the account help path. We will use the details needed to locate the matter and avoid asking you to share private credentials.

The hut123 Privacy Policy covers account details, phone verification, sign-in and device events, cookies, support messages, and payment references. It explains why we use each category, how long records may stay, and how you can request access or correction where local law permits.

We use a DANA or QRIS reference to match a cashier request with your account, check a receipt question, and help resolve a status issue. We do not need your private wallet password. Send the reference through account support rather than a public message.

Yes. Use the signed-in account help path and ask for a copy of the records linked to your phone number. We may verify your identity first, then explain which records can be provided and whether any legal retention rule limits the request.

Tell account support which detail is wrong, such as a phone number or contact record, and provide the corrected value through the protected account route. We check the request before making a change so an unfamiliar person cannot alter your account.

Yes. Cookies can keep a sign-in session active, remember a setting, and help identify device or login errors. You can adjust them in your browser. If you disable a cookie needed for access, the site may ask you to sign in again.

Retention depends on why the record exists, whether a support or security matter remains open, and any legal duty that applies. A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference may stay while that purpose remains valid.

You can submit a deletion request through account support and identify the relevant record. We check your identity and explain the result. Some account, security, or payment records may need to remain when a legal duty or unresolved matter applies.