Reference

Privacy Policy For oke128 Accounts

oke128 Privacy Policy explains what we collect when you open an account, use the mobile lobby, or check DANA and QRIS status.

Account dataCookie choicesWallet recordsAccess requests
Explore Our Lobby Read FAQ
oke128 Privacy Policy For oke128 Accounts
HELP WITH RECORDS

Policy Help Beside Account Support

A clear support path matters when a Privacy Policy question involves your own account.

Account questions Use the account help path when you need to know which profile details we hold or why phone verification is connected to account access. Include your registered contact detail so we can distinguish your request from another account without asking for a password.
Wallet references For a Privacy Policy question about DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, send the receipt reference and date through support. We can check the payment record while keeping wallet passwords, PINs, and full credentials out of the request.
Change requests Ask us to correct account data, explain a cookie choice, or clarify retention through the same support route beside the cashier path. We may request a simple identity check before discussing private records, so your account details are not disclosed to another person.
SIX DATA CONTROLS

What We Do With Your Account Data

Privacy Policy controls are part of the account flow, not a separate promise hidden from you.

Account details

When you open an account, we collect the contact details and verification data needed to create and protect that profile. Phone verification can confirm that an access request belongs to you; we do not treat an unverified contact as proof of identity.

Device sessions

A phone browser and a desktop browser can produce separate session, language, browser, and device records. We use these signals to identify unusual sign-in activity and help restore the correct account path, rather than to read unrelated files on your device.

Cookies

Cookies help remember session status, language choices, and consent preferences on the browser you use. You can clear or restrict them through browser controls, although doing so may require another sign-in and may affect how your Privacy Policy choices are remembered.

Payment data

We keep payment references, amounts, status results, and receipt details needed to match an account transaction. For DANA, OVO, GoPay, and QRIS, we rely on the reference supplied by the payment flow and do not ask for your wallet PIN.

Security steps

Account protection can include phone verification, session checks, and review of unusual access patterns. If you change devices or your login stalls, support may ask for account details that confirm ownership; never send a password, wallet PIN, or one-time code.

Retention requests

We keep each category only while it serves account operation, security, dispute handling, or a legal requirement. You may ask what remains, why it remains, or whether a correction or removal request is available where local law permits.

Privacy Policy Questions About oke128

These Privacy Policy answers address the questions we hear before an account is opened or when a sign-in, cookie, or wallet record needs clarification. They are written for Indonesian account holders and point you toward the account support path when a question depends on your own records. Access depends on local law, and a request may need an ownership check before we discuss private data.

The oke128 Privacy Policy covers account details, phone verification, device sessions, cookies, support messages, and payment references. It explains why we use each category, how we protect it, how long we keep it, and how you can ask about access or correction where local law permits.

We may collect your registered contact details, verification results, session and device signals, cookie choices, support messages, and transaction references. If you use DANA, OVO, GoPay, or QRIS, the record can include status and receipt data needed to match the transaction with your account.

Yes, you can contact our account support path and ask which personal records we hold. Include the contact detail linked to your account and explain the categories you want checked. We may complete an ownership check first, and the available response depends on local law.

Send a correction request through account support with the affected detail and the accurate replacement. We compare the request with your account and may ask for phone verification before changing private data. Payment references should include the receipt date so the correct record can be located.

Yes. The Privacy Policy covers technical records created when you sign in through a mobile browser or desktop browser. Device and session signals help protect the account path, while cookies remember selected settings. Clearing browser data can remove local session markers and require another sign-in.

You can ask support which cookie setting or session record relates to your browser. You can also use your browser controls to clear or restrict cookies. After that change, the site may ask you to sign in again, and some consent choices may need to be selected again.

We retain account, security, support, and payment records for the period needed for their stated purpose, dispute handling, or a legal requirement. Ask support about a specific DANA, QRIS, bank transfer, or virtual account reference to request a retention explanation.

Related Pages

oke128 Indonesia About Us MotoGP Race Bet Account information FAQ