Reference

clikbet88 Privacy Policy For Your Account

clikbet88 Privacy Policy explains how we collect, use and protect the details connected with your account, including phone verification and wallet records for DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record contextAccount request pathIndonesia access wording
clikbet88 clikbet88 Privacy Policy For Your Account
PRIVACY HELP PATH

Contact Path For Wallet Data Questions

A clear contact route matters when your account data does not match a wallet receipt or phone verification step.

Account support Use the support contact inside your account when a phone verification record, profile detail or login session appears incorrect. We can explain which data we hold, why it is needed and what evidence may be required before changing an account record.
Wallet receipt check If a DANA, OVO, GoPay or QRIS reference does not match your account history, send the payment reference through the stated support path. We use the transaction status and account details to investigate without asking for your wallet password.
Privacy request For a copy, correction or removal request, identify your account and describe the change clearly. We may verify ownership through the phone number linked to the account before responding, so another person cannot alter your private records.
DATA HANDLING PRACTICE

How Account Data Stays On Track

We treat the Privacy Policy as an operating process rather than a small print page. The same account details used for phone verification can help us match a cashier reference, while browser…

Account details

We use your submitted phone number and account details to create, verify and maintain your account record. A requested change is checked against the existing account before we edit it, helping prevent an unrelated person from taking control of your profile.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records may show a reference, amount status and time. We use these limited details to reconcile an account action, respond to a receipt question and identify a failed payment step.

Cookies

Cookies and similar browser storage can remember a session choice and help us detect an unusual sign-in. You can manage browser permissions on your device, although blocking some storage may require another phone verification step when you return.

Session security

A mobile browser and a desktop browser can produce different device and session signals. We use those signals for account security, not to request your wallet password. If access looks unusual, we may pause a session until ownership is checked.

Record retention

We keep personal and payment-related records for the period needed for account support, security checks or legal duties. When a record no longer serves one of those purposes, we remove it or make it unable to identify you.

Your requests

You may ask what data we hold, request a correction or ask about deletion through the account support contact. We assess each request under applicable rules, verify ownership through your account step and explain any part that must remain.

Privacy Policy Answers For Indonesia Accounts

These Privacy Policy answers address the questions we expect before you open an account or connect a local wallet. They cover the data created by phone verification, mobile browsing and payment references, plus the practical route for asking us to inspect, correct or remove a record. Where access or eligibility is discussed, it depends on local law.

It covers account details, phone verification, browser and device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains purposes, retention, security steps and how to request access or correction.

We use the phone number to create and verify your account, help distinguish your session from another person’s request and support account recovery checks. We do not ask you to send a wallet password through support, and any access depends on local law.

No. Our Privacy Policy separates wallet payment references from wallet login credentials. We may receive a DANA or QRIS status, reference and timing to match an account action, but you should never place your wallet password in a support message.

Use the support contact shown inside your account area and ask for a Privacy Policy data access request. Include the account phone number and the records you want checked. We verify ownership first, then explain the available copy and any lawful limitation.

Yes, send a correction request through the account support path and describe the inaccurate field. We compare it with your account and, where needed, the relevant payment reference. A phone verification step may be required before we change private records.

We keep personal, security and payment-related records only while they support account service, fraud prevention, dispute handling or a legal duty. Retention can differ by record type. After the relevant need ends, we remove the record or reduce its identifying detail.

Cookies can retain a session choice and help identify unusual access when you open the lobby from a mobile browser. You can adjust browser permissions, but blocking storage may lead to a fresh login or phone verification step on your next visit.