Reference

kipas66 Privacy Policy for Wallet Accounts

The kipas66 Privacy Policy explains what we collect when you open an account, sign in from mobile or desktop, and use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesAccess requests
kipas66 kipas66 Privacy Policy for Wallet Accounts
HELP WITH YOUR DATA

Three Ways to Ask About Privacy

A clear support path helps when you want to understand a record rather than change your account settings blindly.

Account help route Use the account support path for questions about your phone number, login history, verification record or a device that no longer belongs to you. We may ask for account details needed to confirm that the request comes from the account owner.
Wallet status check For DANA, OVO, GoPay or QRIS records, send the payment reference and date through support. We use those details to identify the relevant status without asking you to share a wallet password or full private credential.
Privacy request Ask us to explain, correct or remove eligible personal data through the available support channel. We may first verify your account phone number, then confirm which records can be changed while required transaction entries remain protected.
HOW WE HANDLE DATA

Six Practical Privacy Controls

Our privacy process follows the account journey you actually take: phone verification, device sign-in, lobby activity, wallet status and support contact.

Account details

We collect the details you provide during account creation and phone verification, including contact data needed for sign-in. This lets us confirm account ownership and respond to requests without relying only on a display name or an unverified message.

Device signals

When you sign in on a phone, tablet or desktop browser, we may record device type, browser information, approximate connection data and sign-in time. These signals help us notice unusual access and investigate an account query.

Cookies

Cookies can remember session settings and help the account page load consistently. You can manage cookie controls in your browser, although disabling certain cookies may require another sign-in or prevent a requested account function from working.

Wallet matching

Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account are used to match status and account records. We do not need your wallet password for that matching process, and support should never request it.

Retention

We retain personal data only for account operation, security checks, dispute handling and legal obligations. When a record no longer serves one of those purposes, we remove it or alter it so it no longer identifies you where practical.

Changes and contact

You can ask us to correct inaccurate account data, explain a stored record or request removal where the law allows. Send the request through support with enough detail to locate it; we may verify your phone number before replying.

Privacy Policy Answers for kipas66

These Privacy Policy answers address the searches we hear most often about account records, wallet references, cookies and access requests. They are written for Indonesian account holders and focus on what we can check from the account path. If your situation is specific, include the relevant record date when contacting support so we can respond with the right context.

The Privacy Policy covers account details, phone verification data, login and device signals, cookie activity, support messages and payment references. It can also include account actions connected with lobby titles such as Krakatau Blast Megaways when those records are needed for security or a support response.

We use your phone number to create and verify account access, help identify the account owner and respond to account requests. If a sign-in or wallet record looks unfamiliar, the verified number helps us avoid discussing private details with the wrong person.

We use payment references and status details to match an account record, confirm a request and investigate a discrepancy. We do not need your wallet password. For a query, provide the rail name, date and reference shown in your account or payment receipt.

Yes. When you use a mobile browser, we may record device type, browser details, connection data and sign-in time for session operation and security checks. The same approach applies on desktop, and you can contact support about a device entry you do not recognise.

You can request a correction through the account support route. Explain which field is inaccurate and provide the account phone number used for verification. We may confirm ownership before changing the record, and some transaction entries may need to remain unchanged for legal or dispute purposes.

We keep records while they are needed for account operation, security review, payment reconciliation, dispute handling or a legal obligation. After that need ends, we remove or anonymise the data where practical. The exact period can differ by record type and applicable local requirements.

Use the available support channel and identify your request as a Privacy Policy matter. Include your account phone number, the record type and a useful date or reference. We may verify ownership before sharing details, and access depends on local law.