Reference

Privacy Policy for Your mediabola78 Account

mediabola78 Privacy Policy explains how we handle the details connected with your account, phone verification, browser device and wallet status before you reach titles such as Live Roulette…

Account dataWallet checksCookie choicesContact requests
mediabola78 Privacy Policy for Your mediabola78 Account
CONTACT ROUTES

Three Ways to Ask About Privacy

A clear contact route helps when you want to understand a record rather than simply change a setting. Start from the support contact path connected with your account and include the phone number or wallet reference you want us to check. We use that detail to separate your request from another account, including when you are reaching us from Jakarta or while a QRIS status is still being matched. We may ask for additional account proof before discussing private data.

Team online

Account access request

If phone verification blocks access, tell us which account step stopped and the device path you used. We can explain what account data is needed before discussing a private record or correcting your contact details.

Wallet record request

For DANA, OVO, GoPay or QRIS questions, provide the visible reference and date from your account. We use those details to locate the relevant payment record without asking you to send a wallet password.

Privacy question

Ask how we use a particular detail, cookie or message through the account support route. We will identify the policy point involved and explain any verification needed before releasing or changing information.

DATA PRACTICE

How We Handle Six Privacy Areas

We organise this policy around the actions you can actually take: understand collection, manage cookies, protect account access, request a correction, ask about retention and contact us about a wallet reference.

Data we receive

We may receive your account name, contact detail, phone verification result, device session signals and messages sent to support. Payment references from DANA, OVO, GoPay or QRIS help us match an account event, but they are handled as account records rather than public profile details.

Cookies and sessions

Cookies can keep your sign-in session connected while you move between account pages on a phone or desktop browser. If you clear them, we may ask you to sign in and complete the account check again before showing private account information.

Account security

We treat phone verification as an account access step, not as permission to disclose every record. If a request comes from a new device or lacks the required account detail, we may pause the response until ownership is confirmed.

Correction requests

You can ask us to correct an inaccurate contact detail or account record through the support path connected with your account. Include the specific field and the reason for the change; we may verify your identity before applying an update.

Retention questions

Our retention decision depends on why a record exists, such as account access, payment reconciliation, security review or a legal requirement. A request about a QRIS, bank transfer or virtual account record can be assessed against that purpose.

Policy contact

When you ask about this Privacy Policy, describe the data point or account step in plain English and include your account reference. We will route the question to the relevant contact path without asking you to publish private details in a game or lobby message.

Privacy Policy Questions About Your Account

These Privacy Policy answers focus on the searches we expect before you open an account or return to an existing one. They cover the records linked with phone verification, browser use, local wallets and contact requests. If your situation is different, use the account support path and describe the exact detail you want us to locate or change.

It covers account details, phone verification, browser sessions, cookies, support messages and payment references linked with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains how to ask about access, correction and retention where local law permits.

Phone verification helps us confirm that the person requesting account access or private data matches the account record. If you sign in from a different mobile or desktop browser, we may repeat that step before discussing wallet status or changing contact details.

Yes. The Privacy Policy covers payment references connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account records. We use those references to reconcile account activity, not to request your wallet password or publish your transaction details.

You can request a correction through the support route connected with your account. State which field is inaccurate and provide the relevant account reference. We may complete phone or account verification first so a change is not made by someone else.

Cookies can preserve a signed-in session and remember the browser path needed to reach account pages. Clearing cookies may sign you out or require phone verification again. Your browser controls cookie removal, while the Privacy Policy explains why session data is used.

Retention depends on the reason for keeping a record, including account access, payment reconciliation, security needs or a legal requirement. You can ask about a specific record, such as a QRIS or virtual account reference, and we will assess it against that purpose.

The policy is provided for Indonesian account access where local law permits, and eligibility depends on local law. If a local requirement affects what we can collect, retain or disclose, that requirement takes priority and we will explain the relevant account impact.