Reference

Privacy Policy For Your berkawantoto Account

berkawantoto keeps this Privacy Policy focused on the details you need before opening an account: what we collect, why we use it, how phone verification works, and how…

Clear data purposesWallet record detailPhone check contextAccount contact route
Explore Our Lobby Read FAQ
berkawantoto Privacy Policy For Your berkawantoto Account
CONTACT PATHS

Get Privacy Help Beside Your Account

A clear contact path matters when your account data or wallet record does not look right. Start from the account help area and tell us whether your request concerns access, correction, deletion, cookies or a payment reference. We use the details you provide to locate the relevant record, then explain the next step without asking you to send unrelated account material.

Team online

Account access

If phone verification blocks your account, use the account help path and describe the screen or step where access stops. We check the relevant sign-in and verification record, then ask only for details needed to confirm that you control the account.

Wallet records

For a DANA, OVO, GoPay or QRIS reference, include the account identifier and payment date shown in your record. We use that narrow request to trace the event and avoid placing unrelated wallet details into the support conversation.

Policy requests

To ask about a copy, correction or removal of personal data, name the request clearly in the account help area. We may need an account check before acting, because privacy changes must not expose your data to another person.

DATA CONTROLS

Six Practical Privacy Controls We Use

Privacy becomes easier to assess when each control has a visible account purpose. We separate sign-in protection from payment matching, limit staff access to the records needed for a task, and use…

Account records

We use account details to maintain your sign-in path, complete phone verification and respond to account requests. The account record is kept distinct from a general browsing visit so a privacy question can be tied to the correct profile.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a payment event to your account. We use that record for status checks, reconciliation and disputes rather than collecting a wider wallet history.

Cookie choices

Cookies can retain a session setting and help us understand which account screen was opened. You can manage cookie behaviour through your browser, though restricting some cookies may require another sign-in or reduce account-path convenience.

Device security

Device and session signals help us spot sign-in patterns that do not match your normal account use. We may pause a sensitive step and request phone verification when the signal suggests that someone else may be attempting access.

Retention limits

We retain personal data while an account, security matter, payment trace or dispute gives us a valid operational reason to keep it. When that reason ends, we remove, restrict or de-identify the record according to the applicable requirement.

Change requests

You can ask us to correct inaccurate details, explain a record, or consider removal through the account help route. We verify the requester first, record the decision, and tell you if a security or dispute reason prevents immediate removal.

Questions About This Privacy Policy

These answers address the searches we expect from someone checking berkawantoto before opening an account. They cover collection, wallet references, cookies, phone verification, access requests and local eligibility, so you can decide what to share and where to ask for help.

The berkawantoto Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, support messages, and payment references. It explains why we use each category, how retention works, and how you can request access, correction or removal through the account help path.

Phone verification helps connect an account request to the person controlling the stated number and can interrupt suspicious sign-ins. We use the result for account access and security checks. If you cannot complete it, contact the account help route and describe the blocked step.

Yes. The Privacy Policy includes payment references from DANA, OVO, GoPay and QRIS, plus bank transfer or virtual account records when used. We use those references to match status, resolve a dispute or answer a receipt question, not to collect unrelated wallet activity.

Use the account help area and state whether you want a copy, correction or explanation of a specific record. Include the account detail that needs attention, but do not send unrelated wallet data. We may verify account control before releasing or changing personal information.

We keep personal data while it supports an active account, security investigation, payment reconciliation or dispute, and while an applicable requirement calls for retention. After that reason ends, we remove, restrict or de-identify the record. You can ask support about the reason for a specific record.

You can manage cookies through your browser settings. Some cookies remember a session or account preference, so restricting them may require another sign-in or affect parts of the account path. The Privacy Policy explains this use, and support can help identify a cookie-related access issue.

This Privacy Policy is written for account access in Indonesia, but eligibility depends on local law and is available where local law permits. If you are unsure whether access applies to your location, contact our account help desk before sharing personal data or opening an account.

Related Pages

berkawantoto Indonesia About Us berkawantoto Casino Access guide FAQ