Reference

Privacy Policy For bonsai55 Accounts

The bonsai55 Privacy Policy explains how we collect, use and protect details connected with your account, wallet checks and lobby access.

Account dataCookie choicesPayment recordsAccess requests
bonsai55 Privacy Policy For bonsai55 Accounts
HELP WITH PRIVACY

Get Clear Answers About Your Data

A direct support route helps when you want to understand a record rather than guess what it means.

Account support chat Ask about personal data held against your account, a phone verification record or a…
Payment privacy request For DANA, OVO, GoPay or QRIS records, send the transaction date, payment reference and…
Access request route If you want a copy, correction or removal request considered, use the contact route…
DATA HANDLING

What We Do With Account Details

Privacy choices should be understandable at the point where you use them. We separate account details from payment status where possible, limit access to operational needs and use…

Account records

We use your registered contact details, phone verification result and sign-in history to provide account access and respond to account…

Payment references

A QRIS, bank transfer or virtual account entry can include a reference, amount, time and status needed to reconcile your…

Cookies and devices

Cookies and similar device signals help keep your session connected, remember basic choices and detect repeated failed access.

Security controls

We may record sign-in time, browser type, device signals and failed verification attempts to protect an account.

Retention periods

We keep account, support and payment records only for as long as needed for the stated purpose, security checks, dispute…

Changes and requests

You can ask us to correct inaccurate contact details, explain a stored record or consider deletion through account support.

Privacy Policy Answers For Your Account

These answers focus on the questions we expect you to ask before opening or using an account. They cover the data connected with login, wallet status, cookies, payment receipts and account changes. If your situation is different, contact us through the account support path with only the details needed to identify the request. Where access or eligibility is discussed, it depends on local law.

It covers account details, phone verification, sign-in and device records, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It explains why we use each category, how long records may remain and how to contact us.

Phone verification helps connect account access with the contact detail you provided and helps us assess requests about stored data. We may use the verification result when you ask for a correction, copy or account change, but we do not ask for your wallet PIN.

It covers payment references that reach us, such as a QRIS reference, DANA status, transfer time or virtual account result. It does not give us your wallet password or PIN. Wallet credentials remain with the relevant payment provider, and you should not send them to support.

We use cookies and device signals to keep your session connected, remember basic choices and identify repeated failed access. You can restrict cookies in your browser settings, although the account path may ask you to sign in again or may not work fully.

Use the account support route and describe whether you want a copy, correction or deletion request considered. Include your registered contact detail and the record date when known. We verify ownership first, then explain the available action and any reason a record must remain.

We retain records for the time needed to provide account access, resolve support or payment disputes, protect security or meet a legal duty. After that purpose ends, we remove, anonymise or restrict the record where appropriate, subject to the rules that apply to your request.

Yes. Use the support chat or contact route attached to your account and state the privacy question clearly. You can mention Indonesia, Yogyakarta or the payment reference involved, but avoid passwords and wallet credentials. We handle access and eligibility where local law permits.