Reference

tobabet77 Privacy Policy: Your Account Data Path

Our Privacy Policy explains how we handle the details connected with your tobabet77 account, including login activity, wallet records and device access.

Clear data purposesWallet record contextAccess request stepsAccount security
tobabet77 tobabet77 Privacy Policy: Your Account Data Path
HELP WITH YOUR RECORDS

Get Policy Help Beside Your Account

A clear support route helps you resolve a privacy question without searching through unrelated pages. From your account area, describe the record or access event you want checked, and include the phone number linked to your account. We use that account step to confirm which details can be discussed with you.

Team online

Login data questions

Ask us to check sign-in records, phone verification status or a device session connected with your account. We will use the account details you provide to locate the relevant access event.

Wallet record checks

For DANA, OVO, GoPay or QRIS references, send the account identifier and payment date through our support route. We can explain which transaction reference appears in your account record.

Privacy requests

Use the policy contact path to request access, correction or deletion where available. We may ask you to complete phone verification before discussing personal details or changing an account record.

HOW WE HANDLE DATA

Understand Security, Cookies and Retention

Our privacy process follows the practical points you notice while using an account: the phone check before access, the device session after login and the payment reference beside a wallet status.

Account data

We handle your registration details, phone verification result and account activity to provide access and respond to account questions. We limit internal use to the purpose connected with the recorded account action.

Device signals

Your phone or desktop may send browser type, operating system, session time and security signals. These details help us recognise an unusual login and protect the account path without reading private files on your device.

Cookies

We may use necessary cookies to keep a session active, remember a language or connect a page request with your account. Browser settings can control cookies, although changing them may affect access.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries can appear as payment references. We use them to match status and support checks, not to request your wallet password.

Retention period

We keep records only for the period needed for account support, security review, transaction matching and legal duties. When a purpose ends, the record is removed, anonymised or restricted where applicable.

Your request path

Contact us through the account support route to ask for a copy, correction, restriction or deletion where available. Include your linked phone number and the specific record so we can verify the request.

Privacy Policy Questions About Your Account

These answers address the privacy searches we expect before you open or access an account. They cover the records created by login, phone verification, local wallet activity and browsing from a mobile device in Indonesia.

It covers account details, phone verification, login and device signals, necessary cookies, payment references and support records. It also explains retention, access requests and the conditions that apply where local law permits.

We use DANA and QRIS references to match a payment event with the correct account and status. We do not need your wallet password for that check, and you can ask support which reference is stored.

We may need the details used to create your account and a phone verification result before access or account changes. This helps us connect a request with the correct account and reduce mistaken disclosures.

Yes. The Privacy Policy covers practical device signals such as browser type, operating system, session time and security events when you use a phone or desktop to access your account.

You can contact our account support route with your linked phone number and ask for the records connected with your account. We may verify your identity before releasing details or confirming the request.

Send the specific record, date and account phone number through support. We will check the source, explain what can be changed and update the record where the request is valid and permitted.

You may request deletion through the policy contact path. Some records may need to remain for security, transaction matching or legal duties, and we will explain any restriction that applies to your request.