Reference

Open bcl303 privacy controls on mobile

Live Baccarat Table, Makassar Lucky Slots and Esports PUBG Mobile each sit behind an account flow that helps us protect your personal data.

Account data explainedWallet records clarifiedMobile access coveredLocal law applies

Explore Our Lobby Read FAQ

Check how wallet data is used

bcl303 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers the details needed to create and protect your account, including your name, phone number, verification status, login events, device signals and payment references. When you use DANA, OVO, GoPay or QRIS, we receive transaction status and reference details needed to match a

1
cashier action; we do not need your wallet password. Bank transfer and virtual account records can include the receiving bank, such as BCA, BRI, Mandiri or BNI, plus a reference and status. We use this material to process requests, detect unusual access, answer support questions and
2
meet applicable obligations. Retention depends on the purpose and local requirements, while eligibility and access depends on local law. Read the current policy before opening an account.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

REQUEST HELP DIRECTLY

Contact us about a privacy request

A clear contact path matters when your account record or wallet reference needs attention.

DATA HANDLING PATH

Explore account security and retention

Privacy controls work best when they follow the same path as your account activity. We separate sign-in details from wallet credentials, record security events around phone verification, and…

Phone verification

Before account access or a sensitive data request, we may use the verified phone step linked to your profile.

Device signals

A mobile browser can send practical signals such as device type, session time and security events.

Cookie choices

Cookies can keep a session active and remember selected settings between account pages.

Payment records

We retain a payment reference, rail and status when needed to match cashier activity.

Retention timing

Retention is tied to the reason data was collected, such as account security, a support case or a payment reconciliation.

Change requests

You can ask us to correct a phone number, clarify a cookie record or explain account data through the support…

Find answers about bcl303 Privacy Policy

These Privacy Policy answers focus on the account actions you are most likely to take from Indonesia. We explain the data connected to phone verification, mobile access, cookies and local payment rails, then point you to the support route for a personal request. If a question concerns eligibility or access, the answer depends on local law and the details shown in your account.

It covers account details, phone verification, login and device signals, cookies, payment references, support records, security events and retention. The policy also explains how we handle requests to correct, access or remove data connected with your account and how local law affects access.

We use your phone number to create and protect the account, complete the verification step and help confirm a sensitive Privacy Policy request. Keep it current in your account area. We do not need your DANA, OVO, GoPay or QRIS password for verification.

No. When you use DANA, OVO, GoPay or QRIS, we may receive a payment reference, status and related account details needed for reconciliation. A bank transfer or virtual account may also show a bank and reference, but not your complete banking credentials.

Use the support contact displayed in your account area and state whether you want access to a record or a correction. Include the linked phone number and relevant payment reference where useful. We verify ownership first, then explain the available next step.

Cookies can maintain your session and remember selected settings when you move between account pages in a mobile browser. You can clear or restrict them through browser controls. A change may sign you out or require another phone verification step.

The period depends on why the record exists, such as account protection, a payment receipt question, a support case or a legal requirement. Ask through the support path for a specific record. We explain any retention that cannot be removed and why.

You can send a removal request through the account support contact. We verify that you control the account and assess each record. Some data may need to remain for security, dispute handling or legal duties, while account access depends on local law.

Open bcl303 privacy controls on mobile

Contact us about a privacy request

Explore account security and retention

Phone verification

Device signals

Cookie choices

Payment records

Retention timing

Change requests

Find answers about bcl303 Privacy Policy

01 What does the bcl303 Privacy Policy cover?

02 Why does bcl303 need my phone number?

03 Does the Privacy Policy store my wallet password?

04 How can I request a copy or correction?

05 How does bcl303 use cookies on my phone?

06 How long does bcl303 keep account data?

07 Can I ask for my personal data to be removed?

Related Pages