Reference

tri88 Privacy Policy for Your Account

tri88 Privacy Policy shows how we handle the details behind your account, phone verification, wallet activity and device access.

Account dataWallet recordsDevice choicesYour privacy rights
tri88 tri88 Privacy Policy for Your Account
CONTACT ROUTES

Where to Ask About Account Data

A clear support path helps you act on this Privacy Policy without searching through unrelated pages. Use the account support route when you need a copy of your stored details, a correction to your phone record, or clarification about a DANA or QRIS reference. Include the account contact you used so we can verify the request before discussing private data.

Team online

Access request

Ask us to identify the account data connected with your verified phone contact. We check ownership first, then explain the available format and any lawful reason a detail cannot be released.

Wallet question

If an OVO, GoPay, DANA or QRIS status appears beside the wrong account activity, send the transaction reference through support so we can compare the payment record.

Account correction

Tell us which profile detail needs changing, such as a phone number or contact field. We may request a fresh verification step before applying a privacy-related account update.

SECURITY PRACTICES

Six Controls Around Your Account Data

Privacy depends on practical handling, not a statement alone. We separate account details from payment confirmations where our records allow, restrict staff access by task, and use session checks when a sign-in…

Purpose-based collection

We collect contact, verification, device and transaction details for account access, payment matching, security checks and support. We do not ask for a wallet password to match a DANA or bank transfer record.

Cookie choices

Our pages may use necessary cookies for sessions and optional cookies for settings or performance. You can clear them through your browser, although removing session cookies may require you to sign in again.

Account security

Phone verification, session monitoring and account checks help us respond to unusual access. Keep your sign-in details private and contact support if a device path does not match your activity.

Payment separation

For QRIS, OVO, GoPay, DANA and bank transfer activity, we keep the reference and status needed for reconciliation. Payment confirmation does not give us access to your wallet credentials.

Retention review

We keep account and transaction records for active service, dispute handling and legal requirements. When a record is no longer needed for those purposes, we remove or anonymise it under our retention process.

Rights requests

You can request access, correction or deletion through the account support route. We verify the request belongs to you, explain the result, and apply any restriction required by local law.

Privacy Policy Questions About tri88 Accounts

These Privacy Policy answers focus on the account actions you are most likely to search for before opening an account. They cover phone verification, wallet records, cookies, device access, deletion and the route for asking us to check your personal data.

It covers account contact details, phone verification, device and session signals, cookies, payment references, support requests, retention and your rights to request access, correction or deletion.

No. Our Privacy Policy describes records such as the selected rail, transaction reference, amount and status. We do not need your DANA or OVO wallet password to match a payment.

Phone verification helps connect the account to the contact you provide and supports account recovery and security checks. We use the result for access control, subject to where local law permits access.

We may record browser type, session time, device signals and related security events. These details help us identify unusual sign-ins and investigate an account access question without reading your private device content.

Send a deletion request through the account support route and include your verified account contact. We confirm ownership first, then assess the request against active service, dispute and legal retention needs.

Yes. Tell support which contact or profile detail is inaccurate, such as a phone field, and provide the account verification requested. We record the correction request and update eligible data.

Yes. Access and eligibility depend on local law. Where local law permits, we provide a response to an access request after checking ownership and may limit details protected by a legal duty.