Reference

terbang168 Privacy Policy for Your Account Data

terbang168 Privacy Policy tells you what we collect, why we use it and how you can ask us to correct or remove eligible records.

Account clarityWallet recordsCookie choicesAccess requests
terbang168 terbang168 Privacy Policy for Your Account Data
ACCOUNT HELP PATH

Where To Ask About Your Privacy

A clear support route matters when you want to ask about a Privacy Policy request, a phone verification record or a wallet reference. Use the support link shown beside the cashier path and include the email or phone connected to your account. We can then locate the relevant record without asking you to send a full wallet password or payment credential.

Team online

Privacy request

Send a request through our support route with your account contact and the change you want. We use those details to locate the correct Privacy Policy record.

Wallet reference

For DANA, OVO, GoPay or QRIS questions, include the transaction reference and date only. Do not send your wallet PIN, one-time code or full banking password.

Login concern

If a sign-in or phone verification record looks wrong, tell us through the account help path beside the cashier area. We may ask for a safe ownership check.

SECURITY PRACTICE

Cookies, Retention And Account Security

We handle privacy requests as account operations, not as a general marketing message. Our process covers the data created when you open access, sign in from a mobile browser, select a wallet…

Collection at account opening

We use the contact details and phone verification result you provide to establish account access, respond to account requests and reduce the risk of another person using your details.

Wallet records

A DANA, OVO, GoPay or QRIS reference helps us match a payment status with your account. We use the reference for reconciliation rather than requesting your private wallet password.

Device signals

When you move from mobile login to the lobby, we may record device and session signals for security. These signals help us spot unusual access without reading unrelated phone content.

Cookie choices

Cookies can keep your session and selected settings available between pages. You can manage browser cookie controls, although disabling some cookies may affect account access or request handling.

Retention checks

We keep account, payment-reference and support records only for operational, dispute or legal needs described by our Privacy Policy. When a retention need ends, we remove or de-identify the record.

Requests and corrections

You can ask us to access, correct or clarify eligible personal data through the support route. We verify account ownership first, then explain the action, timing and any legal reason for a limit.

Privacy Policy Questions Before Opening An Account

These Privacy Policy answers cover the practical questions you may have before opening access from Indonesia. We keep the wording tied to account records, device sessions, local wallets and support requests. If your situation is not covered, use the support path beside the cashier area and provide only the minimum account detail needed for us to respond.

It covers account details, phone verification, device and cookie signals, wallet references, support requests, retention and eligible access or correction requests connected with your account.

We use the verification result to help establish account ownership, protect sign-in access and investigate an access concern. We do not ask you to share your one-time code with support.

Yes. We may retain a DANA or QRIS payment reference, status and time so we can match account activity. Your wallet PIN and full banking password should not be sent to us.

You can ask through the support route beside the cashier path. Include your account contact, and we will verify ownership before explaining which eligible records can be supplied.

Send the correction request through account support and identify the record, such as a phone detail or payment reference. We may request a safe ownership check before changing it.

Retention depends on the operational, dispute or legal reason for keeping a record. Once that reason ends, we remove or de-identify eligible data under our Privacy Policy process.

You may contact us with a privacy request, but the available action depends on local law. We will explain the applicable route, ownership check and any reason a request cannot proceed.