Reference

Open the bonsai33 Privacy Policy

The bonsai33 Privacy Policy explains what we collect when you create an account, verify your phone and move between the lobby and wallet area.

Account recordsCookie choicesWallet privacy
bonsai33 Open the bonsai33 Privacy Policy
CONTACT THE TEAM

Choose a clear privacy support path

A direct support route helps when a privacy question appears during login, phone verification or a wallet status check. Tell us which account step needs attention and include only the details needed to locate your record. From Medan or elsewhere in Indonesia, use the support contact displayed in your account area so we can connect the request with the correct privacy case.

Team online

Account access

If phone verification blocks your account, contact support through the account path and ask which personal record is being checked before access can continue.

Wallet status

For DANA, OVO, GoPay or QRIS questions, share the payment reference shown in your account rather than sending extra personal details.

Privacy request

Ask about a copy, correction or removal request through the same support route. We may confirm account ownership before discussing private records.

DATA HANDLING

Browse the controls behind this policy

We keep the Privacy Policy practical by linking each data use to a visible account action: phone verification, wallet status, lobby access or support contact.

Account details

We use your account details to identify the correct account, complete the clear phone verification step and respond to a…

Payment references

DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI references can be connected to payment-status checks.

Cookie controls

Cookies and similar device signals help remember your session and protect the path from login to the lobby.

Account security

Phone verification and session checks help us distinguish your account from an unfamiliar device.

Retention approach

We retain account, payment-status and support records only for the period needed for service operation, security, dispute handling or legal…

Change requests

You can ask us to correct relevant account details or explain the records held about you.

Find answers about your Privacy Policy

These answers focus on the questions we expect you to ask before opening an account or checking wallet activity. If your case involves a particular device, payment reference or phone-verification step, include that context in your support request so we can address the relevant Privacy Policy section.

It covers account details, phone verification, device and session signals, cookies, payment references, support records, retention and requests to access, correct or remove relevant personal data.

We use your phone number for account identification and the clear verification step before account access. This helps connect a privacy request or wallet-status question to the correct account.

Yes. The Privacy Policy explains how references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may support payment-status checks and account security.

Use the support contact shown in your account area and ask for a Privacy Policy data request. We may confirm ownership first, then explain which records can be provided.

Yes. Send a correction request through the account support path and identify the record that needs changing. We may ask for phone verification before applying or discussing the update.

Cookies can remember a session and support the mobile path from login to the lobby. Browser settings may restrict them, but limiting cookies can require extra verification during account access.

We keep records for service operation, security, support, dispute handling or legal duties when needed. The Privacy Policy explains the retention approach, and you can ask support about a specific record.