Reference

batu goncang Privacy Policy for Your Account

Our batu goncang Privacy Policy shows what we collect when you create an account, verify your phone, browse from a mobile device, or select DANA and QRIS at…

Account dataDevice signalsWallet recordsCookie choices
Explore Our Lobby Read FAQ
batu goncang batu goncang Privacy Policy for Your Account
DATA HELP DESK

Reach Us About Your Account Data

A clear support route helps when a privacy question appears beside an account or wallet record.

Account help path Use the account help form for a copy request, correction request, or question about how we use your batu goncang account data. We may ask you to confirm the account step or phone number connected to the request before discussing personal records.
Wallet status check If a DANA, OVO, GoPay, or QRIS reference appears in your request, attach the receipt number and date rather than a wallet password. We check the matching account record, explain its purpose under this Privacy Policy, and limit the response to data connected with you.
Privacy request For deletion, correction, access, or objection requests, write the exact action you want and the email or phone used at account creation. We may verify ownership before making a change, and we will explain if a record must remain for security or legal duties.
DATA PRACTICES

Protect Your batu goncang Account Records

We keep the policy practical by tying each data use to a visible account action: signing in, confirming a phone, opening a game page, checking a wallet status, or contacting support.

Collection points

We collect data when you enter account details, complete phone verification, sign in, contact support, or select a payment route. Device type, browser language, IP-related security signals, and page events can help us identify suspicious access without treating your game choices as a public profile.

Cookie controls

Cookies and similar browser storage can keep your session active, remember a selected language, and help us detect repeated sign-in failures. You can clear or restrict them in your browser settings, but doing so may require another login or interrupt account and wallet status screens.

Account security

Phone verification connects account access to the contact detail you supplied, while login records help us investigate unusual device behaviour. Never send a password, wallet PIN, or full authentication code through support. We may ask for limited account facts before releasing personal data.

Retention decisions

We keep account, support, and transaction references only while they serve account security, dispute handling, service records, or legal duties. A deletion request does not always remove a record immediately when we must preserve evidence, but we can restrict its further use where appropriate.

Correction requests

If your contact detail, phone number, or account record is wrong, send the requested correction through account help. We compare the request with the account step and may ask for verification. Once confirmed, we update the relevant field and explain any linked record that cannot change.

Who to contact

Our account help path is the first contact for Privacy Policy questions, data copies, deletion requests, and cookie concerns. Describe the page or event involved, such as a QRIS status screen or a Live Roulette Diamond session, so we can locate the correct record.

Browse Privacy Policy Answers

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover account creation, device records, cookies, local wallet references, access requests, and contact steps. If your situation is different, use account help with the smallest amount of personal data needed to identify your request.

It covers personal data connected with your account, phone verification, sign-in events, device and browser signals, cookies, support messages, and payment references. It applies when you use account pages, game pages, wallet status screens, or support where local law permits.

Phone verification helps connect access to the contact detail supplied during account creation and helps us investigate unusual sign-in activity. We record the verification result and related security event, not your private phone conversations. You can ask account help how that record is used.

Yes. When you choose DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account, we may keep a payment reference, amount status, date, and matching account identifier. These records help reconcile wallet activity and support requests without requiring your wallet PIN.

We may record device type, operating system or browser details, language settings, IP-related security signals, and sign-in times. This helps recognise unusual access and keep a session working on mobile or desktop. It does not give us access to private files stored on your device.

Yes. Send a request through the account help path, state whether you want access or correction, and provide the email or phone linked to your account. We verify ownership before responding. We may retain limited records when security, dispute handling, or legal duties require it.

Use account help and specify the records you want deleted, such as an old contact detail or support message. We assess the request against security and legal retention needs, then remove or restrict eligible data. We explain any part that must remain and why.

You can restrict or clear cookies through your browser settings. Essential session storage may still be needed for sign-in, phone verification, or wallet status pages, so refusing it can require repeated access steps. Contact account help if a cookie choice causes a privacy or account concern.

Related Pages

batu goncang Indonesia Live Roulette Diamond About Us Account information FAQ