Reference

raja colok Privacy Policy For Your Account

Our Privacy Policy explains how raja colok handles your account details, device data and wallet records when you use the lobby.

Account dataWallet recordsCookie choicesRequest support
raja colok raja colok Privacy Policy For Your Account
HELP WITH PRIVACY

Get Policy Help Beside Your Wallet

A clear support route helps you act on this Privacy Policy without leaving your account flow.

Account data request Use the account help path to ask which personal details we hold for your…
Wallet record question If a DANA, OVO, GoPay or QRIS reference appears unclear, send the date, amount…
Correction or removal Tell us which account detail needs changing or which data you want removed.
DATA IN PRACTICE

How We Keep Privacy Policy Clear

We keep this policy practical by linking each data use to a real account action.

Account details

We may hold your phone number, account identifiers and verification results so we can open the correct account path and…

Device and cookies

Your phone or desktop browser can send device and session details when you move from login to the lobby.

Payment matching

A transaction reference helps us connect a deposit or withdrawal status with your account.

Account security

Phone verification is an account step before access, and we may ask for additional confirmation when a request involves private…

Retention decisions

We keep account, support and transaction records for the period needed to provide the service, investigate disputes, protect accounts or…

Requesting changes

You can ask for access, correction, deletion where permitted, or a reason for a particular data use through the account…

Privacy Policy Answers For Account Holders

These Privacy Policy questions cover the account and wallet situations you are most likely to face on raja colok. We explain the data connected with login, payment checks, cookies, corrections and deletion in direct terms. If your situation is unusual, use the support route with the account details needed to identify your request, while keeping passwords and security codes private.

The Privacy Policy covers data linked to your account, phone verification, device session, cookies, support requests and payment references. It explains why we use those details, when a record may be shared for an operational or legal reason, and how you can request access or correction.

We use your phone number to create and verify the account path before access. It also helps us identify the right account when you ask for a data copy or correction. We do not ask you to send a password or wallet PIN for that request.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references to match status, investigate a receipt and support the correct account without needing unrelated wallet credentials.

You can request a copy of the personal data connected with your account through the support path. Include the phone number linked to your profile and describe the request. We verify account ownership first, then explain the available format and any limits required by law.

Cookies and session details can help your mobile browser remember settings and keep the path from login to the lobby working. You can change cookie controls in the browser, but turning some off may require another sign-in or affect account functions.

Send a correction or removal request through account help and identify the detail involved. We verify ownership, update inaccurate data where possible, and explain if a transaction, security or legal record must remain. Removal access depends on local law and the record's purpose.

Use the account support route for a Privacy Policy concern, especially when it involves a login detail, device session or wallet reference. Provide only the minimum details needed to locate your account. We can explain the data use, request process and next step.