Reference

tunas4d Privacy Policy For Your Account Data

Our Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the lobby and cashier path.

Account dataWallet recordsDevice choices
tunas4d tunas4d Privacy Policy For Your Account Data
POLICY HELP

Where To Ask About Privacy Policy

A clear support route helps you act on this Privacy Policy without guessing which team to contact. Start from the account help area when a sign-in record, wallet status or receipt needs checking, then include the email or phone detail attached to your account. We use the details you send only to locate the relevant record and respond to your request.

Team online

Account access

Ask us to check account data when phone verification does not match your record. Include your registered contact detail so we can identify the correct account without requesting your wallet password.

Wallet status

For DANA, OVO, GoPay, QRIS or bank transfer queries, send the payment reference from your account path. We use that reference to trace status without asking for a private wallet credential.

Privacy requests

Request a copy, correction or removal review through our policy contact route. Tell us which account detail is involved, and we will check identity before changing or releasing personal data.

DATA CONTROLS

Six Controls Behind Our Data Handling

We keep this policy practical by tying each data action to an account event you can recognise: registration, phone verification, wallet status, sign-in or a support request.

Collected fields

We may collect your contact details, verification result, transaction reference, device type and sign-in records. These fields support the account path and wallet reconciliation rather than unrelated profiling.

Cookies and sessions

Cookies can keep a session open, remember a language choice and help connect a page request to your account. You can adjust browser cookie settings, though some account steps may then need repeating.

Account protection

Phone verification is checked before account access, while device and connection signals can flag unusual sign-ins. Never send us a wallet password or one-time security code in a support message.

Mobile behaviour

On a phone, the lobby and cashier path may use the same browser session. Our records can show the device and browser used, helping us investigate a repeated login or wallet-status problem.

Retention purpose

We retain account and transaction records for as long as needed for account administration, security checks, support history and legal duties. When a record is no longer needed, we remove or separate it.

Your changes

You can ask us to correct contact details, request a copy of relevant data or ask about deletion. We verify the account holder first and explain any record that must remain for legal reasons.

Privacy Policy Questions For Indonesian Accounts

These Privacy Policy answers focus on the account and wallet questions we hear most often from people using DANA, OVO, GoPay, QRIS or bank transfer. If your situation is not covered, use the policy contact route with your account reference and we will direct the request.

It covers account details, phone verification, device and browser records, cookies, wallet references, support messages and retention. It explains why we use each category and how to request access or correction.

Phone verification helps connect you with the correct account before access is provided. It also reduces mistaken changes when a DANA, OVO, GoPay or QRIS status needs checking.

Yes. The Privacy Policy covers payment references and status details linked to DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account records. Wallet passwords are not requested.

You can request a copy of personal data connected with your account through our policy contact route. We first check account ownership, then explain the available records and any legal retention requirement.

Send a correction request with the account detail that needs changing. We verify your identity, compare the request with the account record and update eligible fields after the check is complete.

We keep records for account administration, security checks, support history and legal duties for the period needed for those purposes. After that period, records are removed or separated where appropriate.

Yes. Access or eligibility depends on local law. Where local law permits, you can ask about access, correction or deletion; some records may remain when a legal duty requires retention.