Reference

Privacy Policy for Your kembarjitucom Account

Our Privacy Policy explains how kembarjitucom handles the account, device, wallet and support details you provide before you enter the lobby.

Clear data purposesWallet details explainedAccount controls includedCookie choices available
kembarjitucom Privacy Policy for Your kembarjitucom Account
CONTACT ROUTES

Get Privacy Help Near Your Account

A direct support route helps you ask about the Privacy Policy without sending sensitive payment details through an open message.

Policy questions Ask which account, device or cookie detail is held about you.
Wallet references For DANA, OVO, GoPay or QRIS questions, share the transaction reference shown in your…
Account checks When a request concerns account access, we use a verification step before changing personal…
CONTROL CENTRE

How We Handle Your Data Choices

We separate information needed for account operation from optional signals used to understand device visits.

Data handling

We use your phone number, account details and payment references for stated account purposes.

Cookie controls

Our browser cookies can remember session settings and help us understand whether a sign-in step completed.

Account security

Phone verification and sign-in event checks help connect account activity with the right person.

Retention timing

We keep account, transaction and security records only while an operating, dispute or legal purpose remains.

Who to contact

Our account support route handles questions about the Privacy Policy, stored details, cookie use and wallet references.

Change requests

You can ask us to correct an inaccurate phone number, profile detail or account record.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account and device questions you may have before opening access through kembarjitucom. They cover what we collect, why wallet references appear, how to request a change and what happens when access depends on local law. If your situation is not listed, use the account support route with a reference rather than a password or wallet PIN.

The Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages, security events and payment references. It explains why we use each category, how long we may retain it and how you can request correction or clarification through the account support path.

No. Our Privacy Policy does not require you to send a DANA or QRIS PIN to us. We may retain a payment reference, amount, status and account link needed to match an account event, while DANA, QRIS and the related provider handle credentials under their own terms.

Device type, browser version, session markers and sign-in events help us recognise an account access pattern and investigate unusual activity. The Privacy Policy treats these as security and service records, not as a reason to request your password or wallet credential.

Use the account support route and identify the phone number or account reference connected with the record. Tell us which detail is inaccurate, such as a phone number or profile entry. We may complete a verification step before changing it, and we will explain any required retention.

The Privacy Policy allows retention while an account, payment question, security matter, dispute or legal duty needs the record. After that purpose ends, we remove or de-identify the data where practical. A payment provider or bank may keep separate records under its own retention rules.

Yes. You can ask our account support route which cookies relate to session settings, sign-in continuity or browser measurement. You can also change cookie choices in your browser. If cookies are restricted, a sign-in or account step may need to be repeated.

Access and eligibility depend on local law. Our Privacy Policy explains the data used to apply those rules, such as account and location signals, but it does not change the law that applies to you. If access is unavailable, contact support without sending sensitive credentials.