Reference

akunbaru Privacy Policy For Your Account

akunbaru Privacy Policy explains how we handle the details connected with your account, device, login, and wallet status before you open the lobby.

Account detailsWallet recordsDevice accessPolicy requests
akunbaru akunbaru Privacy Policy For Your Account
PRIVACY HELP

Get Privacy Help Near Cashier Status

A clear contact path matters when your account record or wallet reference needs correction. Use the account help route for privacy questions, and include only the details needed for us to locate the record. We check requests against the account step involved, such as phone verification, login access, or a payment receipt.

Team online

Account access

If your phone verification or login record looks wrong, contact us through account help. Tell us the affected step and device type, but never send a password or one-time security code.

Wallet status

For a DANA, OVO, GoPay, or QRIS reference, share the receipt number and approximate time through the cashier support path. We use those details to locate the payment record without asking for your wallet password.

Privacy request

Ask us to access, correct, or remove eligible personal details through the same support route. We may request account verification first so a private record is not disclosed to the wrong person.

DATA CONTROL

Your Data Path From Login Onward

We keep our policy connected to the real account actions you take, rather than describing data in abstract terms.

Account creation

When you open an account, we handle the details needed to create access and complete phone verification. We do not need unrelated personal content for that step, and you can ask which account fields are held.

Device signals

A mobile browser or desktop session may provide device type, browser details, approximate login timing, and security events. These signals help us protect account access and investigate unusual sign-in activity.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account references can be recorded to match receipts with account activity. We use the reference for reconciliation and status checks, not for unrelated account profiling.

Cookies and storage

Cookies or similar browser storage can keep a session active, remember a security choice, or help us understand an access error. You can manage browser storage through your device settings, though some account steps may then need repeating.

Retention period

We retain account, security, and payment records while they support access, dispute handling, security checks, or legal duties. When those needs end, we remove the record or reduce it so it no longer identifies you where practical.

Changes and contact

You can request a copy, correction, or eligible deletion through account help. Include the account step involved, such as phone verification or QRIS status, and we may confirm your identity before making a change.

Privacy Policy Answers For akunbaru Accounts

These Privacy Policy answers address the account, device, payment, and access questions we hear most often. If your situation is different, contact us through account help with the smallest useful set of details.

The Privacy Policy covers account details, phone verification, device signals, cookies, login events, payment references, support requests, retention, and eligible requests to access, correct, or remove personal data.

We record a payment reference, receipt detail, or status signal from DANA or QRIS to match an account transaction and resolve a stalled cashier status. We do not ask for your wallet password.

Yes. The Privacy Policy covers references connected with OVO, GoPay, bank transfer, and virtual account steps when those details help us reconcile a receipt, check account ownership, or respond to support.

Use the account help route and request a copy of the personal data linked to your account. Tell us the relevant account step, and we may verify your phone or account details first.

Yes. Send a correction request through account help and identify the inaccurate field, such as a phone verification detail or payment reference. We check the request against the account before changing the record.

The Privacy Policy allows us to handle device type, browser details, login timing, and security events from a mobile or desktop session. These signals support account protection and access troubleshooting.

Yes. Account access and certain data requests depend on local law. Where local law permits, we follow the request process described here and explain when a legal or security reason limits a response.