Reference

How bobatoto2 Handles Your Personal Data

This privacy policy covers exactly what data we collect when you open an account, deposit via DANA, OVO, or GoPay, and use our platform — and how we keep that data secure.

Account data protectedDANA, OVO, GoPay wallet info handled securelyNo data sold to third partiesYou can request data access anytimeIndonesia-local data handling
bobatoto2 How bobatoto2 Handles Your Personal Data
PRIVACY CONTACT PATHS

How to Reach Us About Your Privacy

If you want to review your stored data, request a correction, or ask us to delete your account information, our support team handles privacy requests directly. Reach out through any of the channels below and let us know what you need — we'll confirm receipt and work through the request with you.

Team online

Live Chat

Start a live chat session from your account dashboard. Privacy requests are handled by our account team and confirmed in writing during the session.

Email Support

Send your privacy request to our support email. Include your registered account name so we can locate your data record and respond accurately.

In-App Help

Open the Help section inside your account on mobile or browser. Use the privacy request form to submit data access, correction, or deletion requests directly.

HOW WE PROTECT IT

Data Security and Account Privacy Practices

We apply security measures at the account, session, and payment layers. Every login session uses token-based authentication, and we log access timestamps to flag activity that looks out of the ordinary. Payment data passed through DANA, OVO, and GoPay is handled over encrypted connections, and wallet references are stored in masked form — we never hold your full wallet credentials. Cookies on our platform serve session continuity and fraud detection only; we do not use tracking cookies for external advertising. You can clear session cookies through your browser settings at any time without affecting your account balance.

Encrypted Connections

All data exchanged between your device and our servers — including DANA, OVO, and GoPay payment references — travels over SSL-encrypted connections at all times.

Cookie Use

We use session cookies to keep you logged in across pages and to detect unusual login patterns. No advertising or cross-site tracking cookies are set by bobatoto2.

Data Retention

Account data is kept for as long as your account is active and for the period required under applicable local regulations. You can request deletion once your account is closed.

Access Control

Only authorised internal teams can access your personal data — and only when a specific account, payment, or support function requires it. Access is logged and audited.

Your Questions About Privacy at bobatoto2

These are the privacy questions we hear most from account holders in Indonesia. If your question is not covered here, contact our support team through live chat or email and we will respond directly.

We collect your name, email, phone number, and device data at registration. When you deposit or withdraw via DANA, OVO, or GoPay, we also record the transaction reference tied to your account.

We do not sell your data. We share only the minimum required information with payment processors like DANA, OVO, and GoPay to complete your transactions — nothing more.

Contact our support team via live chat or email with your registered account name. We will locate your data record and send you a summary of what we hold.

Yes. Once your account is closed, you can request deletion of your personal data. We will process the request in line with applicable local regulations and confirm when it is done.

We use session cookies for login continuity and fraud detection only. You can clear them through your browser settings at any time — your account balance and history are stored server-side, not in cookies.

Wallet references are stored in masked form over encrypted connections. We never hold your full wallet PIN or credentials — only the transaction reference needed to verify your payment.
Reference

Privacy Policy

Service availability depends on eligible regions and local law. Users should check local rules before opening an account.

Access may be available only where local law permits.