Reference

Privacy Policy for tv888 account data

Our Privacy Policy shows how tv888 handles the details linked to your account, device and wallet choices, including DANA and QRIS.

Account dataWallet recordsDevice choicesPolicy requests
tv888 Privacy Policy for tv888 account data
ACCOUNT HELP ROUTE

Get policy help through your account

A clear support route matters when your account data or wallet record needs attention.

Account access If you cannot reach the account area, use the support path displayed at sign-in and describe the step that stopped. We can then address access data without requesting your password.
Wallet records For a DANA, OVO, GoPay or QRIS record, include the payment rail and visible status from your account. This helps us identify the relevant data entry and respond accurately.
Change request To correct a name, phone detail or other account field, send the request through account support. We may ask for a verification step before changing data tied to account security.
CONTROL OVER DETAILS

Your device and account data controls

We keep this policy practical by linking each data choice to an account action you can recognise.

Data we receive

We receive details you enter during account creation, verification and support, plus records from sign-in, device use and payment status. We use these categories only for the account purposes described in this Privacy Policy.

Cookies and storage

Browser cookies or local storage can keep a session recognised and preserve basic choices. You can manage browser settings, but removing them may require another sign-in or affect account access.

Account security

We use sign-in checks and account verification steps to reduce access by the wrong person. Never send your password through support, even when asking about DANA or QRIS records.

Retention periods

We retain account, payment and support records for as long as needed for account operation, security checks or legal duties. When a record is no longer needed, our handling follows the policy.

Who receives data

Payment and technical service partners may receive limited data when needed to process a selected rail or keep the account working. We do not give them unrelated account details.

Requesting changes

You can ask us to correct, access or clarify personal details through the signed-in support route. State the account field involved, and we may verify ownership before responding.

Privacy Policy questions Indonesian account holders ask

These answers address the policy points you are most likely to check before opening an account with tv888. They cover account creation, payment records, mobile sessions, cookies, retention and requests for access or correction. If your question is specific to a DANA, OVO, GoPay or QRIS entry, use the account support path with the visible status.

The tv888 Privacy Policy covers account details, verification, device sessions, cookies, support records and payment status connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We need account details to create and protect your profile, complete verification steps, respond to support requests and connect a payment status with the correct account. Access depends on local law.

Yes. The Privacy Policy covers mobile browser sessions as well as desktop access. Device and browser data can help maintain sign-in security, recognise a session and diagnose an account access issue.

We use DANA and QRIS records to identify the selected payment rail, match visible status with your account and address support questions. Only the data needed for those steps is handled.

Yes. Use the signed-in support route and name the field you want corrected, such as a phone detail. We may verify account ownership before changing data connected with security.

We keep account, payment and support records while they are needed for account operation, security checks or legal duties. The Privacy Policy explains retention by purpose rather than one universal period.

Sign in and open the support path shown near your account or cashier details. Include the relevant policy section, payment rail or account step, while avoiding passwords and unnecessary sensitive data.