Reference

90bola Privacy Policy For Indonesia

Our Privacy Policy explains how 90bola uses account, device and payment details when you open an account or reach the lobby.

Account clarityWallet record careCookie choicesRequest support
90bola 90bola Privacy Policy For Indonesia
PRIVACY CONTACT ROUTE

Get Privacy Help Beside Account Verification

A clear contact route matters when a name, device record or wallet reference needs attention. From your account area, use the support contact shown beside account and cashier assistance, then describe the Privacy Policy request in plain English. For help from Jakarta or Surabaya, include the account identifier and the relevant DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference, but do not send a password or full payment credentials.

Team online

Account request

Use the support contact inside your account for a copy, correction or removal request. We ask for the account identifier and enough context to locate the record, then use Account Verification before changing personal details.

Wallet query

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, tell us the date, amount reference and displayed status through the account support path. We compare the record with the wallet event without asking for your secret wallet code.

Security concern

For an unfamiliar login or device record, contact us through the same account support route and change your password before sharing details. We use the account trail, device signal and recent access record to assess the request.

DATA HANDLING PRACTICE

How Account Security Meets Privacy

Privacy work continues after Account Verification. We separate identity details from routine lobby activity where our systems allow, restrict internal access to people who need a task completed and review unusual sign-ins…

Collection

We collect the details needed to create and maintain your account, complete Account Verification and answer a support request. Device, browser and session signals help us distinguish a normal login from an unfamiliar access attempt.

Cookie control

Cookies can keep a session active and remember selected settings on your mobile browser. You can adjust cookie controls in the browser path you use, although disabling some cookies may require another login or limit account-session functions.

Account security

We use account credentials, verification checks, device signals and access records to reduce unauthorised entry. Never send a password, wallet PIN or one-time code through support; our Privacy Policy does not require those secrets.

Retention

We keep personal and transaction records for as long as a service, security review, dispute or legal requirement calls for them. When a record is no longer needed for those purposes, our process removes or anonymises it.

Your request

You can ask us to access, correct or delete personal details, subject to checks and any record we must retain. Include the account identifier and request type through the support contact shown in your account area.

Policy changes

If this Privacy Policy changes in a way that affects account data use, we place the updated wording on this page. Check the policy before using the lobby, wallet status tools or account settings where local law permits.

Privacy Policy Questions For Your Account

These Privacy Policy answers focus on the searches we expect from an Indonesian account holder. They explain the records connected with login, Account Verification, device use and local wallet references, plus the practical route for requesting access or a change. If your situation is unusual, use the support contact inside your account and include only the details needed to locate the record.

It covers personal details, Account Verification, device and browser signals, cookies, login events, support messages and payment references. It explains how we use, protect, retain and disclose those records when you use the account where local law permits.

We use device and browser signals to keep a session working, recognise unusual access and investigate an account-security concern. The record can include device type, browser details, session time and security events, rather than the private contents of your device.

Yes. We may retain a wallet name, transaction reference, status and related account record when you use DANA, OVO, GoPay or QRIS. We use those details to match activity, resolve a query and protect the account, not to request your wallet PIN.

Account Verification lets us check that requested account changes relate to the right person. We use the submitted details for that check, account security and required records. You should send only the requested material through the account support path.

Open the support contact shown in your account area and ask for a copy of your personal records. Include your account identifier and the data category you need, such as login, cookie, Account Verification or wallet records. We may verify the request first.

You can request a correction or deletion through the same support route. We assess the request against account security, unresolved disputes and records that must be retained under local requirements. If deletion is not possible, we explain which record remains and why.

Use the support contact inside your account and label the message as a Privacy Policy question. For a faster check, mention the account identifier, device or wallet reference involved, and whether you need access, correction, deletion or clarification.