Reference

truk88 Privacy Policy, Clearly Explained

Our Privacy Policy shows what truk88 collects, why we use it and how you can ask about your account data before opening an account.

Account dataWallet detailsCookie choicesYour requests
truk88 truk88 Privacy Policy, Clearly Explained
CONTACT ROUTES

Get Privacy Policy Help Through Your Account

A clear contact route matters when you want to ask about the Privacy Policy rather than troubleshoot a game screen. Start from your signed-in account and include the phone number or email connected with your request, so we can locate the correct record without asking for unrelated wallet credentials. If your question follows a DANA, OVO, GoPay or QRIS status check, keep the payment reference ready and use the account-help path close to the cashier area.

Team online

Account help

Send a Privacy Policy question through the account-help path after login. Include your registered phone detail and the specific request, such as a copy, correction or explanation of stored account data.

Wallet context

For a privacy question linked to DANA, OVO, GoPay or QRIS, share only the payment reference and account identifier requested by support. Do not send a wallet PIN, password or full security code.

Status follow-up

If a data request is connected to a pending wallet status, support can use your account path and receipt reference to separate the privacy question from the payment record without requesting unrelated device content.

ACCOUNT SAFETY

How truk88 Handles Your Data Choices

We keep this policy practical by tying each data use to an account action you can recognise: phone verification, login, wallet status or a support request.

Collection

We collect details you enter for an account, the phone verification result, device and browser signals from sign-in, and references attached to a requested DANA, OVO, GoPay, QRIS or bank transfer status.

Purpose

We use account data to complete the access step you request, match support with the right record, check wallet status, protect sign-in activity and respond to a Privacy Policy request about your information.

Cookies

Cookies may keep a mobile browser session available or help us understand whether the Privacy Policy page loads correctly. You can manage browser cookie settings, although changing them may affect account-path continuity.

Security

Keep your password, phone verification codes and wallet PIN private. We may compare sign-in details with the account record when activity looks unusual, but support does not need your private wallet credential to answer a policy question.

Retention

We keep records only while they support account operation, security, payment reference checks or a valid legal need. When a retention reason ends, we assess deletion or anonymisation rather than keeping every record without purpose.

Your request

Ask for a copy, correction, explanation or deletion assessment through account help. Tell us which record you mean and confirm account ownership; we may need that step before changing or disclosing personal data.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions you may search before creating an account or sending a wallet-status message. We keep the examples tied to real account actions, including phone verification, mobile browser access and local payment references. If your situation concerns eligibility or location, access depends on local law, and support can explain which account-data question we can address through the available contact path.

The truk88 Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages and payment references connected with your requests. It explains why we use those details, how retention works and how you can ask for a copy, correction or deletion assessment.

We do not need your wallet PIN to answer a Privacy Policy question or check an account reference. For DANA, OVO, GoPay or QRIS activity, share only the payment reference and account detail requested through support. Keep your PIN and verification code private.

Phone verification connects the account-access step with the correct account and helps us respond to a personal-data request safely. We may use the verification result with login and support records, but a policy request still needs only the details required to identify your account.

The Privacy Policy covers limited device and browser signals created when you sign in through a mobile browser or desktop path. These signals can help maintain a session and identify unusual access. They are considered alongside account details, not treated as a record of unrelated device activity.

Use the signed-in account-help path and state whether you want a copy, correction or explanation. Include the registered phone detail and describe the record, such as a QRIS reference or support message. We may confirm account ownership before handling the request.

You can ask us to assess deletion through account help. We first identify the requested records and check whether account security, payment reference checks or a legal duty requires retention. Where removal is possible, we handle the request for the relevant data rather than unrelated records.

The Privacy Policy explains our data handling for the website and mobile browser path, but account access depends on local law. If you are in Indonesia, including Denpasar, use the policy contact route for questions about your records and location-specific eligibility wording.