Reference

terang288 Privacy Policy for Your Account

Our terang288 Privacy Policy explains what account, device and wallet records we collect, why we use them, and how you can ask about them.

Account clarityWallet dataYour privacy choices

Explore Our Lobby Read FAQ

How Wallet Data Is Used

terang288 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We use payment details only to identify the account action involved, confirm status, prevent mismatches and answer a support request. For DANA, OVO, GoPay and QRIS, this can include a wallet reference, amount, time, status and receipt details supplied during an account transaction. Bank transfer and

1
virtual account records may include the bank rail, such as BCA, BRI, Mandiri or BNI, together with the reference needed to match your account. We do not need the contents of your private wallet beyond what the payment rail sends for status handling. Our Privacy Policy
2
applies where local law permits and may be adjusted when a local rule requires a different handling period or access right. You can ask us to explain a wallet record without sending your full password or private wallet PIN.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT PATHS READY

Policy Help Beside Your Wallet

A privacy question should not disappear inside a general account request. We keep the route practical: tell us whether your question concerns login, a wallet reference or a record shown on your…

Account request Ask about a phone verification record or account detail through our support route. We may request an account identifier so we can separate your request from another terang288 account.

Wallet receipt For DANA, OVO, GoPay or QRIS questions, send the payment reference and status shown on your receipt, not your wallet PIN. We use that reference to check the matching record.

Access concern If a mobile browser session or login check appears unfamiliar, contact us with the device path and time shown. We can explain the recorded event and help protect account access.

CONTROL OVER RECORDS

Account Data Controls at terang288

Our handling process separates account access from payment matching and from device protection. That separation helps us answer a Privacy Policy request with a specific record instead of sending a broad account…

Account records

We may hold your account identifier, phone verification result and selected account settings to operate access. These records help us distinguish your request from an unrelated account.

Device signals

A mobile browser can send technical signals such as session time, browser type and security events. We use these signals to investigate unusual access, not to read private device content.

Cookie choices

Cookies can keep a session active, remember a language or connect a page visit to a security check. You can manage browser cookie settings, though some account steps may then need repeating.

Wallet matching

A DANA, OVO, GoPay or QRIS reference is used to match a status or receipt with your account. We do not ask you to share a wallet PIN in a privacy request.

Retention checks

We retain records only for the period needed for account security, payment reconciliation, dispute handling or a legal requirement. When that need ends, the record is removed or separated from direct account use.

Change requests

You can ask us to correct an account detail, explain a device event or request access to a record. Include your account identifier and the exact matter so we can assess the request.

Privacy Policy Questions for Indonesia

These answers cover the questions we expect before an account step: what we collect, how wallet references work, what cookies do and how you can contact us. If your case involves a specific record, use the support path above and avoid sending passwords or wallet PINs.

It covers account details, phone verification, device signals, cookies, wallet references, retention and requests for access or correction. It also explains how local requirements may affect handling where local law permits.

No. We use payment references and status details needed to match an account transaction. Do not send a DANA, OVO, GoPay or QRIS PIN when asking us to check a receipt.

Technical browser and session signals help us identify an unusual login or protect an account after phone verification. They do not give us access to private files, messages or unrelated device content.

Yes. Contact us through the account support route with your account identifier and a clear request. We may verify account control before discussing records, so another person cannot obtain your details.

Send the specific account detail, wallet reference or device event you believe is wrong. We will check the source record and explain whether it can be corrected, retained or separated for a legal reason.

Retention depends on the purpose, such as payment reconciliation, account security, dispute handling or a legal requirement. When the purpose ends, we remove the record or reduce its link to your account.

You can open this Privacy Policy from the terang288 brand home before completing an account step. If wording or local requirements change, the page will show the current policy text.

terang288 Privacy Policy for Your Account

Policy Help Beside Your Wallet

Account Data Controls at terang288

Account records

Device signals

Cookie choices

Wallet matching

Retention checks

Change requests

Privacy Policy Questions for Indonesia

01 What does the terang288 Privacy Policy cover?

02 Does the Privacy Policy store my DANA or OVO PIN?

03 Why does terang288 record my mobile browser?

04 Can I ask for my account data?

05 How can I correct a Privacy Policy record?

06 How long does terang288 keep payment records?

07 Where can I read the current Privacy Policy?

Related Pages