Reference

Open kuatjp Privacy Policy Before Your Account

kuatjp Privacy Policy explains what we collect when you open an account, sign in from a phone, browse Live Baccarat Diamond or use DANA and QRIS.

Account-first wordingWallet data clarityIndonesia access rulesCookie choices
kuatjp Open kuatjp Privacy Policy Before Your Account
CONTACT PATHS

Check Privacy Questions Through Account Support

A clear contact path helps when you want to ask about the Privacy Policy, correct an account record or understand a payment reference.

Policy request Use the account support route to ask which personal data we hold for your kuatjp profile. Include the email or phone linked to the account, but do not send a password, wallet PIN or full payment credential.
Correction path If your name, phone number or account record needs correction, tell us what changed and why. We may ask for a verification step before editing the record so a request cannot redirect another person’s account.
Wallet question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, provide the transaction reference and date shown in your cashier receipt. We use those details to separate a privacy request from a payment-status check.
DATA HANDLING

Browse How Privacy Works Behind Your Login

Privacy choices should fit the way you actually use an account. We describe how login records, device behaviour, cookies and cashier references support account access without turning a policy page into a…

Account records

We use account details to create your profile, confirm the phone step and keep sign-in activity connected to the correct account. This includes the contact details you submit and records needed to respond to a Privacy Policy request.

Device signals

When you open the lobby on a phone or desktop, technical signals such as browser type, session time and device path can help us protect login access. These signals also help us investigate an account request without asking for your password.

Cookie choices

Cookies can keep a session working and help us understand whether a policy page or account step loaded correctly. Your browser controls may allow you to limit cookies, although some login or account functions may then need another verification step.

Wallet references

We retain payment references, not a request for your wallet PIN, to reconcile DANA, OVO, GoPay and QRIS events with the account that started them. Bank transfer and virtual account references may be checked for the same reason.

Retention approach

We keep records for as long as needed for the stated account, security, payment reconciliation and legal purposes. When a retention period ends, we remove or separate the record in line with applicable local requirements.

Change requests

To request access, correction or another policy action, contact us through the account support path and describe the record involved. We may ask for account verification, then explain the result or any limit that depends on local law.

Ask About Privacy Policy And kuatjp

These Privacy Policy answers focus on the questions you may have before opening an account or using the wallet path. We keep the wording practical: what data is involved, why verification may appear, how cookies behave and where to send a request. If your situation involves a payment provider or a legal restriction, our response may depend on local law.

The kuatjp Privacy Policy covers account details, phone verification, login records, device signals, cookies, support requests and payment references. It explains why we use each category, how we protect account access and how you can ask for access or correction where local law permits.

Phone verification helps us connect an account to the person completing the access step and helps prevent a request from changing someone else’s record. We may use its status when handling account support, but we do not need your wallet PIN for a DANA or QRIS question.

Yes. The Privacy Policy covers the transaction references and account links created when you use DANA, OVO, GoPay or QRIS through the cashier path. We use those references to check status and reconcile a receipt, while the wallet provider handles its own separate data practices.

Send a data access request through the support route connected to your kuatjp account. State the phone or contact detail linked to the profile and the records you want to access. We may verify your identity before responding, and the outcome depends on local law.

Yes. Tell us which account field is wrong, such as a phone number or contact detail, and provide the corrected value through account support. We may request a verification step before editing it, because a correction must not weaken another person’s account security.

Cookies can keep your login session active and help us identify whether a policy or account page loaded correctly. You can adjust cookie controls in your browser, but limiting them may require another sign-in or may affect parts of the account path.

Use the account support path and ask about deletion or retention for a named record, such as a login event or payment reference. We first verify the request, then explain what can be removed, retained or restricted because of local legal requirements.