Reference

to288 Privacy Policy And Account Data

Our Privacy Policy explains what to288 collects when you open an account, sign in from a mobile browser, or connect DANA, OVO, GoPay or QRIS.

Account clarityWallet recordsCookie choicesData requests
to288 to288 Privacy Policy And Account Data
CONTACT ROUTES

Get Privacy Help From Your Account Path

A clear contact route matters when a receipt, login event or data request needs attention.

Account help panel Use the help path attached to your account when you need to ask about stored details, a sign-in record or a verification message. We may ask you to confirm the contact detail already linked to the account before discussing private data.
Wallet receipt query For a DANA, OVO, GoPay or QRIS receipt question, share the reference shown in your wallet history rather than sending a password. We compare the payment record with the account event and explain what data was used for the status check.
Data change request Ask us to correct an inaccurate contact detail or explain a retention entry through the support route. We verify the requester first, record the request, and tell you if a legal or transaction record must remain stored.
HANDLING DETAILS

What We Do With Your Private Records

We keep this policy practical: account information supports sign-in, wallet matching and security checks, while device signals help us detect a session that does not look like your usual access.

Account security

Clear phone verification before account access helps connect a sign-in to the right account. We may record failed attempts, device signals and session timing to investigate suspicious access, but we do not need your wallet PIN to assess an account event.

Cookie controls

Cookies can keep a mobile browser session active and help us understand whether a page loads correctly. You can clear or restrict them in your browser settings. Some account functions may then ask you to sign in again or repeat a security check.

Payment references

A QRIS, DANA, OVO or GoPay reference lets us match a receipt to the correct account request. Bank transfer and virtual account records are handled for reconciliation and support, not displayed as public account content.

Device signals

When you use a phone or desktop browser, we may receive device type, browser version, IP-related security data and session timestamps. These signals help identify unusual access and diagnose a page issue without reading unrelated files on your device.

Retention choices

We retain account, payment and support records only while they serve account administration, dispute handling, security or a legal requirement. After that period, records are deleted or changed so they no longer identify you where that process is available.

Your requests

You can ask for a copy, correction or explanation of personal data connected with your account through the account help route. We check identity before responding and explain any limit when a record must remain for a transaction or legal reason.

Privacy Policy Answers For to288 Accounts

These Privacy Policy answers address the points most often raised before account access: what is collected, how wallet records are matched, how cookies behave on mobile, and how to contact us. The same process applies whether you sign in from a phone in Semarang or use a desktop browser. Access and eligibility depends on local law, and we will explain any request that needs extra verification.

It covers account details, phone verification, device and browser signals, cookies, support messages and payment references. It explains why we use each category, how records support account security and wallet reconciliation, how long they may remain stored, and how you can request access or correction.

Yes. The policy includes references needed to match DANA, OVO, GoPay and QRIS activity with an account request. It can also cover bank transfer and virtual account records. We use these references for status checks, reconciliation and support, not as public profile details.

We may collect device type, browser version, session time, IP-related security data and signals from failed or unusual sign-in attempts. This helps us protect your account and diagnose page behaviour. We do not use this process to inspect unrelated files stored on your phone or computer.

You can contact us through the account help route and ask for a copy, correction or explanation of data linked to your account. We first confirm your identity using existing account details. If a record must remain for a transaction or legal reason, we explain that limit.

Cookies may keep your session active, remember selected settings and show us whether pages load correctly on a mobile browser. You can restrict or clear them in browser settings. Doing so may sign you out or require another phone verification step before account access.

We retain payment, account and support records while they are needed for account administration, receipt matching, security investigations, dispute handling or a legal requirement. When the purpose ends, we delete or anonymise the record where possible rather than keeping it without a reason.

Use the help panel connected to your account and describe the data question clearly. Include the linked contact detail, request type and relevant date, but never send a wallet PIN or secret code. We may request identity confirmation before discussing private account or payment records.