Reference

Open bola442 Privacy Policy for Indonesia

At bola442, we keep the privacy policy tied to the account you open, the device you use, and the payment path you choose.

IndonesiaDANAOVOQRIS
bola442 Open bola442 Privacy Policy for Indonesia
REQUEST PATHS

Browse the Contacts for Policy Requests

When you need a privacy change, we keep the contact paths simple. Live chat runs from 08.00-22.00 WIB, every day, and the form inside your account keeps a written trail if you prefer that route. We will ask you to confirm the account before we touch anything sensitive, then we route the request to the team that handles access, correction, or deletion checks.

Team online

Live chat, 08.00-22.00 WIB

Use this for access, correction, or a request to stop a specific message thread. We confirm your account first, then answer through the same chat so you can keep a record.

Email request path

Send your request from the email linked to your account if you want a written trail for access, correction, or deletion. Include your registered name and last login date.

Account menu

Open Account > Settings > Privacy to check consent, device access, and saved contact details. If you changed phone or email, update them there before you ask us to make further changes.

DATA HANDLING

Switch Through Our Data Handling Rules

We keep privacy controls close to the account actions you can see. Cookies help us remember sessions and language choices, while device logs help us confirm whether a login came from a…

Data minimisation

We only collect details needed for account setup, identity checks, support handling, and payment matching. Anything outside that scope is not part of the standard record.

Cookie use

Cookies remember your login session, language choice, and the pages you opened. You can clear them in your browser, but you may need to sign in again after that.

Login security

From Account > Settings > Security, you can change your password and sign out other sessions. That helps if you used a shared device or a public network.

Retention window

We keep chat logs and access logs only as long as needed for support, security checks, and legal duty. After that, the records are removed or anonymized.

Correction path

If your name, phone number, or email changes, update the record in your account first, then ask us to sync the history so future messages go to the right place.

Contact route

For access, correction, or deletion requests, use live chat or the account email path. We verify the account before action and answer within the stated support hours.

Open FAQs About Your Data Rights

These answers focus on the records tied to your account, devices, and wallet activity. If you ask for a change, we may first confirm your identity and the access route, then act only where local law permits. That keeps the process clear when you use DANA, OVO, GoPay, or QRIS and later need a correction, a copy, or a deletion check.

We collect the details needed to open and secure your account, answer support requests, and match payment records. That usually means your name, contact details, login history, device data, and the route used for DANA, OVO, GoPay, or QRIS.

Yes. Send the request through live chat or the account email path, and we will confirm the account before we share anything. If local law restricts part of the request, we will explain the limit clearly.

Open Account > Settings > Privacy, update the contact field, and save the change before you contact support. That way, our replies go to the right address and your record stays current.

We keep only the payment references and routing details needed to confirm the account action and settle support questions. We do not store more than the record needs, and we remove old entries when the retention window ends.

We keep support chats, login logs, and account change records for as long as needed for service handling, security checks, and legal duty. After that, we delete or anonymize them according to the policy.

Use live chat during 08.00-22.00 WIB or the email path inside your account. We ask you to confirm the account first, then route the case to the team that handles access or correction.

It applies where we can lawfully serve the account. If a local rule does not allow a request or feature, we will limit access to what local law permits.