Reference

bonsai33 Privacy Policy For Your Account

The bonsai33 Privacy Policy explains how we collect, use and protect the details you provide when opening an account, checking wallet status or entering the lobby.

Account clarityWallet data contextPhone access checksPolicy contact route
bonsai33 bonsai33 Privacy Policy For Your Account
CONTACT FOR PRIVACY

Where To Ask About Your Data

A clear contact route helps you act on the Privacy Policy instead of searching through unrelated account screens.

Account privacy request Send a request through the account support path when you want to ask what…
Wallet record question If a DANA, OVO, GoPay or QRIS status looks unfamiliar, share the visible reference…
Access correction Use the same support route when your phone number, contact detail or account access…
DATA HANDLING DETAILS

What We Do With Account Data

Privacy decisions affect the account from the first phone check through later wallet status checks, so our policy separates necessary records from optional browsing signals.

Account details

We may hold the name, contact detail and phone verification result you submit during account creation.

Payment status

A wallet or bank record can show a reference, amount, time and status needed to match activity to your account.

Cookies and devices

Cookies can retain a session choice, while device signals can help detect repeated failed access or an unusual sign-in.

Account security

We use sign-in checks, account history and verification prompts to reduce unauthorised access. Never share your password or verification code.

Retention decisions

We retain records only as long as needed for account operation, payment reconciliation, security checks and legal duties that apply…

Your request

You can ask for a copy, correction, clarification or deletion of personal data through the account support path.

Privacy Policy Answers For bonsai33

These Privacy Policy answers address the account and payment questions we expect from Indonesian customers before they open an account. They explain the practical data path without replacing the full policy text. If your situation involves a disputed receipt, changed phone or restricted access, use the account support path with the relevant reference.

It covers account details, phone verification, sign-in events, device signals, cookies and payment status used on our service. It also explains how we respond to requests about access, correction, clarification and deletion, subject to legal duties that apply where local law permits.

Phone verification connects the person opening the account with the correct account record and helps protect later access. It can also support a privacy request when we need to confirm that the person asking about DANA, QRIS or account data is you.

Our policy covers the account-side payment details needed to match a DANA or QRIS status, such as a reference, time and result. DANA and QRIS also hold data in their own systems, so their separate privacy terms apply to information they collect directly.

Open the account support path and ask for a personal-data copy, explaining which account detail or period you need. We may request phone or account verification before replying. The response can be limited where disclosure would affect security or a legal obligation.

Yes, send the correction through support with the account identifier and the relevant receipt or reference. We check the request before changing private data. If the record belongs to OVO, GoPay, a bank or another provider, that provider may need to correct its own system.

Retention depends on why the record exists. Account, security and payment records may be kept for operation, reconciliation, dispute handling or legal duties. When those reasons end, we follow the deletion or de-identification process that applies where local law permits.

You can request deletion through the account support path, and we assess it under the Privacy Policy and applicable law. Some records may need to remain temporarily for security, payment reconciliation or an unresolved request. We explain the outcome and any relevant reason.