Reference

Privacy Policy For Your bumi303 Account

Our Privacy Policy explains how bumi303 handles the account, device and wallet details you provide before you enter the lobby.

Account clarityWallet recordsDevice choicesContact access
bumi303 Privacy Policy For Your bumi303 Account
PRIVACY CONTACT ROUTES

Get Privacy Help Before Account Access

A clear contact path matters when a name, phone number or wallet reference needs attention. Start with the privacy contact route shown on our website and include the account phone number only through that secure channel. We may ask for an account step, such as phone verification, before discussing personal records. If your request concerns a DANA or QRIS status, include the relevant reference without sending a wallet password or one-time code.

Team online

Privacy request

Use our published support contact to ask what personal data we hold, why it is used or whether a record needs correction. We will ask for enough account detail to identify your request without requesting your wallet password.

Account check

When a request involves login records or phone details, we may confirm ownership through the phone verification step linked to your account. This helps us avoid disclosing personal data to someone using an unverified device.

Wallet query

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account references, send the transaction identifier through the stated contact route. We use it to trace status without asking for your wallet PIN or one-time code.

DATA HANDLING LENS

How We Handle Device And Wallet Data

Privacy choices work best when you can see the practical reason behind each record. We separate account access data from payment references, use device signals to spot unusual sign-ins and keep cookie…

Account records

We may store your phone number, verification result, sign-in time and account changes to operate access and respond to account requests. We use these records for the account they relate to, not as a reason to request unrelated personal details.

Device signals

Your browser or phone may provide device type, session details and security signals when you sign in. We use these details to recognise an unusual access pattern and may ask you to repeat phone verification.

Cookies

Cookies can keep a session active, remember a setting or help us understand whether a page loads correctly. You can manage or clear them through your browser, though some account pages may then require another sign-in.

Wallet references

Payment records may show a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference and its status. We use that narrow record for reconciliation, account support and security checks rather than wallet access.

Retention timing

We retain each category while it supports account security, payment reconciliation, support handling or a legal requirement. When the relevant purpose ends, we remove, anonymise or restrict the record according to our internal process.

Your requests

You can ask us to access, correct or delete personal data through the published privacy contact route. We may verify your account first, and the outcome can depend on local law or a record we must retain.

Privacy Policy Questions For bumi303

These Privacy Policy answers cover the account questions we expect you to ask before opening access. They explain the records connected with phone verification, mobile browsing and Indonesian wallet references without replacing the full policy text. If your case involves a specific DANA, QRIS or login record, use the privacy contact route and share only the details needed to locate that record.

The Privacy Policy covers personal data used for account opening, phone verification, sign-in, support, cookies, device security and payment reconciliation. It also explains retention and requests for access or correction. Account access depends on local law, so check the policy before submitting your details.

Yes. The Privacy Policy covers payment references and status records connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account routes. We use those references to reconcile an account request, not to access your external wallet.

Phone verification helps us confirm that the person requesting account access or a privacy change controls the registered phone number. It can also support an unusual sign-in check. We will not ask you to share a wallet PIN or one-time code through support.

The Privacy Policy describes browser type, phone or device details, session records and security signals created during access. These details help us identify an unusual session and keep account records accurate when you move between a mobile browser and desktop.

Use the privacy contact route published on our website and state which account record needs correction. Include your registered phone number only through that route. We may verify ownership before changing the record, and the result can depend on local law.

We keep records for the period needed for account security, payment reconciliation, support handling or a legal requirement. After that purpose ends, we remove, anonymise or restrict the record under our retention process. Some transaction references may therefore remain longer than session data.

You can request access to personal data connected with your account through the stated privacy contact route. We may confirm your identity using the phone verification step, then explain the records we can provide and any restriction required by local law.