Reference

too288 Privacy Policy For Your Account

The too288 Privacy Policy explains what we collect when you open an account, use Wallet Verification Steps, or connect DANA, OVO, GoPay and QRIS.

Account clarityWallet recordsCookie choicesSecure access
too288 too288 Privacy Policy For Your Account
HELP WITH PRIVACY

Get Clear Answers About Your Data

A privacy question should not interrupt your account path. Contact our support team when you need to ask what data is linked to your phone verification, why a wallet reference appears in your account record, or how to request a correction. Include the account identifier you can safely share and the relevant date, but never send a password or wallet PIN. We can explain the Privacy Policy, check a receipt status and direct a request to the right account-handling route.

Team online

Account questions

Ask which account details we hold and how phone verification is connected to access. We will use the account path you provide to locate the relevant record without asking you to disclose a password, wallet PIN or full payment credential.

Wallet records

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the receipt date and visible transaction reference through support. We can explain its status and check whether it was matched to your account, while keeping sensitive wallet credentials out of the request.

Privacy requests

Use our support route to request access, correction or deletion where applicable. Tell us the account email or phone detail involved and the change you seek. We may ask for account verification before acting, so another person cannot alter your records.

DATA HANDLING

What We Do With Your Account Details

We keep the Privacy Policy practical by linking each data use to an account action.

Account data

We may hold the details you submit for an account, including contact data and phone verification status.

Wallet matching

Payment records show a method, reference, amount status and time needed for reconciliation.

Cookies

Our cookies can keep a session active, remember selected settings and help us understand whether a page request is functioning.

Device security

We may record browser, device and connection signals to identify unusual access patterns and protect your account.

Retention

We retain account, support and transaction records for the period needed to provide the requested service, resolve disputes, protect the…

Policy changes

If our Privacy Policy changes in a material way, we will present the updated wording through an appropriate account or…

Privacy Policy Answers For too288 Accounts

These Privacy Policy answers address the account questions you are most likely to have before opening an account or asking for help. They explain the practical difference between account data, wallet references, device signals and cookies. If your situation involves a specific receipt, phone verification issue or request to change a record, contact support with only the details needed to locate the account.

It covers data connected with your account, phone verification, browser or device session, cookies, support requests and payment status. It also explains how we use those records for access, security, reconciliation and requests to view, correct or remove data where applicable.

No. Our Privacy Policy concerns the transaction reference and status needed to match a wallet action with your account. Do not send a PIN or password to support. If a receipt needs checking, provide only the visible reference and date.

Phone verification helps us confirm that an access request belongs to the account holder. We may retain its status and related account record so we can handle login questions, identify unusual requests and prevent another person from changing account details.

Yes, you can contact support with the account detail that needs correction and a clear description of the requested change. We may verify your identity first. We will assess the request under applicable requirements and explain if a record must be retained.

Send a deletion request through our support route, identify the account using a safe contact detail and state what you want removed. We may need to verify the request, and some account or transaction records may remain where needed for security or applicable duties.

Yes. The policy applies when you use a mobile browser or desktop browser. Device and browser signals can support session security, while cookies may preserve login settings. Your device path does not give us access to private files, photos or wallet PINs.

A privacy request does not automatically decide account eligibility. Access depends on local law and on any security checks required for the account. We can explain how a request affects account records, but we cannot bypass phone verification or account protection.