Reference

hanabet Privacy Policy for Your Account

DANA and QRIS records, account details, device activity and support messages are covered in the hanabet Privacy Policy, so you can see what we collect and why.

Account dataWallet recordsCookie choicesAccess requests
hanabet hanabet Privacy Policy for Your Account
CONTACT ROUTES

Where To Ask About Account Data

A clear contact path helps when you need a Privacy Policy answer rather than a general account reply. Start from the support route connected to your account help area and include the email or phone detail linked to your profile. We use that account step to locate the correct record, while receipt and wallet questions can be matched with DANA, OVO, GoPay or QRIS status.

Team online

Account data request

Ask us to identify the personal data linked to your account through the support route shown after login. Include your registered contact detail, but never send a password or full wallet PIN.

Receipt and wallet query

For a Privacy Policy question about DANA, QRIS, OVO or GoPay records, share the transaction reference and date. We use those details to find the relevant receipt without asking for unnecessary account information.

Mobile access help

If the Privacy Policy page or an access request stalls on your phone, tell us the browser and device path you used. We can separate a display issue from an account-data request.

DATA PRACTICE

Six Controls Behind Your Account Data

We handle this policy area through practical account controls rather than broad promises. The same process covers information entered during registration, wallet references, device signals and messages sent to support.

What we collect

We may store your registration details, verification status, sign-in events and support messages. Activity connected with Andar Bahar, Rocket Crash or Football Betting can appear as account records when you use those areas.

Cookie choices

Cookies and similar browser storage help keep your session open and remember selected settings. You can clear them through your browser path, although clearing storage may require another account sign-in.

Account protection

We use account checks, session controls and verification details to reduce unauthorised access. Never place your password, wallet PIN or one-time verification code in a support message.

Retention timing

We keep each record only as long as it serves the purpose explained in this Privacy Policy, supports account safety or meets a legal need. After that point, we delete, restrict or anonymise it where appropriate.

Correction request

If your name, phone detail or other account data is wrong, contact us through account help and describe the correction. We may verify ownership before changing the stored record.

Who receives data

We limit access to people and service partners who need records for account operation, payment matching, safety or support. We do not ask you to provide unrelated personal details for a simple policy question.

Privacy Policy Questions Before Account Access

These Privacy Policy answers cover the searches we hear most often before an account is opened or checked. They explain the practical route for data requests, wallet records, cookies and account access. If your question is not listed, use the support path above and refer to the account detail you want us to locate.

It covers registration details, verification, sign-in activity, device signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account use.

We use the contact detail you provide to identify your account, complete the verification step before access and respond to a data request. We only use it for stated operational, safety or legal purposes.

Yes. The Privacy Policy covers references needed to match DANA or QRIS receipts with your account. Send the transaction reference and date through support, rather than sharing a wallet PIN.

You can ask through the account help route for the personal data linked to your profile. We may confirm your registered phone or email first so the response goes to the account holder.

Contact us with the incorrect name, phone detail or other field and explain the requested change. We may verify ownership before editing the record, and some records may need a retention reason.

Cookies and browser storage can keep your session and preferences available on your phone. You can clear them in browser settings, but doing so may sign you out or remove saved choices.

Yes. Account access, eligibility and certain data requests depend on local law or apply where local law permits. We will explain the available route when you contact support about your record.