Reference

jkt48 web slot Privacy Policy

jkt48 web slot Privacy Policy explains what we collect, why we use it, and how you can ask about your account records before opening access.

Account dataWallet recordsCookie choicesAccess requests
jkt48 web slot jkt48 web slot Privacy Policy
PRIVACY HELP PATH

Ask About Your Account Records

A clear support path helps you deal with a privacy question without sending account details through an unrelated channel. Start from the account help path and tell us whether your request concerns sign-in data, a wallet reference, a cookie choice or a correction to your profile. We may ask for the account step that relates to your request so we can locate the right record without exposing another person’s details.

Team online

Account privacy request

Use the account help path to ask what personal details we hold or to request a correction. Include the phone verification stage or account reference connected with your request, and we will use those details to identify the correct record.

Payment record question

For a DANA, OVO, GoPay or QRIS record, share the payment reference rather than a wallet password or security code. We can check the account-side status and explain which transaction detail is linked to your profile.

Access and deletion request

If you want a copy, correction or removal request assessed, contact us through account help and describe the exact data involved. We may verify account ownership before acting, and access remains subject to local law and required transaction records.

HANDLING YOUR DATA

What We Do With Privacy Requests

We separate account operation from privacy handling so a request can be checked against the right record.

Collection at account access

We collect details you enter during the account path, plus phone verification results needed before access. Device and browser signals can help us spot an unusual sign-in, while we avoid asking for wallet passwords through support.

Wallet and payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create references attached to your account record. We use these references to check payment status, not to request your private wallet security code.

Cookies on your device

Cookies can remember session settings and help us understand how a page is reached. Your browser controls can block or remove them, although changing those settings may affect sign-in continuity or the way policy pages load.

Account security checks

Phone verification and sign-in signals help us distinguish your normal account path from an unusual device event. If a check is needed, we use the account help path and do not ask you to disclose a wallet password.

Retention and removal

We keep personal records for the purpose that required them, account protection, dispute handling or legal duties. A removal request can be sent through account help, though some transaction or security records may need to remain where local law permits.

Requesting a policy change

You can ask us to correct account details, explain a stored record or assess a removal request. Give us the relevant account reference and request type; we may confirm ownership before changing information tied to your access.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account questions we expect before you open access from Indonesia. They explain phone verification, payment references, cookies, device records and requests for copies or corrections. If a question concerns eligibility, remember that access depends on local law. For a record-specific matter, the account help path gives us the context needed to respond.

It covers account details, phone verification, device and browser signals, cookies, support requests and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains why we use those records, how long they may remain and how to request a change.

Phone verification is used before account access to help confirm that the account path belongs to you and to reduce unusual sign-in events. We may connect the result with device signals for security. We do not ask for your wallet password as part of this check.

Yes. The Privacy Policy includes account-side references for DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. These references help us check payment status and resolve an account question without requiring your private wallet security code.

You can contact us through the account help path and ask for a copy or correction of the details connected to your account. Tell us which record you mean, such as a phone detail or payment reference. We may verify account ownership before releasing or changing it.

Cookies may remember session settings and help us understand how you reached a policy or account page. You can block or remove them through your browser controls. Some sign-in continuity or page behaviour may change after that choice, but the policy remains available.

We keep data for the purpose that required it, including account security, payment reconciliation, dispute handling or legal duties. When you request removal, we assess the relevant record and whether it must remain. The outcome depends on the data type and where local law permits.

Use the account help path and describe whether your question concerns access, cookies, phone verification, a wallet reference or a correction request. Include only the details needed to locate your record. We may ask for an account reference so we do not disclose another person’s data.