Reference

detik356 Privacy Policy For Your Account

Our detik356 Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity.

Account accessWallet recordsDevice controlsPolicy requests
detik356 detik356 Privacy Policy For Your Account
PRIVACY CONTACTS

Three Ways To Ask About Your Data

A clear contact path matters when a name, phone number or wallet reference needs checking.

Account contact Use the support route attached to your account when you want a copy of personal details linked with your login. We may ask for the registered phone number and a verification step before discussing records or making any change.
Wallet query For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, include the transaction date and reference shown in your account. We compare those details without asking you to reveal a wallet PIN or complete credential.
Privacy request Send a correction, deletion or policy question through our privacy contact path. We review the request against your account details, explain any legal or security reason for keeping a record, and confirm the action taken.
DATA CONTROL

Six Practical Privacy Controls We Apply

Privacy is handled through account steps rather than broad promises. We limit staff access to records according to the task, keep payment references separate from wallet credentials, and use device checks when…

Collection scope

We collect details that support account access, phone verification, payment matching and assistance. A visit to Spaceman Crash Play or Fishing War Arcade does not by itself require us to request extra identity details beyond the account and device data needed for the session.

Cookie choices

Cookies can keep your login path working and help us see whether a page loads correctly on mobile or desktop. You can adjust cookie controls in your browser, though restricting necessary cookies may interrupt account access or the handoff to wallet status.

Account security

Before account access, we may use phone verification and device signals to spot an unusual login. If you change phones, sign out of old sessions and contact support through the account route rather than sharing a password or one-time code.

Payment separation

Our records can show that a DANA, OVO, GoPay or QRIS transaction was matched, along with its reference and status. We do not need your wallet PIN to investigate that event, and we ask you to keep those credentials private.

Retention period

We keep account, support and transaction records only while they serve account security, dispute handling, legal duties or service administration. When a record no longer serves one of those purposes, we remove it or change it so it cannot directly identify you.

Change requests

You can ask us to correct inaccurate account details or explain how a record is used. Send the request with your registered phone number and a short description; we verify ownership first, then tell you whether the change can be completed.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers cover the searches we hear most often before an account is opened or a wallet record is queried. They explain what we collect, why verification appears, how device data works and how you can contact us. If your situation involves a specific account event, include its date and reference so our team can locate the correct record.

The detik356 Privacy Policy covers personal details, phone verification, device signals, cookies, support records and payment references connected with your account. It also explains retention, security, correction requests and the circumstances in which we may share data to operate or protect the service.

Phone verification helps connect an account request with the person controlling the registered number and reduces mistaken access. We may request it before account entry or before discussing a data request. Never send us your password, PIN or one-time code.

No wallet PIN should be sent to us. Our Privacy Policy permits records such as a DANA or QRIS reference, amount status and transaction date when needed to match an account event. Those details help support trace a payment without receiving your private wallet credential.

We may use browser, device and session signals to keep your login active, recognise an unusual access attempt and protect account records. The Privacy Policy treats these signals as security and service data, not as a reason to request unrelated details from your phone or computer.

Yes. Contact us through the privacy route with your registered phone number and the detail you believe is inaccurate. We verify account ownership before changing a record, explain any restriction that applies, and confirm the result. Access and eligibility depends on local law.

We retain payment references for as long as they support account security, dispute handling, service administration or legal duties. This can include a bank transfer, virtual account, OVO or GoPay status record. When the purpose ends, we remove or anonymise the record where permitted.

Use the account support route and label your message as a Privacy Policy request. Add your registered phone number, request type and relevant date, while leaving out passwords and wallet PINs. We use that information to verify ownership and locate the correct account record.