Reference

Privacy Policy for Your tunas4d Account

Our Privacy Policy explains how tunas4d handles the details connected with your account, device, login checks and payment records.

Account dataWallet recordsDevice choicesPolicy requests

Browse Our Lobby Read FAQ

What Our Privacy Policy Covers

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

This Privacy Policy covers information you provide when opening or maintaining an account, including contact details used for phone verification and records created when you sign in. It also covers device signals from the browser you use, such as session data, cookies and security checks that

1
help connect your visit with the right account. Payment records can show a selected rail, transaction reference and status, including DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We use these records to match deposits, investigate an unsettled receipt and answer an account request.
2
We keep account and transaction records for as long as needed for the stated service, security and legal purposes, then remove or anonymise them when appropriate. Where access is discussed, it depends on local law; we do not use this page to promise eligibility. You may
3
ask us what data we hold, request a correction, or ask how a record is being used through the support path connected to your account.

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

REQUEST A CHECK

How To Contact Us About Privacy

A clear support path matters when you need a copy, correction or explanation of personal data.

Account request Use the support route beside your signed-in account to ask what personal data we hold. We may ask for an account detail or phone verification so we do not disclose records to the wrong person.

Payment record For a privacy question involving DANA, OVO, GoPay or QRIS, share the transaction reference and date rather than a PIN. That lets us locate the relevant record without requesting unnecessary wallet credentials.

Correction path If your contact detail or account record is inaccurate, tell us which field needs changing and why. We may compare the request with your account step before applying a correction or explaining why a record must remain.

HANDLING DETAILS

Six Practical Privacy Safeguards

Privacy work is part of the account flow, not a separate promise hidden from you. We separate sign-in details from payment references where the service allows, use session controls on the mobile…

Data collection

We collect account details you submit, login events, device session signals and payment references needed for account servicing. A DANA or QRIS reference identifies a transaction status; it does not give us your wallet PIN.

Cookies and sessions

Our mobile browser path may use cookies or local session storage to keep your sign-in state and security checks working. Clearing browser data can end the session, so you may need to complete phone verification again.

Account security

Keep your password, phone verification code and wallet credentials private. We use account checks when handling sensitive requests, and support will not need your DANA, OVO or GoPay PIN to locate a receipt.

Payment separation

A payment record can include the chosen rail, reference, amount status and timing needed for reconciliation. For bank transfer or virtual account questions, we use the reference you provide rather than asking for unrelated personal details.

Retention approach

We retain records while they serve account security, transaction reconciliation, support handling or a legal need. When a record no longer has that purpose, we assess removal or anonymisation rather than keeping it without a reason.

Change requests

You can ask us to correct account data, explain its use or clarify a retention decision. Send the request through the account support path with enough detail to find the record, while leaving passwords and wallet PINs out.

Privacy Policy Answers For tunas4d

These Privacy Policy answers address the searches we hear most often before account access: what we collect, why a device can appear in a record, how wallet references are handled and where to request a change. Read them alongside the sections above, then use the support path connected to your account if your situation needs a record-specific response. Where access or eligibility applies, it depends on local law.

It covers account details, phone verification, sign-in events, browser session data, cookies, support messages and payment references. The Privacy Policy explains why each category may be needed for account security, transaction matching, support handling or a legal purpose.

Do not send a wallet PIN to us. Our records may contain a payment rail, reference, timing and status for DANA, OVO or GoPay, but the Privacy Policy does not ask you to share the credential that authorises your wallet.

A device and browser can create session, security and cookie records when you sign in. These details help connect activity with the correct account and detect an unusual session. Clearing browser storage may end your session and prompt phone verification again.

Use the support route beside your account and ask for the personal data connected with your account. Include the relevant phone or account detail so we can check identity before responding, and never include your password, verification code or wallet PIN.

Yes. Tell us which account field is inaccurate and provide the corrected detail through the account support path. We may complete a phone verification step before changing it, especially where the correction could affect account access or a payment record.

The Privacy Policy does not set one universal period for every record. We keep payment references while they support reconciliation, account security, support handling or a legal need, then assess deletion or anonymisation when that purpose ends.

Yes, it describes how we handle data connected with your account when you use the service in supported Indonesia regions. Eligibility and access depend on local law. If you are unsure about a data request, contact us through the account support route.

Privacy Policy for Your tunas4d Account

How To Contact Us About Privacy

Six Practical Privacy Safeguards

Data collection

Cookies and sessions

Account security

Payment separation

Retention approach

Change requests

Privacy Policy Answers For tunas4d

01 What does the tunas4d Privacy Policy cover?

02 Does tunas4d store my DANA, OVO or GoPay PIN?

03 Why does the Privacy Policy mention my device?

04 How can I request a copy of my tunas4d data?

05 Can I ask tunas4d to correct my account data?

06 How long does tunas4d keep payment records?

07 Does the Privacy Policy apply to access in Indonesia?

Related Pages