Reference

babahoki Privacy Policy for Your Account

Our Privacy Policy explains how babahoki handles the details you provide when opening an account, signing in, checking wallet status or contacting support.

Account dataWallet recordsCookie choicesSupport requests
babahoki babahoki Privacy Policy for Your Account
CONTACT THE TEAM

Privacy Help Beside Your Account

A clear contact route matters when you want a copy, correction or explanation of personal data. We ask you to contact us from the account area where possible, because that lets us match the request to the right account without exposing private details to the wrong person. Your message can also mention a wallet status or device issue connected with the request.

Team online

Account support

Send a privacy request through the signed-in account path and include the phone number linked to your profile. We use that account step to check identity before discussing stored details.

Wallet records

For a DANA, OVO, GoPay or QRIS receipt, share the transaction reference and date rather than a full wallet password or one-time code. We can then trace the relevant record.

Device access

If a mobile or desktop session looks unfamiliar, tell us the device path, browser and approximate sign-in time. We can review the account security event without asking for your password.

HANDLING YOUR DATA

Six Practical Privacy Commitments

We handle this policy area through ordinary account operations rather than broad promises. Phone verification is used before account access, wallet records are connected to the relevant transaction status, and device signals…

Account details

We collect details needed to open and maintain your account, such as contact data and verification status. We use them for sign-in, account recovery, support handling and access checks where local law permits.

Payment matching

When you use DANA, OVO, GoPay or QRIS, we keep transaction references and status details needed to match wallet activity with your account. We do not need your wallet password to process that check.

Cookie controls

Cookies can keep your sign-in path, language choice and selected page settings available between visits. You can adjust cookie storage in your browser, although blocking some cookies may interrupt account access.

Account security

We may record device type, browser details, session timing and sign-in events to investigate unusual access. Never send us your password or one-time code when asking for privacy assistance.

Retention period

We retain personal and transaction records while they support account operation, payment checks, security work or legal duties. When a record is no longer needed, we remove it or separate it from direct account identity.

Change requests

You can ask us to correct inaccurate account details, explain a data use or provide an accessible copy. Submit the request through account support, and we may verify ownership before replying.

Privacy Policy Questions From Indonesia

These answers address the questions we expect you to have before opening an account or checking your existing records. They cover the babahoki Privacy Policy, local wallet references, cookies, device access and the practical route for asking us to change or explain your data.

The babahoki Privacy Policy covers account details, phone verification, device and session data, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps connect the account to the correct person before access and support changes. It also helps us investigate an unfamiliar sign-in. Access and eligibility depend on local law.

Yes. The Privacy Policy covers the transaction reference, selected rail and status needed to match DANA or QRIS activity with your account. Do not send us a wallet password or one-time code.

We use cookies to support sign-in continuity, saved preferences and basic page measurement. You can manage them through your browser settings, but blocking required cookies may affect the mobile or desktop account path.

You can request an accessible copy, correction or explanation through the signed-in account support route. Include the phone number linked to your profile, and we may verify account ownership before sharing details.

We keep account, payment and security records while they are needed for account operation, transaction checks, support handling or legal duties. We then remove or anonymise them through our retention process.

Contact account support promptly and mention the device type, browser and approximate sign-in time. Do not share your password or one-time code. We can review the session and help secure the account path.