Reference

Privacy Policy for Indonesian Accounts

One page shows how we collect, use, store, and update your data, so you can check the rules before you open your account.

DANAOVOGoPayQRIS
bwin365 Privacy Policy for Indonesian Accounts
CONTACT PATHS

Where to Reach Us About Privacy

For privacy requests, we answer through in-site chat, email, and the account form after login.

In-site chat Open chat after login if you want access to your records, a correction, or a cookie question. We check the account email and recent login details before we touch anything.
Email Write from the address tied to your account when you need a privacy request in writing. We use it for questions about stored data, contact updates, and the status of a previous request.
Account form Go to Account > Settings > Privacy on mobile or desktop to send a change request. That path helps us keep a clear record of what you asked for and when.
HOW WE STORE

How We Handle Your Data

We handle privacy requests by limiting collection, keeping cookie use simple, and tying account changes to the login that made them.

Minimal collection

We collect only the details needed to open the account, confirm login, and answer your request. That usually means contact details, device data, and the logs tied to your account history, not extra fields that sit unused.

Cookie control

On Android Chrome, iPhone Safari, and desktop browsers, cookies keep the session stable and remember language choice. You can clear them in the browser at any time, but the account will ask you to log in again.

Device sessions

When you change a password or open a new device, we may ask you to confirm the request through email or chat. That keeps account access tied to you, not to a browser that someone else could use.

Payment records

If a request touches DANA, OVO, GoPay, QRIS, or bank transfer references, we keep the linked record only long enough to verify the account and resolve the ticket. We do not use it for unrelated purposes.

Retention timing

We keep logs only as long as needed for support, security checks, dispute handling, and legal duties. After that period, they are removed or archived under the same retention rules that apply to the account.

Your change request

Send correction, access, or deletion requests through chat, email, or the Privacy area after login. We match the request against your account details first, then tell you what happens next in the same channel.

Privacy Questions We Hear Most

These answers cover the practical parts of the policy: what we keep, how cookies behave on Android, iPhone, and desktop, who can see your data, and how you ask for changes. When local law matters, we say it plainly, and we only process access where local law permits. The same request path stays inside your logged-in account, so you do not need to repeat the same details.

It covers collection, use, storage, sharing, and change requests for your account data. It also explains cookies, device logs, and the checks we need before we act on a request tied to your profile.

We keep the details needed for login, identity checks, support, and payment matching, including device and browser data. If a DANA, OVO, GoPay, or QRIS record matters to a request, we tie it to the account record.

On Android Chrome and iPhone Safari, cookies help keep you signed in, remember language choice, and load the same account state across pages. You can clear browser cookies at any time, but you may need to log in again.

Yes. Open the Privacy area in your account, send the correction request, and we will check it against your login details. If the field affects verification, we may ask for a supporting step before we update it.

We keep records only as long as needed for support, security checks, dispute handling, and legal duties. After that period, we remove or archive them under the same retention rules that apply to the account.

Only staff who need the data for support, operations, or legal checks can access it, and access depends on the task at hand. We do not share it outside those uses unless local law requires it.

Use in-site chat, email, or the Privacy area after login. We verify the request against your account before we reply, and the same path is available only where local law permits.