Reference

Privacy Policy For Your tt678 Account

The tt678 Privacy Policy explains how we handle the details linked to your account, including contact data, device signals and records connected with DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesRequest access
tt678 Privacy Policy For Your tt678 Account
CONTACT PATHS

Privacy Help Beside Account Support

A privacy question should not get lost inside a wallet status request. We keep a direct support path for questions about your account data, cookie choices…

Account data request Ask us to confirm which account details we hold, such as your registered phone…
Wallet record check If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the date, rail…
Access and cookie help For a cookie choice, mobile browser issue or sign-in concern, tell us your device…
HANDLING DETAILS

Inside tt678 Data And Security Steps

Privacy work follows the account actions you can see: phone verification, sign-in, wallet status checks and support contact.

Account details

We may hold your account identifier, phone verification result, sign-in events and support correspondence. These details help us recognise your account, investigate access problems and answer a Privacy Policy request. We do not need your DANA, OVO or GoPay wallet password.

Device signals

A mobile browser can send device, browser and connection signals used to detect unusual access or repeated verification attempts. We use these signals for account security and troubleshooting, including when the lobby behaves differently on a phone than on a desktop browser.

Cookies

Cookies can keep a signed-in path working, remember a selected setting and help us understand security events. You can clear or block them through your browser controls. Some account functions may require a necessary cookie, and we explain its purpose when support investigates access.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may produce a reference, amount status or timestamp in the account record. We use that limited payment detail to match a cashier event and resolve a receipt question, rather than storing wallet passwords.

Retention steps

We keep personal data only while it serves account operation, security checks, dispute handling or a legal need. When a retention period ends, we remove the record or separate it from direct account identifiers. A support request can ask what category remains and why.

Changes and contact

You can ask to access, correct or delete eligible personal details through the support path. Tell us the account contact and the change requested; we verify ownership before acting. If the Privacy Policy changes, we place the updated wording on this page with its effective date.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and payment questions we hear most often in Indonesia. They explain what to send, what we use for security and how to request a change without exposing your wallet credentials. If your question concerns eligibility or access, it depends on local law and applies where local law permits.

The tt678 Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages, security events and payment references. It applies when you open an account, sign in, contact us or use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

No. Our Privacy Policy does not require your DANA or GoPay wallet password. We may receive a payment reference, status or timestamp needed to match an account event. Do not include a wallet password, one-time code or full security credential in a support message.

Use the support path while signed in and ask for an account data request. Include your registered phone detail and the categories you want checked, such as verification or cookie records. We verify account ownership first, then explain the available data and any lawful restriction.

Yes, you can ask us to correct inaccurate details or delete eligible personal data through support. State the requested change clearly and identify the account contact. Some records may remain for security, dispute handling or legal needs, and our Privacy Policy explains that reason.

Device and browser details help us detect unusual sign-in behaviour, repeated phone verification attempts and access faults on mobile or desktop. We use those signals for security and troubleshooting, not to request wallet credentials. You can mention your device path when reporting a problem.

Cookies can support sign-in continuity, selected settings and security checks. You can clear or block them through your browser controls, although a necessary cookie may be required for account access. Our Privacy Policy describes the purpose of cookies used on the tt678 site.

Access and eligibility depend on local law. The Privacy Policy applies where local law permits, while account handling remains subject to the rules that apply to your location. If you need a location-specific answer, contact support and state your Indonesian region without sending sensitive wallet details.