Reference

tombol88 Privacy Policy For Your Account Data

Your account data, wallet records and device details are covered in the tombol88 Privacy Policy, so you can see what we collect and why before opening an account.

Clear data purposesWallet record contextAccount contact routeLocal-law access
tombol88 tombol88 Privacy Policy For Your Account Data
CONTACT PATHS

Where Your Privacy Questions Go

A clear contact route helps you ask about the Privacy Policy without guessing which account screen to use.

Account data request Use the account help route to ask what personal details are linked to your tombol88 account. Include your registered contact and the specific record you want checked; we may need an account step to confirm that the request belongs to you before sending details.
Wallet record question For DANA, OVO, GoPay or QRIS references, send the transaction reference shown in your account rather than sharing a wallet password or private code. We use the reference to check the relevant status and explain which payment record the Privacy Policy covers.
Correction or deletion If your contact details are wrong or you want to ask about removing a record, contact us through account help and name the requested change. We assess the request against security, transaction and legal retention needs, then explain any record that must remain.
RECORD HANDLING

How We Handle Account Records

The Privacy Policy is practical at each point where your account creates a record: registration, phone verification, wallet activity, device access and support contact.

Account details

When you open an account, we use the details you provide to create access, confirm the registered contact and manage account requests. Phone verification may be required before access or a data response, helping us avoid sending private account details to the wrong person.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can produce reference numbers, amounts, status markers and timestamps. We use those records to match an account request or check a wallet issue; we do not ask for your wallet password.

Cookies and sessions

Cookies and session signals help keep your login connected, remember necessary choices and identify unusual device behaviour. On a phone, browser changes or cleared cookies may require another login or phone check; this is part of protecting the account session.

Security checks

We may compare login details, device signals and phone verification when an account request looks unusual. If you contact us about a locked session or wallet status, provide the account contact and reference only through the stated support path, never a password.

Retention choices

We retain account, payment and support records only for the period needed for the stated service, security, dispute handling or legal requirement. A deletion request does not automatically remove records that must be kept to confirm a transaction or meet a lawful request.

Policy changes

If the Privacy Policy changes in a way that affects how we handle your account data, we update the policy page and identify the changed section. You can return from the tombol88 account area to check the current wording before continuing account activity.

Privacy Policy Questions For tombol88

These Privacy Policy answers cover the account questions you are most likely to ask before sharing contact details or using a local wallet. We explain the request path, device records, cookies, payment references and policy access in plain English. If your case involves a specific record, use account help and include only the details needed to locate it.

The tombol88 Privacy Policy covers account details, phone verification, device and session signals, cookies, support messages, payment references and security records. It also explains why we use each category, how retention works and how you can ask for access, correction or clarification.

A DANA or QRIS action can create a reference, status and timestamp linked to your account request. We use that record to match payment support, check an unsettled wallet status and protect the account from incorrect changes. The Privacy Policy explains this payment-record purpose.

Yes. Use the account help contact path and ask for the personal data connected with your registered contact. We may request phone verification or another account step before responding, because the Privacy Policy requires us to protect your details from an unauthorised request.

Phone verification confirms the contact used for account access, while device and session signals help identify unusual login behaviour. If you switch browsers, clear cookies or change phones, another check may appear. These records are handled for access and security under the Privacy Policy.

You can ask us to correct inaccurate account or contact details through account help. State which field is wrong and what should replace it, without sending a password. We may verify the request before changing the record, and we explain any restriction that affects the correction.

Retention depends on the purpose of the record, such as account security, payment matching, dispute handling or a lawful requirement. DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may therefore remain after a request, even if other data can be removed.

Check the current Privacy Policy page from the tombol88 account area, then use account help if a wording change is unclear. Tell us the section or topic you mean, such as cookies, retention or wallet references, and we can direct the question to the relevant contact path.