Reference

kpk100 Privacy Policy, Made Clear

The kpk100 Privacy Policy explains how we collect, use and protect your account, wallet and device data when you open the lobby from Indonesia.

Account dataWallet recordsCookie choicesContact steps

Explore Our Lobby Read FAQ

What Our Privacy Policy Covers

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

Our Privacy Policy applies when you create or access an account, contact support about a wallet status, or use the mobile path to reach titles such as Live Blackjack Elite and Banjarmasin Casino Lobby. We may collect account details, phone verification results, device signals, session activity

1
and payment references needed to match a transaction with your account. DANA, OVO, GoPay, QRIS, bank transfer and virtual account records can show a reference, amount and status, but we use them for account and payment handling rather than unrelated purposes. We retain records only for
2
operational, safety, dispute and legal needs, then remove or anonymise them when they are no longer needed. Access and eligibility depend on local law; this policy applies where local law permits.

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

CONTACT YOUR WAY

Get Privacy Help Beside Account Support

A clear contact route helps when you need to ask about a stored detail, a wallet reference or a device record.

DATA HANDLING

How We Handle Your Privacy Choices

Privacy controls work best when they match the actual account journey. We separate sign-in checks from payment references, limit internal access to people who need the record for…

Account security

Phone verification is used before account access so we can connect a sign-in attempt with the right account.

Cookie controls

Cookies and similar device storage can remember a session or page setting on your browser.

Payment references

When you use QRIS, DANA, OVO or GoPay, we record the reference and status needed to match the wallet event…

Retention periods

We keep account, session and payment records for as long as they serve account access, dispute handling, safety or legal…

Data access

You can ask which personal data is linked to your account and request a usable copy where the request is…

Corrections and removal

Tell us if an account detail is inaccurate or if you want a qualifying record removed.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the searches we hear around account creation, wallet activity, device access and personal data requests. We keep the wording practical so you can decide what to share before opening an account or contacting us. If your question concerns eligibility or access, the answer remains subject to local law and the account details we can verify.

It covers personal data connected with your account, phone verification, device sessions, cookies, support requests and payment references. The policy also explains why we retain selected records, how we protect account access and how you can request access, correction or removal where permitted.

No. To match a DANA or QRIS event, we use a transaction reference, status and related account details rather than your wallet password. If a payment needs checking, send the reference through account support and do not share your wallet login secret.

Phone verification helps connect an account access attempt with the correct account and reduces the chance of an unauthorised change. We may also use it when handling a privacy request, because confirming account ownership protects your personal and wallet-related records.

Use the signed-in account support path and ask for access to your personal data. Include your registered phone detail and explain whether you need account, device, cookie or payment-reference records. We verify the request before sharing data linked to your account.

Yes, you can request correction of an inaccurate detail or removal of a qualifying record through account support. We may retain some data for safety, dispute handling or legal duties, and we will explain when that limits the requested change.

The period depends on why the record exists. We retain payment references, account events and device signals while needed for access, safety, disputes or legal duties, then remove or anonymise them when that purpose ends.

The same Privacy Policy applies on mobile and desktop. A mobile browser may store session cookies and device signals differently, but the account, phone verification and payment-reference rules remain the same. You can manage cookie permissions in your browser settings.

kpk100 Privacy Policy, Made Clear

Get Privacy Help Beside Account Support

How We Handle Your Privacy Choices

Account security

Cookie controls

Payment references

Retention periods

Data access

Corrections and removal

Privacy Policy Answers For Your Account

01 What does the kpk100 Privacy Policy cover?

02 Does kpk100 store my DANA or QRIS password?

03 Why does kpk100 need phone verification?

04 How can I request my personal data from kpk100?

05 Can I ask kpk100 to correct or remove data?

06 How long does kpk100 keep payment and device data?

07 Does the Privacy Policy change if I use a mobile device?

Related Pages