Reference

Open tuna68 Privacy Policy

tuna68 Privacy Policy explains how we collect, use, protect and remove data connected with your account, mobile browser session and wallet checks.

Clear data purposesWallet status contextPhone verification detailIndonesia access wording

Explore Our Lobby Read FAQ

Browse Privacy Policy Wallet Rules

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

Our Privacy Policy covers the details created when you open an account, verify your phone, sign in from a mobile browser or desktop, and ask us to check a wallet status. We may use account identifiers, contact details, device signals, session records and payment references to

1
keep access working and match a receipt to the correct account. DANA, OVO, GoPay and QRIS can appear in those records, while bank transfer or virtual account references may be handled when you choose those rails. We use this material for account access, security checks, service
2
operation and required legal handling. Where local law permits, we provide access to the service; otherwise, eligibility may be restricted. The current policy applies to data collected through our site and support route.

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

CONTACT PATHS

Reach Support About Privacy

A privacy question should have a clear next step, especially when your login or wallet status is involved.

Account data request Ask us to locate the personal data connected with your tuna68 account. Include your registered phone detail and the request type, such as access, correction or removal, so we can begin the right verification step.

Wallet record question When a DANA, OVO, GoPay or QRIS receipt does not match your account view, contact us with the transaction reference and approximate time. We use those details to check status without asking for your wallet password.

Privacy clarification If a cookie notice, mobile session record or phone check is unclear, send us the page or step that raised the question. Our support route can explain the purpose and identify what can be changed under the policy.

DATA PRACTICES

Check How tuna68 Handles Data

We handle privacy through the same account path you use to reach the lobby: identify the account, check the device session, confirm the requested action and record the result.

Data we collect

We may receive your account name, phone detail, sign-in records, device and browser signals, support messages and payment references. We collect these categories when needed for access, security, wallet status checks or a request you send us.

Cookies and sessions

Cookies and related session tools help keep your mobile browser or desktop session connected to the correct account. They can remember an access state and support security checks; clearing them may require you to sign in and verify again.

Account security

Phone verification is required before account access, and device signals can help us spot an unusual sign-in pattern. We do not need your wallet password to compare a DANA, OVO, GoPay or QRIS payment reference.

Retention decisions

We retain account, security and payment-reference records only for the period needed for the stated purpose, account support and legal duties. When a record is no longer needed, we remove it or separate it from direct account identification.

Requesting changes

You can ask us to correct an account detail, provide a copy of relevant data or remove data where the policy and local rules allow. We verify the request through the registered account path before making a change.

Policy contact

For a Privacy Policy question, use the support route and describe the data or account step involved. We may ask for a registered phone detail, transaction reference or other limited proof so we do not disclose data to the wrong person.

Ask About Privacy Policy Access

These Privacy Policy answers focus on the searches we hear most often from Indonesian account holders. They explain what happens around phone verification, mobile sessions, local wallet references, cookies, retention and data requests. The policy does not change the need to follow local eligibility rules: access depends on local law, and we may restrict a request when the required account check cannot be completed.

It covers data linked with your account, phone verification, sign-in sessions, device and browser signals, support messages, cookies and payment references. It explains why we use each category for account access, security, wallet status checks, service operation and applicable legal handling.

We use a DANA or QRIS payment reference to connect a receipt with the correct account and check its status. We do not need your wallet password for that comparison. The reference may be retained for support, security and legal purposes described in the Privacy Policy.

Phone verification helps us confirm that an account access request comes through the registered account path. It can also reduce mistaken disclosures when you ask for data changes. We use the verification detail for that security purpose and do not treat it as permission to request your wallet password.

Yes. Send a request through our support route and state whether you need access to relevant data, a correction or removal. We first verify the registered phone or account detail, then assess the request under the Privacy Policy and local rules before responding.

Cookies and session records help keep your mobile browser connected to the right account and can support security checks between sign-in steps. If you clear them, you may need to sign in and complete phone verification again. The Privacy Policy explains their operational purpose.

We keep account, security and payment-reference records for as long as needed for the stated service purpose, support handling and applicable legal duties. Once a record is no longer needed, we remove it or separate it from direct account identification where practical.

Yes, you can read the Privacy Policy before opening an account, but service eligibility depends on local law. If access is restricted, we may also need to pause an account or request until the required legal and security checks are complete.

Open tuna68 Privacy Policy

Reach Support About Privacy

Check How tuna68 Handles Data

Data we collect

Cookies and sessions

Account security

Retention decisions

Requesting changes

Policy contact

Ask About Privacy Policy Access

01 What does the tuna68 Privacy Policy cover?

02 How does tuna68 use my DANA or QRIS data?

03 Why is phone verification part of the Privacy Policy?

04 Can I request a copy or correction of my data?

05 How do cookies affect mobile access to tuna68?

06 How long does tuna68 keep account data?

07 Where local law permits, can I access the policy and account?

Related Pages