Reference

kaskustoto rtp Privacy Policy for Indonesia

Our kaskustoto rtp Privacy Policy explains what we collect when you open an account, use the mobile lobby, or check wallet status through DANA and QRIS.

Account dataCookie choicesPolicy requestsLocal access
kaskustotortp.club page image
REQUEST PATHS

Contact us about policy requests

A clear contact route helps you ask what data we hold, why a record exists, or how to request a correction.

Data access request Ask for the account data connected to your verified phone number, including sign-in records and wallet references. We may ask for account details to confirm that the request belongs to you.
Correction request Tell us which account detail needs changing and explain the correction clearly. We compare the request with your account record before updating information linked to DANA, OVO, GoPay, or QRIS activity.
Privacy contact For a policy question, use the support contact displayed after login and state that your request concerns privacy. Do not include a password, one-time code, or wallet security code in the message.
HANDLING DETAILS

See how we handle account data

Our privacy process follows the account journey rather than collecting unrelated details. We separate sign-in records, wallet references, device signals, and cookie choices so a request can address a specific record.

Account data

We use your account details to create access, confirm the phone verification step, and connect activity to the correct account. This can include contact details and records created while you use the lobby.

Wallet records

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account references help us identify payment activity. We keep these records for account checking and request handling, not as a substitute for your wallet credentials.

Cookie choices

Cookies can remember sign-in preferences and help us understand whether a policy page or account path loads correctly. You can manage browser cookie settings, though some account functions may then require repeated sign-in.

Account security

Phone verification helps us confirm account ownership before access or privacy details are discussed. Keep your password and one-time codes private; our support path does not need your wallet PIN.

Retention timing

We retain account and transaction records only as long as needed for account operations, security checks, dispute handling, or legal duties. A request can ask which record is retained and the reason for keeping it.

Change requests

You can ask us to access, correct, or clarify personal data through the support contact shown in your account. Include the relevant account step, such as login or QRIS status, so we can locate it.

Find Privacy Policy answers quickly

These Privacy Policy answers cover the account, device, cookie, and wallet records you are most likely to ask about before opening access. If your question is not listed, use the support contact displayed in your account area and describe the record or account step involved.

It covers account details, phone verification, device and sign-in records, cookies, wallet references, support requests, retention, and how you can ask for access or correction.

DANA and QRIS references can be stored to match a payment request with your account. The same policy treatment applies to OVO, GoPay, bank transfer, and virtual account records.

We may collect details needed for account creation, phone verification, sign-in security, payment matching, and support. The policy does not require unrelated personal details to open its pages.

Cookies may remember a sign-in preference and help us check page function across a mobile browser or desktop device. Browser settings can remove them, but repeated sign-in may follow.

Yes. Use the support contact shown inside your account, identify the relevant record, and complete any ownership check. You can ask for access, correction, or an explanation of retention.

Phone verification helps us confirm that the person asking about account data controls the account. Never send a password, one-time code, or wallet PIN with your request.

Access and eligibility depends on local law. The policy applies to activity handled through our Indonesia-facing service where local law permits, including requests made through the account support path.