Reference

cgk33 Privacy Policy for Your Account Data

cgk33 Privacy Policy explains what we collect when you open an account, complete phone verification, use the mobile lobby or contact account help.

Clear data purposesPayment status contextAccount access controlsPolicy contact route

Explore Our Lobby Read FAQ

See How Payment Data Is Used

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

DANA, OVO, GoPay and QRIS details help us match a payment request with the correct account and show whether a cashier step is pending, accepted or needs attention. For bank transfer and virtual account payments, we may receive a reference, amount and status from the payment

1
route; we do not need your wallet password. We also record account actions linked to phone verification, login attempts and device sessions to reduce unauthorised access. Information from a Live Dealer Lobby, The Dog House or Fish Hunter session is used to connect activity with the
2
correct account and maintain account records. We apply this Privacy Policy according to the law that applies to your access, and eligibility depends on local law. Please check this page before opening an account or sending a policy request.

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

POLICY HELP ROUTE

Get Policy Help Near Your Cashier

A clear account-help route lets you ask about personal data without guessing which team handles the request. Start from the support contact path connected to your account and include the phone number or account reference involved. We can then check the relevant login, wallet status or payment receipt record while keeping the request focused on Privacy Policy matters.

Team online

Account access

Ask us to clarify phone verification records, login activity or a device session connected with your account. Share only the details needed to locate the record safely.

Wallet status

For DANA, OVO, GoPay or QRIS questions, send the payment reference and visible status. We use that detail to explain what account data is connected with the payment.

Policy request

Request a copy, correction or deletion assessment through our account help route. We may ask for verification before discussing personal data or changing an account record.

DATA CONTROL DETAILS

Keep Control of Account Data

Your phone verification step gives us a practical way to distinguish your account from an unknown login, while browser and device records help us investigate unusual activity.

What we collect

We may handle your account phone number, verification result, login time, device details, IP address, payment reference and support messages when those details are needed for account or policy handling.

Why cookies appear

Session cookies help keep you signed in while moving from account access to the lobby. Preference and measurement cookies help us understand page use; browser controls can manage them.

Account protection

Phone verification, session checks and login records help us examine access concerns. Never send a wallet password in a support request, including for DANA, OVO, GoPay or QRIS.

How long records stay

We retain account, payment and support records only for the period needed for account operation, dispute handling, security checks and legal duties that apply to our service.

Who can receive data

Relevant payment and technical service partners may receive limited details needed to process a reference, display status or protect a session. We do not request your wallet password.

How to request changes

Contact account help to ask for access, correction or deletion assessment. Include your account reference and request type; we verify ownership before releasing or changing records.

Privacy Policy Answers for cgk33 Accounts

These Privacy Policy answers focus on the questions we expect you to ask before opening an account from Indonesia. They cover account records, payment references, cookies, device access and the practical route for asking us to inspect or change personal data.

It covers personal data connected with your account, phone verification, device sessions, cookies, support requests and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

Phone verification helps us confirm that the person requesting account access matches the account record. It also gives support a safer reference when you ask about login activity or policy rights.

Yes. The policy explains how we use a DANA or QRIS reference, visible amount and payment status to match a transaction request with your account without requesting your wallet password.

We may record device type, browser details, IP address, session time and login events. These records help us assess unusual access and keep your account connected when you use a mobile browser.

Use the account help contact path and state whether you want access, correction or deletion assessment. Add your account reference, then complete any ownership check we request before handling the record.

Cookies can keep your session active and show whether policy pages load correctly. Some also measure page use. You can manage available cookie settings through your browser, although session changes may affect access.

Yes. Account access and data handling depend on local law. We apply the Privacy Policy to the extent permitted for your location and may request details needed to assess eligibility.

cgk33 Privacy Policy for Your Account Data

Get Policy Help Near Your Cashier

Account access

Wallet status

Policy request

Keep Control of Account Data

What we collect

Why cookies appear

Account protection

How long records stay

Who can receive data

How to request changes

Privacy Policy Answers for cgk33 Accounts

01 What does the cgk33 Privacy Policy cover?

02 Why does cgk33 need phone verification data?

03 Does the Privacy Policy include DANA and QRIS payments?

04 What device data does cgk33 store?

05 How can I request a copy or correction?

06 How does the Privacy Policy treat cookies?

07 Does access depend on local law?

Related Pages