Reference

Privacy Policy for Your Account

Our okbos 86 Privacy Policy explains what we collect when you create an account, sign in from a mobile browser, check Live Baccarat Prestige or open Aviator Mobile…

Clear data purposesWallet record contextAccount access choicesMobile browser details
okbos 86 Privacy Policy for Your Account
CONTACT ROUTES

Privacy Questions Reach Our Support

A clear contact route helps when your account record or payment reference needs checking. If a DANA or QRIS receipt does not match the account shown after sign-in, send the relevant reference through the support route displayed on our site. We can use your account step, phone verification status and device path to locate the request without asking you to publish sensitive details in a game or lobby message.

Team online

Account data request

Ask our support team what account details are held under your verified phone path. Include your account identifier, but do not send a password, full wallet PIN or complete banking credential.

Receipt status check

For DANA, OVO, GoPay or QRIS questions, provide the payment reference and approximate date. We compare that reference with the account record and explain the next step through the stated support contact.

Access concern

If a mobile browser sign-in or phone verification step looks unfamiliar, contact us before continuing. We can review the recorded device path and guide you through account protection without requesting your private login secret.

DATA PRACTICE

Six Ways We Handle Your Details

We keep this policy practical by linking each data purpose to an account action you recognise.

Account creation

We use the details submitted during account opening to create your profile and connect the correct phone verification step. Providing accurate information helps us distinguish your account request from an unrelated sign-in attempt.

Device signals

When you sign in through a mobile browser, we may record limited device and connection signals linked to access. These details help us identify unusual account activity without treating the device itself as your identity.

Cookie choices

Cookies and similar storage can remember necessary page settings and help us understand whether a page loads correctly. You can manage browser storage through your device settings, although some account steps may then need repeating.

Payment matching

A DANA, OVO, GoPay or QRIS reference helps us match a receipt to the account requesting status assistance. We use the reference for that operational check rather than asking for a wallet PIN.

Retention period

We retain account, access and transaction records only as long as needed for the stated purpose, account support, dispute handling or applicable legal duties. We review stored records when those needs no longer apply.

Change requests

You may ask us to correct account details, explain our data use or consider a deletion request through the listed contact path. We may verify ownership before changing records connected with your phone.

Privacy Policy Answers for okbos 86

These Privacy Policy answers address the account, device and payment questions you are most likely to search before creating an okbos 86 account. Each answer points back to a practical step, from phone verification to a DANA receipt check, so you know what to send and what we may need to confirm.

It covers account details, phone verification, sign-in and device signals, cookies, support requests and payment references. This includes records connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity when we need to match or explain an account transaction.

Phone verification helps connect the account request to the correct contact path before access. It also lets us check ownership when you request a data correction or ask about an unfamiliar mobile-browser sign-in. We do not ask you to disclose your password for that check.

Yes. The Privacy Policy covers payment references used to match a DANA or QRIS receipt with your account, as well as comparable references from OVO, GoPay, bank transfer and virtual account steps. Send only the reference needed for a status enquiry, never a wallet PIN.

When you access the account through a mobile browser or desktop browser, we may record limited technical signals such as browser, connection and access timing. These signals support page function and account protection. They are handled alongside your account request, not as a substitute for phone verification.

Cookies and similar browser storage can retain necessary preferences and help us see whether account pages load as intended. You can clear or restrict them in your browser settings. If you do, sign-in or phone verification may need to be completed again on that device.

Yes. Use the privacy contact path shown on our site and identify the account record you want changed. We may ask for a verification step before editing phone, account or payment-related details, so a third party cannot alter your record.

Send a deletion request through the stated support contact with your account identifier and the reason for the request. We assess it against open support matters, transaction records and applicable legal duties, then explain which data can be removed and which must remain.