Reference

tomatbet Privacy Policy for Indonesia Accounts

tomatbet Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, or connect DANA and QRIS.

Account dataWallet recordsCookie choicesPrivacy requests
tomatbet tomatbet Privacy Policy for Indonesia Accounts
ACCOUNT HELP DESK

QRIS Questions Reach Our Account Desk

A privacy question should not get lost beside a wallet receipt. Use the support route shown inside your tomatbet account when you need to ask about stored details, a device record, or a QRIS payment reference. Include your account contact and a clear request, but leave out passwords and one-time security codes. We use the account path to reduce confusion and locate the right record.

Team online

Account privacy request

Ask through the signed-in support path when you want to know which account details we hold or why a phone verification record appears in your access history.

Wallet record question

For DANA, OVO, GoPay, or QRIS references, provide the date and receipt identifier so we can check the account link without requesting your wallet password.

Security concern

If a new device, unfamiliar sign-in, or changed contact detail looks wrong, contact us through your account route and describe the event before requesting any data change.

DATA PRACTICE

How We Protect Your Account Trail

We treat privacy as an account process rather than a statement hidden from view. Our controls connect the policy to practical events: phone verification, mobile-browser access, wallet references, and support requests.

Data we receive

We may receive account contact details, verification results, sign-in time, device signals, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, or bank transfer.

Cookie controls

Cookies and similar device storage can help keep a session open and remember security settings. You can review browser controls, though blocking them may interrupt account access.

Account security

Phone verification helps connect access to the correct account. We may check unusual device activity before changing contact details, wallet links, or other account information.

Retention approach

We keep records only as long as needed for the stated account purpose, security checks, dispute handling, or a lawful request, then assess whether continued storage remains necessary.

Request a correction

Send a clear request through the account support route if your contact detail, device record, or payment reference needs correction. We may ask for verification before making changes.

Third-party boundaries

DANA, OVO, GoPay, QRIS, banks, and other linked services manage some data under their own terms. We can explain our record, but their privacy request must reach them.

Privacy Policy Questions for tomatbet

These answers focus on the searches we hear before an account is opened or a wallet is connected. They cover access, stored details, cookies, correction requests, and the boundary between our records and Indonesian payment services. If your question is not listed, use the signed-in support route and describe the exact account event.

It covers account details, phone verification, sign-in and device records, cookies, support messages, security events, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account.

Phone verification helps us connect account access to you, reduce mistaken sign-ins, and check sensitive changes. We may use the result when you request a contact or wallet-record correction.

It covers the payment reference and account link we receive for DANA or QRIS activity. The wallet or payment provider controls its own records, so its separate privacy terms also apply.

Use the support path inside your signed-in account and state whether you want access, a correction, or an explanation. We may verify your identity before releasing or changing account details.

We may record device and browser signals, sign-in time, and security events needed to protect access. These details help us identify an unfamiliar mobile browser without reading your private device content.

Send the request through account support with the relevant contact detail or record. We assess removal against security, dispute, and lawful retention needs, and explain when a record must remain.

The policy applies to tomatbet pages and account areas that link to it, while access and eligibility depend on local law. Payment providers and banks may apply their own regional terms.