Reference

What This Privacy Policy Covers

This page explains how bujangtotoslot handles the data tied to your account, from the details you type during sign-up to device signals, login times, and support messages.

DANAOVOGoPayQRIS
bujangtotoslot What This Privacy Policy Covers
REQUEST ROUTES

Where To Send Privacy Requests

When you need a privacy change, we route it through the same desk that handles account verification, so your request does not get lost.

WhatsApp privacy desk Message us with the email on file, the change you want, and the account…
Email request inbox Send a request from the address tied to your account.
Account help desk If your case involves login history, device access, or a payment reference, we can…
DATA HANDLING

How We Keep Data Controlled

We keep privacy work tied to the account steps that matter most: collection, access, correction, retention, and closure.

Account setup record

We store the details you type into the form, plus verification results and login timestamps, so we can tie the profile to the right person and answer later requests without guessing.

Cookie and device signals

Cookies, browser type, device model, and IP address help us remember session state and flag odd access. The same signals work across Android, iPhone Safari, and desktop Chrome.

Payment trace data

If you use DANA, OVO, GoPay, or QRIS, we keep the reference number, status, and time stamp needed to locate a pending or failed transfer. Those records stay inside the account trail.

Game session logs

When you open Speed Blackjack, Aviator, Mahjong Ways, or Crash Games, we keep the session path and device signal needed for security checks and help tickets. We do not use that history for unrelated profiling.

Retention rules

We keep data only while it is needed for service, disputes, legal duties, or fraud checks. After that period, we remove it or anonymize it according to our retention schedule for the relevant records.

Correct or export data

You can ask for a copy, a correction, or an update to your contact details. We verify the requester first, then confirm any approved change through the same contact method.

Common Questions About Privacy Policy

These questions focus on the parts of the privacy policy you are most likely to check before opening an account. We cover what we collect, how cookies work on mobile and desktop, who can see the data, and how to request a change or a copy. If a request touches local law or a legal hold, we tell you what can move and what must stay.

We collect the details you enter in the form, plus login time, device type, and the contact method you choose. If you contact support, we keep the message thread and verification trail.

Yes. Cookies and similar tools remember session state, language, and basic security checks on Android, iPhone Safari, and desktop Chrome, so you do not repeat the same steps.

We keep it only for service operation, dispute handling, legal duties, and fraud checks. After that, we remove it or anonymize it according to our retention schedule for the relevant records.

Yes. Send the request from the address linked to your account, and we will verify it before acting. If the request is approved, we confirm the change or the copy in the same channel.

Only staff and service partners who need the data for account operation, payment tracing, or support can access it. They are limited to the task, and we do not share private details with other customers.

We follow the law that applies where access is permitted. If a rule changes what we may collect or keep, we update the policy and apply the new rule to the relevant records.