Reference

Privacy Policy for Your 20detik Account

20detik keeps the Privacy Policy close to the account path, so you can see how we handle details connected with login, DANA, OVO, GoPay and QRIS before opening…

Account clarityWallet contextDevice choicesPolicy access
20detik Privacy Policy for Your 20detik Account
CONTACT PATHS

Where Privacy Questions Go

A privacy question should not be mixed with a stalled login or an unclear wallet receipt. We separate those requests so your message reaches the right account path: use the support contact shown inside your account for personal-data questions, choose the cashier help route when a DANA or QRIS record needs matching, and include the relevant account step without sending a password. If you cannot access the account, use the contact route displayed on the 20detik site and state that your request concerns the Privacy Policy.

Team online

Account contact

Use the support contact shown in your account when you want to ask what personal details we hold, why a phone check is needed, or how to request a correction under the Privacy Policy.

Wallet matching

For a DANA, OVO, GoPay or QRIS record that does not match your account, include the payment reference and time shown in your receipt. We use those details to locate the relevant status without asking for your wallet password.

Access request

If sign-in blocks the normal policy path, contact us through the site route and name the account email or phone step you can safely confirm. We can explain the request process without requiring you to disclose a password.

HANDLING DETAILS

How We Handle Account Data

The practical side of the Privacy Policy starts with limiting each account action to the data needed for that action.

Account records

When you open an account, we record the details needed to create and maintain access, including the contact detail used for phone verification. We use that record to connect your sign-in, policy requests and account messages.

Payment references

DANA, OVO, GoPay and QRIS status checks rely on payment references and account matching. Bank transfer and virtual account records are handled for the same narrow purpose: confirming the transaction state linked to your account.

Cookies and sessions

Cookies and session records help keep the account path active and remember security choices on your device. You can clear browser cookies, although doing so may require another sign-in or phone verification before access continues.

Device security

We may use device and browser signals to identify unusual access patterns, protect the sign-in step and reduce account misuse. These signals are not a request for your device contents, contacts or private wallet password.

Retention approach

We retain account, payment-status and support records only for the period needed for the stated account, security, legal or dispute purpose. When a record is no longer needed for those purposes, our handling process moves it toward deletion or anonymisation.

Changes and requests

You can ask us to explain, correct or update personal details through the privacy contact route. We may ask you to confirm account ownership before making a change, so one person cannot alter another account's records.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account steps Indonesian customers most often need before they continue: phone verification, wallet matching, device access, cookies, data requests and local-law conditions. We keep the answers tied to how the account path works on 20detik, whether you use a mobile browser for Crash Skyrise Arena or a desktop connection for the live tables.

The 20detik Privacy Policy explains what we collect during account opening, phone verification, sign-in, wallet matching and support contact. It also covers cookies, device signals, retention, security handling and your route to request access, correction or clarification about personal details.

Phone verification connects the account to a contact step that you can confirm before access continues. We use it to help protect sign-in and account changes, not to request your wallet password. If verification fails, contact support through the route shown on the site.

Yes. The Privacy Policy covers the payment references needed to match DANA and QRIS status with your account. Similar handling applies to OVO, GoPay, bank transfer and virtual account records. We ask for the reference and receipt time, not your private wallet credentials.

We may receive technical details from the browser or device used for the account path, including session data and security signals. Those details help identify unusual sign-in activity and keep a mobile session working. We do not need access to your contacts or device files.

You can contact us through the privacy route displayed in your account or on the site and ask for access, clarification or correction. We may request an account ownership check before changing records. Include the affected account step, but never send a password.

We keep account, payment-status and support records for the period needed for the stated account, security, legal or dispute purpose. When that purpose ends, our process moves the record toward deletion or anonymisation, subject to any applicable local requirement.

Use the policy link on the 20detik site or the account help route when your normal sign-in path is available. Account access and eligibility depends on local law. If the page is unavailable, contact us through the displayed site route and request the Privacy Policy.