Reference

Open your Privacy Policy path

Your berani win Privacy Policy explains what we collect when you create an account, verify your phone, browse Auto Roulette or use DANA and QRIS.

Account dataWallet recordsCookie choicesRequest access
berani win Open your Privacy Policy path
CONTACT ROUTES

Browse support for privacy requests

A clear support route helps when your privacy question concerns login, a wallet record or an account document. Start from the account support area and include the phone number tied to your profile, the date of the relevant event and the request you want us to assess. Do not send a full password or wallet PIN. We use the account context to locate the right record, confirm that the request comes from you and explain any legal or security reason for limiting access.

Team online

Account privacy request

Ask us to locate, correct or explain personal details connected with your account. Include your registered phone number and a short description of the requested change so we can match the request without asking you to repeat private data.

Wallet record question

If a DANA, OVO, GoPay or QRIS receipt appears linked to the wrong status, contact the account support route with its date and reference. We can compare the account record while avoiding requests for your wallet PIN or full login password.

Access and deletion help

For a copy request, correction request or eligible deletion request, tell us which account detail is involved. We may need an account step to confirm your identity, and we explain where local law permits the requested action or requires limited retention.

DATA PRACTICE

Check how we handle account data

Privacy choices work best when you can see the practical steps behind them. We separate account identity details from ordinary browsing signals where the service allows, record security events for protection and…

Data we receive

We may receive your phone number, account details, verification outcome, login timestamps, device signals and support messages. When you open Fish Hunter or another lobby area, we may record the account event needed to maintain access and investigate a security or payment question.

Cookies and device signals

Cookies can remember a session, support account navigation and help us identify unusual sign-in behaviour. Device and browser signals may be used for security checks. You can manage available browser choices, although changing them may affect login continuity or privacy request handling.

Phone verification

A phone verification step helps connect a privacy request to the correct account and reduces mistaken disclosure. We use the result to confirm access, not as a reason to request your password. If the check cannot be completed, support explains the next account step.

Payment references

For DANA, GoPay, QRIS, bank transfer and virtual account activity, we may retain transaction references, amount status and timestamps needed to reconcile an account. We do not need your wallet PIN to investigate whether a receipt reached the correct payment record.

Retention and deletion

We keep information only for the period needed for account operation, security checks, dispute handling or a legal duty described in the policy. A deletion request does not always remove records that local law requires us to retain, and we explain that outcome.

Security questions

If you suspect another device accessed your profile, tell us through the account support route and include the sign-in time if visible. We may restrict a privacy change until identity is checked, protecting account details while we assess the event.

Ask about berani win Privacy Policy

These Privacy Policy questions cover the account steps people usually need before sending a request. Each answer points you toward the relevant record, from a phone verification result to a DANA receipt or cookie setting. If your situation is different, use the account support route and describe the exact data concern.

The berani win Privacy Policy covers account details, phone verification, device and cookie signals, support messages, payment references and security events. It also explains retention, service processing, disclosure conditions and how you can request access, correction or eligible deletion.

Use the account support route and identify the phone number connected with your profile. State that you want a data copy, then describe the account period or record involved. We may ask for a verification step before releasing details, subject to local law.

Yes. The Privacy Policy covers references linked with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We may use timestamps, status and payment references to reconcile an account, but you should never send a wallet PIN or full password.

Cookies can keep a session active, support account navigation and help identify unusual sign-in behaviour. The Privacy Policy explains these purposes and available browser controls. If you block certain cookies, login continuity or a privacy request may require another account step.

Yes, you can request a correction through the account support route. Include the detail that appears wrong and the replacement information, without sending a password. We check the account context first, then explain whether the change can be made under the Privacy Policy.

You may request deletion of eligible personal details, but some records can remain when needed for security, payment reconciliation, dispute handling or a legal duty. The Privacy Policy explains the reason and retention period where possible. The result depends on local law.

Contact us through the account support route and include your registered phone number, the affected record and the action you want. For a wallet issue, add the payment date or reference. We use those details to assess the request without asking for secret credentials.