Reference

Open toz288 Privacy Policy With Clarity

Our Privacy Policy explains what toz288 collects when you create an account, sign in from a phone or desktop, check wallet status, and contact support about access.

Clear data purposesWallet-linked account recordsRequest and access path
toz288 Open toz288 Privacy Policy With Clarity
CONTACT PATH

Check Your Privacy Request Route

A clear contact route helps you ask about the Privacy Policy without sending sensitive details through an unsuitable channel.

Account access request Ask us to explain account data connected with your sign-in, phone verification, device activity…
Payment record question For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account record, provide the…
Cookie or correction request You can ask us to explain cookie use, correct an inaccurate account detail, or…
DATA PRACTICE

Explore How We Handle Your Records

The Privacy Policy follows the path your data takes through account creation, sign-in, wallet matching, support, and account closure.

Account data

We may hold your contact details, account identifier, verification state, sign-in history, and settings so we can maintain access and answer account questions. We use these records for the stated service purpose and do not treat an account opening as permission for unrelated use.

Cookie controls

Cookies can keep your session available, remember selected settings, and help identify unusual sign-in behaviour. You can manage browser cookie settings on your device, although removing required cookies may interrupt access until you sign in again and complete the account checks.

Wallet matching

When a wallet or bank reference is linked to an account, we use the reference, amount status, and timing needed to reconcile that record. DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri, and BNI details remain tied to the transaction purpose.

Account security

We use phone verification, sign-in records, device signals, and other account checks to protect access. Never disclose your password or one-time code to a contact claiming to represent support. A privacy response may require confirmation through your existing account step.

Retention period

We keep personal and transaction records only as long as needed for the purposes described in this policy, including security, account queries, dispute handling, and legal duties. When a record is no longer needed, our handling follows deletion or anonymisation requirements.

Changes and requests

You can ask what data we hold, request a correction, question a processing purpose, or ask about deletion where the law allows it. Tell us which account record is involved; we may verify ownership before taking action or explaining a restriction.

Browse Answers About Privacy Policy

These Privacy Policy answers address the questions we expect when you are deciding whether to open a toz288 account from Indonesia. They cover collection, wallet records, cookies, device access, retention, and requests. Where a legal or account-security limit affects an answer, we state that directly so you know which next step to take.

The toz288 Privacy Policy covers account creation, phone verification, sign-in activity, device signals, cookies, wallet or bank references, support contact, retention, and requests about your data. It explains why each category is used and when access or a request may depend on local law.

Phone verification helps us confirm account access, reduce mistaken identity, and protect records when you ask about personal data. We store the verification state and related security record for those purposes. Do not send a verification code to support or any other contact.

Yes. The Privacy Policy explains how we handle transaction references and status when your account uses DANA, OVO, GoPay, or QRIS. We may also process a bank transfer or virtual account reference to reconcile the account record, without asking for unrelated wallet credentials.

We use required cookies to keep your session active, remember selected settings, and support sign-in security. Browser controls can remove or block cookies, but required settings may then interrupt access. Device signals may also help us identify unusual activity during account checks.

You can ask us to explain the account data we hold, correct an inaccurate detail, or clarify a processing purpose. Use the account support path and identify the record involved. We may confirm ownership through phone verification before disclosing or changing personal data.

We keep records for the period needed for account security, payment reconciliation, support questions, dispute handling, and legal duties. The exact period can vary by record type and applicable law. Once a record is no longer needed, it is deleted or anonymised where required.

You may ask about deletion of personal data, and we assess the request under applicable law and the reason the record is retained. Security, transaction, or legal records may need to remain for a defined period. Access to the service depends on local law.