Reference

t6com Privacy Policy for Your Account

t6com Privacy Policy explains how we handle the account, device and wallet details you provide while using our Indonesia service.

Clear data purposesWallet status contextRequest accessPolicy contact path
t6com t6com Privacy Policy for Your Account
CONTACT THE TEAM

Get Help With a Privacy Request

A clear support route helps you ask what we hold, why we use it or how to correct an account detail.

Account request Use the account support path when you want to ask for a copy of personal data, check the purpose of a phone verification record or correct a name or contact detail. Include your account phone number so we can connect the request to the right profile.
Wallet record For a DANA, OVO, GoPay or QRIS record, provide the payment reference and approximate date shown on your receipt. We use that narrow detail to check the wallet status without asking you to reveal a password, PIN or complete payment credential.
Access concern If a login or device change raises a privacy concern, tell us the device type and the time you noticed it. We can review the account security event, explain the next account step and direct you to a safer sign-in path.
DATA HANDLING

What We Do With Account Details

Privacy Policy choices should be easy to connect with real account actions. We separate contact details, payment references and technical security events so a support request can be checked without exposing unrelated…

Account data

We use your account phone number and submitted account details to create your profile, complete phone verification and respond to requests tied to that profile. We do not need your password in a support message, so leave passwords and one-time security codes out of every request.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a receipt with an account status. We check the transaction detail needed for reconciliation and support, rather than asking you to send a wallet PIN or full credential.

Cookies

Our site may use cookies or similar browser storage for session continuity, account security and required page settings. You can inspect or clear these controls in your browser, although removing necessary session data may sign you out or interrupt an account step.

Device security

When you sign in from a phone or desktop browser, we may record device type, access time and security events. These signals help us investigate an unfamiliar login and protect the account; they are not a reason to request your private device passcode.

Retention

We keep account, support and payment records only while they serve the stated account, security, reconciliation or legal purpose. When a record is no longer needed, our handling follows applicable retention requirements and the access rules that depend on local law.

Your request

You can ask what personal data is linked to your account, request a correction or ask how a record is used. Send the request through account support with enough detail to identify you, but do not include a password, PIN or complete security code.

Answers About t6com Privacy Policy

These Privacy Policy answers focus on the account steps you are most likely to question before opening an account or returning to the lobby. They explain the practical records connected with phone verification, mobile access, cookies and local wallet receipts. If your question is not covered, use the account support path and describe the specific record or action you want us to check.

The t6com Privacy Policy covers account details, phone verification, support messages, payment references, cookies and device security events. We use these records to provide account access, check wallet status, investigate sign-in concerns and respond to requests. Access and eligibility depends on local law.

We use your phone number to create and identify your account and to complete phone verification before account access. It also helps support connect a Privacy Policy request with the correct record. Do not include your password or one-time security code in a message.

Yes. A DANA or QRIS receipt reference can be part of the account record when you ask us to check a payment status. We use the reference for reconciliation and support, while you should keep your wallet PIN, password and full security credentials private.

Use the account support path near the cashier area and state that you are making a Privacy Policy data request. Include your linked phone number and the record you want checked, such as a login event or support message. We may need account details to verify the request.

You can ask us to correct an inaccurate account detail through support. Mention the field that needs changing and provide the updated value without sending a password or payment PIN. We will review the request against the account record and apply the applicable process.

The Privacy Policy applies whether you sign in from a mobile browser or desktop. We may record device type, session details and security events to protect access. Browser cookies can support the session, and clearing necessary storage may sign you out or interrupt verification.

We retain account, payment and support records while they are needed for account operation, security checks, reconciliation or a legal requirement. The exact period can depend on the record and local rules. You can ask support which category applies to a specific account record.