Reference

Open kapal 303 slot Privacy Policy

kapal 303 slot Privacy Policy explains what we collect when you open an account, verify your phone, browse on mobile and use DANA, OVO, GoPay or QRIS.

Clear data purposesPhone verification contextWallet record handlingCookie choices
kapal 303 slot Open kapal 303 slot Privacy Policy
HELP WITH DATA

Reach support about Privacy Policy

A clear support route matters when you want to ask about a Privacy Policy entry, a phone check or a wallet reference. Start from the account help path and include the email or phone detail connected to your account, without sending a password or one-time code. If a receipt appears beside a DANA or QRIS record, our team can use the reference to locate the relevant entry. You can also ask how to submit a correction request.

Team online

Account help path

Use the account help route when a Privacy Policy question concerns your phone verification, login record or stored contact detail. We can explain which data point is being checked and what account step is needed, while you keep passwords and one-time codes private.

Cashier reference check

For a payment-data question, provide the receipt reference rather than sensitive wallet credentials. We can trace the related DANA, OVO, GoPay, QRIS, bank transfer or virtual account entry and explain how that record fits the Privacy Policy.

Policy request route

Ask us to correct an inaccurate account detail, clarify a cookie choice or explain retention through the available support contact. Include your registered phone detail and request type so we can locate the right record without exposing unrelated account data.

DATA PRACTICES

Explore our Privacy Policy safeguards

The way we handle data is tied to specific account actions rather than broad promises.

Account details

We collect the contact and login details needed for an account path, including the phone detail used before account access.

Device signals

When you open the lobby in a mobile browser, technical signals such as session details and device characteristics may be…

Cookie choices

Cookies can support a remembered session, page settings and basic access measurement.

Payment records

A DANA, OVO, GoPay or QRIS reference can be retained with the related account transaction record.

Retention timing

We retain account, security and payment records only for the period needed for the purpose described in the Privacy Policy…

Change requests

You can ask us to correct an inaccurate phone detail, clarify a stored record or explain how a request is…

Browse Privacy Policy answers

These Privacy Policy questions cover the account actions you are most likely to check before opening access. We address phone verification, cookies, mobile sessions, payment references, retention and correction requests in plain language. If your question involves eligibility, remember that access depends on local law and is provided where local law permits. For a record tied to your own account, use the support path with a relevant reference.

It covers account details, phone verification, mobile session signals, cookies, payment references, security handling, retention and requests to correct applicable data. It also explains how we respond when you ask about a DANA, QRIS, bank transfer or virtual account record connected with your account.

Phone verification helps us connect an account access attempt with the correct account and identify unusual login activity. It is part of the account security process described in the Privacy Policy. Keep your verification code private, and contact support if the phone detail shown is inaccurate.

Yes. When you move from login to the lobby on a mobile browser, we may handle session details and device signals for access continuity and security checks. The Privacy Policy explains these purposes, while browser settings can affect cookies and the way a session is remembered.

We may keep the payment reference, amount context and status needed to match a DANA or QRIS receipt with the correct account transaction. We use that record for reconciliation and support questions, not as a substitute for your wallet credentials. The Privacy Policy describes this handling.

You can ask us to correct an inaccurate contact detail or clarify a record through the available account support route. Include your registered phone detail and the specific change requested. We may confirm account ownership before acting, so another person cannot alter your information.

The retention period depends on the purpose of the record, such as receipt matching, account security, dispute handling or a legal requirement that applies where local law permits. Our Privacy Policy explains the applicable process, and support can clarify a particular DANA, OVO or bank reference.

Use the account help or policy request route and describe the question without sending a password or one-time code. Include a safe reference, such as the relevant receipt number or registered phone detail. We can then explain the record, correction path or cookie question involved.