Reference

kuda189 Privacy Policy for Your Account

kuda189 Privacy Policy explains how we use your account data when you open access, sign in from a mobile browser, or check DANA and QRIS status.

Account dataWallet detailsCookie choicesRequest access
kuda189 kuda189 Privacy Policy for Your Account
REQUEST PATHS

Privacy Requests Beside Account Support

A clear request path helps you act when a privacy question sits beside a login or wallet issue. Start from the account support area and include the email or phone detail attached to your account, the subject of your request and any relevant reference. We use those details to locate the right record without asking you to send a wallet password. The route is available to you where local law permits.

Team online

Account support

Use the support link after sign-in to ask about stored account data, a correction or the status of a Privacy Policy request.

Cashier reference

For DANA, OVO, GoPay, QRIS or bank transfer concerns, include the payment reference so we can separate wallet status from personal data.

Access request

Ask for a copy or change through the same account path, then complete the account check needed to protect your personal records.

DATA PRACTICES

Baccarat Access and Data Handling

We apply this policy to the account journey rather than treating privacy as a separate page.

Collected details

We may hold account contact details, verification results, sign-in events, device signals, support messages and payment references connected with your account.

Cookie controls

Cookies can remember sign-in preferences and selected settings. Your browser controls let you manage them, although some account functions may then need repeated choices.

Account protection

We use sign-in checks, account verification and device activity to identify unusual access before discussing private account or wallet records.

Retention timing

We keep records for the period needed for account operation, payment matching, security checks, disputes or legal duties, then remove eligible data.

Correction requests

If your phone, email or other account detail is incorrect, contact support from your account path and tell us which record needs changing.

Policy contact

Privacy questions belong in the account support route; include your account identifier and request type so we can respond without exposing another person’s data.

Privacy Policy Questions Before Account Access

These Privacy Policy answers cover the questions we expect before you open an account or ask us to change stored data. They explain wallet references, mobile access, cookies, retention and the account route for requests. If a question depends on your location or legal status, access depends on local law and our support team can direct you to the relevant policy path.

It covers account details, verification records, sign-in activity, device signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We use contact and verification details to open and protect your account, match wallet status and respond to requests. Access or eligibility depends on local law.

No. We use payment references and status details to match activity to your account; we do not ask you to provide a DANA, OVO, GoPay or QRIS wallet password.

Sign in, open the account support path and state that you want a data copy. Add your account contact detail so we can verify the request before releasing records.

Yes, where local law permits. Use account support, identify the incorrect phone, email or verification detail, and provide the replacement data needed for a proper check.

Cookies can retain sign-in preferences and selected settings on your mobile browser. Disabling them may require repeated choices, while account access still follows the Privacy Policy.

We retain records for account operation, payment matching, security, disputes or legal duties. When those reasons end, eligible data is removed according to applicable requirements.