Reference

Open han33 Privacy Policy Clearly

The han33 Privacy Policy explains what we collect, why we use it and how you can ask us to correct or remove eligible data.

Account dataWallet recordsCookie choicesAccess requests

Browse Our Lobby Read FAQ

Explore What Our Privacy Policy Covers

han33 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy sets out the data needed to create and protect your account, including your phone number, verification status, login events and support correspondence. We also record transaction references when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, so we can

1
match a receipt with the correct account and investigate a stalled wallet status. Device and browser details may help us detect unusual access, while cookies can remember selected settings. We use this material for account operation, fraud checks, payment reconciliation, support and legal duties where required.
2
Access depends on local law, and where local law permits, you may request a copy, correction or deletion of eligible personal data through our support route.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT OUR TEAM

Switch To The Right Privacy Contact

A clear contact path helps you deal with a privacy question without explaining your request repeatedly. Use the account support route when you need to confirm which phone number is attached to your profile, query a wallet record or ask how a device event was handled. Include the email or phone detail linked to your account, the relevant date and a short description. Do not send a password or full payment credentials. We use the details you provide to locate the request, respond through the available support channel and keep a record of the case.

Team online

Account privacy request

Ask our account support team to explain the personal data connected with your han33 profile. Include your registered phone number and request type, such as access, correction or deletion, but leave passwords and complete wallet credentials out of the message.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the transaction date, amount shown in your receipt and the payment rail used. We can compare the reference with account records without asking you to share a secret wallet PIN.

Security access concern

Tell us promptly when a login notification, device session or phone verification event does not look like yours. We may ask account questions before discussing the record, helping us protect your profile while we investigate the reported access.

HOW WE HANDLE DATA

Browse The Privacy Controls We Use

Privacy protection works through small account steps that you can recognise. We separate identity details from payment references where operationally possible, restrict account access by verification checks and use device signals to…

Data collection

We collect the details required for account access, including your phone number, verification result, login history and support messages. Payment references from DANA, QRIS, bank transfer or a virtual account help us match activity without treating a wallet PIN as account data.

Cookie settings

Cookies can keep a sign-in choice, remember a language setting and help us understand whether an account page loads correctly. Your browser controls these files. If you block them, some account or privacy-request steps may ask you to repeat a setting.

Account security

Phone verification is used before account access and may be followed by checks when a device or login pattern changes. We do not ask for your password in a support message. Report an unfamiliar session so we can review the account record with you.

Retention choices

We keep personal data for the time needed to operate the account, resolve a wallet or support issue, meet record duties or handle a dispute. When a retention reason ends, we delete, anonymise or securely restrict the relevant record where the law allows.

Correction request

If your phone number, contact detail or account name is inaccurate, contact support with the detail that needs changing. We may verify ownership first, then update the record or explain why a particular field must remain unchanged for account or payment reconciliation.

Data access request

You can ask what personal data we hold, how we use it and which request route applies. State that your message concerns the han33 Privacy Policy and include your registered contact detail so we can locate the correct account before responding.

Ask About han33 Privacy Policy

These Privacy Policy answers focus on the account questions you are most likely to have before opening han33. They explain the practical handling of identity details, wallet references, cookies, device events and requests. If your situation is not covered, use the support path with the smallest useful set of account details. Access depends on local law, and some requests may require an ownership check before we disclose or change a record.

It covers account details, phone verification, login and device events, cookies, support messages and transaction references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. It explains why we use each category, how long records may remain and how to request access or correction.

We use your phone number to create the account identity, complete the clear phone verification step and help protect later access. It also lets support locate the correct profile when you ask about a login or wallet record. We do not need your wallet PIN for this process.

Yes. The Privacy Policy covers transaction references linked to DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use those references to reconcile an account receipt or investigate a stalled status. Send only the date and visible reference details when contacting support.

Contact the account support route and state that you are making a Privacy Policy data request. Include your registered phone number, the account detail you want to see and your preferred response channel. We may verify account ownership before sharing records, and access depends on local law.

Yes, where local law permits. Send the incorrect phone, contact or profile detail with the replacement you want recorded. We may check ownership first and may retain a transaction reference when it is needed for payment reconciliation or a dispute, even after another field is corrected.

Cookies can remember a sign-in choice, selected language and certain page settings, while technical signals help us identify loading or access issues. You can manage cookies in your browser. Blocking them may mean repeating account steps or losing a stored preference during a later visit.

Use the security support route and provide the registered phone number, approximate login time and device detail shown to you. Do not send a password, wallet PIN or complete card credential. We use the report to investigate the session and may verify ownership before discussing account data.

Open han33 Privacy Policy Clearly

Switch To The Right Privacy Contact

Account privacy request

Wallet record question

Security access concern

Browse The Privacy Controls We Use

Data collection

Cookie settings

Account security

Retention choices

Correction request

Data access request

Ask About han33 Privacy Policy

01 What does the han33 Privacy Policy cover?

02 Why does han33 need my phone number?

03 Does the Privacy Policy cover DANA and QRIS records?

04 How can I request my han33 data?

05 Can I ask han33 to correct my account data?

06 How does han33 use cookies on my device?

07 How do I report an unfamiliar device login?

Related Pages