Reference

Open onebet303 Privacy Policy for wallet clarity

Our onebet303 Privacy Policy explains what we collect when you open an account, complete phone verification, sign in from a mobile browser, or check DANA and QRIS wallet…

Account data explainedWallet records coveredPrivacy requests welcome
onebet303 Open onebet303 Privacy Policy for wallet clarity
CONTACT ROUTES

Use the support path for privacy requests

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

Account access Use the support link beside the sign-in path when you need a copy of…
Wallet reference For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, send the transaction…
Correction request Tell us which profile field is incorrect and what it should say.
CONTROLLED HANDLING

See how we handle your account data

We keep the Privacy Policy practical by linking each data use to an account action you recognise, from opening an account to checking a wallet reference.

Account records

When you open an account, we use your submitted contact details and phone verification result to create the correct profile.

Cookies and devices

Cookies can keep a mobile browser connected to the correct sign-in session and remember relevant page choices.

Security checks

We use sign-in activity, device signals, and account changes to identify unusual access.

Retention period

We retain account and payment references only for the period needed for account administration, security checks, dispute handling, and legal…

Your choices

You can ask what personal details we hold, request a correction, or ask whether deletion is available for a particular…

Request changes

Send a privacy request through the support path and include your account identifier, the requested action, and a safe contact…

Find Privacy Policy answers before opening access

These Privacy Policy answers focus on the questions you may have before creating an account from Indonesia. We explain the practical steps for account data, cookies, phone checks, wallet references, and correction requests, while access remains subject to local law. If your situation is not covered, use the support path with the smallest useful set of details.

It covers account details, phone verification, sign-in activity, device signals, cookies, payment references, retention, security checks, and the ways you can request access or correction of eligible personal data.

Phone verification helps connect an account to the correct contact route and supports account security. We record the verification result and may use it when checking a request to change profile or wallet details.

Yes. The policy covers payment references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer, and virtual account requests, without requiring your wallet password or security code.

Use the support link beside account access, state that you want an account-data copy, and provide your account identifier plus a safe contact route. We may complete an identity check before responding.

Yes, you can identify the incorrect field and provide the replacement detail through support. We may verify the account first, particularly when the request changes your phone number, email, or wallet reference.

Cookies can maintain your mobile browser session and remember page settings. Clearing them may sign you out or trigger another account check, but it does not automatically erase records held for security or legal needs.

The Privacy Policy is available for you to read, while account access and certain data requests depend on local law. We apply the described process where local law permits and explain any restriction through support.