Reference

kurmatoto Privacy Policy, Clearly Explained

kurmatoto Privacy Policy explains what we collect when you open an account, use a mobile browser, check wallet status or enter rooms such as Ganesha Gold and Aviator.

Account dataWallet recordsMobile cookiesAccess choices

Browse Our Lobby Read FAQ

Read How Wallet Data Is Used

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

Our Privacy Policy separates the details needed for an account from the records created when you use a wallet or browse the lobby. We may handle your name, contact details, verification response, sign-in events, device signals and payment references so we can connect a DANA, OVO,

1
GoPay or QRIS action with the correct account. Bank transfer and virtual account references can also appear in payment records, while BCA, BRI, Mandiri and BNI names may be visible in a transfer description. We do not treat a payment reference as permission to use unrelated
2
personal details. Access and eligibility depends on local law, and this policy applies where local law permits. You can ask us which categories relate to your account, request a correction, or ask how long a record is kept through the privacy route in the support area.

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

CONTACT YOUR WAY

Open A Privacy Request Path

A clear contact path matters when a record looks unfamiliar or an account step needs correction.

Account records Ask us to confirm the personal data connected with your account. Include the account contact detail and the specific record you want checked so we can direct the request without exposing another account.

Wallet references If a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference appears incorrectly, send the date and reference shown. We use those details to locate the matching payment record.

Access support When login or verification blocks a privacy request, tell us which device path you used, such as a mobile browser or desktop browser. We can then explain the next account step.

DATA HANDLING

Explore How We Protect Policy Choices

Privacy work is tied to practical account events rather than broad statements. We check the request against the account contact path, separate payment references from unrelated records, and explain the result in…

Account security

We use sign-in activity, verification results and device signals to help detect unusual account access. These checks support account protection and are handled as part of the Privacy Policy process.

Cookie choices

Cookies may remember session settings and help us understand which access path was used. You can manage browser cookie settings, though changing them may affect sign-in or saved preferences.

Payment separation

A wallet label such as QRIS or DANA and its transaction reference are kept with the relevant account event. We use that pairing to check status without treating it as unrelated profile data.

Retention checks

We retain account, verification and payment records only for the period needed for account operations, dispute handling and legal duties. You can ask which retention category applies to your record.

Correction requests

If your phone detail, contact entry or account record is wrong, request a change through support. We may ask for an account step to confirm the request before editing data.

Policy contact

Privacy questions should include your account contact, the affected data category and a short description. We use that route to explain access, correction or deletion options where local law permits.

Browse Privacy Policy Answers

These Privacy Policy answers address the searches we hear before an account is opened or a wallet is connected. We keep the wording tied to actual account, device and payment records, so you can decide what to ask through the support path.

It covers account details, verification responses, sign-in events, device signals, cookies and payment references created when you access the service or use DANA, OVO, GoPay, QRIS or bank transfer.

We use account contact and verification details to connect access with the correct account, respond to requests and check wallet records. Eligibility and access depends on local law.

Yes. The policy covers data created when you use a mobile browser, including session cookies, device signals and sign-in events. Cookie changes may affect saved settings or account access.

Use the privacy route in the support area and include your account contact plus the data category you want checked. We may confirm an account step before sharing records linked to you.

Yes. Send the incorrect phone detail, contact entry or other account field through support. We may request verification so a change is made to the right account.

Retention depends on the record type and the period needed for account operations, dispute handling and legal duties. Ask support which category applies to a DANA, QRIS or bank reference.

You can ask us to assess deletion or restriction of a data category through the privacy contact path. We will explain any account, dispute or legal reason a record must remain.

kurmatoto Privacy Policy, Clearly Explained

Open A Privacy Request Path

Explore How We Protect Policy Choices

Account security

Cookie choices

Payment separation

Retention checks

Correction requests

Policy contact

Browse Privacy Policy Answers

01 What does the kurmatoto Privacy Policy cover?

02 Why does kurmatoto need my account details?

03 Does the Privacy Policy cover mobile browsing?

04 How can I request a copy of my personal data?

05 Can I ask kurmatoto to correct account data?

06 How long are wallet and payment records kept?

07 Where local law permits, can I request deletion?

Related Pages