Reference

hambabet Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open an account, sign in, verify your phone and use wallet options such as DANA or QRIS.

Account dataWallet referencesDevice choicesPolicy access
hambabet hambabet Privacy Policy for Your Account
CONTACT PATHS

Privacy Help for Account and Wallet Requests

A clear contact path helps when you want to ask about your personal data or correct an account detail. Use the support route connected to your hambabet account, and include the email or phone detail used during verification. This helps us locate the right record without asking you to send wallet passwords or full payment credentials.

Team online

Data access request

Ask us what account, device or support details are linked to your profile. We may ask for the verified phone step before releasing account-specific information.

Wallet reference check

If a DANA, OVO, GoPay or QRIS reference appears in a privacy query, share the date and reference fragment only; keep your wallet PIN and full credentials private.

Account correction

Send a correction request through the account support path when your phone, email or profile detail changes. We check the request against your verified account before updating records.

HANDLING DETAILS

How We Handle Your Personal Data

The Privacy Policy is practical: it explains why each data category is used and how you can contact us about it.

Account records

We use the details you submit during account opening and phone verification to create, locate and protect your profile. Keep your contact details current so policy requests reach the correct record.

Payment references

Our records can show a payment method or transaction reference, such as QRIS, bank transfer or virtual account. We use those references to match account activity without requesting your wallet PIN.

Cookies and sessions

Cookies and session signals help keep your sign-in connected and remember basic access choices. You can review browser cookie controls, though changing them may affect account access.

Device security

We may record device and browser signals linked to sign-in attempts. These checks help us spot unusual access and may lead to an extra phone verification step.

Retention choices

We keep personal data for the period needed to provide account access, resolve records and meet applicable legal duties. The policy explains retention by purpose rather than hiding it in general wording.

Change requests

You can contact us to ask for correction, access or clarification about your data. Include your verified account contact and a precise request so we can respond to the right person.

Privacy Policy Answers for hambabet

These Privacy Policy answers focus on the account steps Indonesian customers ask about most. They cover collection, wallet references, cookies, device checks and requests for access or correction. If your question is not listed, use the account support path and refer to the current policy wording.

It explains how we collect and use account, phone verification, device, cookie, wallet reference and support data. It also describes retention, security checks and ways to request access or correction.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We do not need your wallet PIN for a policy request.

Device and browser signals help us connect a sign-in to your account and identify unusual access. If a sign-in needs checking, we may ask for phone verification before account access.

You can send an access request through the account support path. Include the verified phone or email linked to your profile, and we may ask for an additional identity check.

Contact support with the specific account detail that needs correction. We compare the request with your verified account before changing records, including phone, email or profile information.

Yes. We explain how cookies and session signals support sign-in continuity and basic access choices. Your browser controls can change cookie use, but some account functions may then behave differently.

Access depends on local law and may differ by location or account circumstance. Before opening an account, read the current Privacy Policy and check the eligibility wording where local law permits.