Reference

berkaslot Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open a berkaslot account, use VIP Baccarat or Sugar Rush, and connect DANA, OVO, GoPay or QRIS.

Clear collection purposesWallet record detailsAccount contact routeCookie choices
berkaslot berkaslot Privacy Policy for Your Account
CONTACT YOUR WAY

Get Privacy Help Near Account Support

A clear contact path helps when you want to ask about your Privacy Policy rights, correct an account detail, or understand a wallet record. Start from the support route inside your account and include the email or phone detail linked to your profile, plus the relevant date or receipt reference. We use those details to locate the request without asking you to send a password or full wallet credentials.

Team online

Account support form

Use the signed-in support form for a data question, correction request or access concern. Include your account identifier and a short description so we can match the request to the right record.

Cashier record check

For DANA, OVO, GoPay or QRIS questions, mention the transaction date and visible status. We can check the account-side record while you keep wallet PINs and full authentication details private.

Login access route

If phone verification or sign-in blocks a Privacy Policy request, use the account access support path. We may ask for matching details before discussing personal data tied to the profile.

HOW DATA STAYS ORDERED

Your Data Choices Inside berkaslot

We separate account, payment-status and technical records so a Privacy Policy request can be handled with the narrowest useful scope.

Account data

We may hold your account contact details, verification status and sign-in history to provide account access and respond to account requests. We use the profile details you submit rather than creating an unrelated identity record.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries can create status, amount and receipt references. We use these records to reconcile requests and investigate mismatched cashier activity.

Device signals

Browser type, device signals and login timing can be recorded to protect the account from unusual access. These checks support verification without requiring your wallet PIN or banking password.

Cookies

Cookies can keep a signed-in session active, remember selected settings and help us understand technical errors. You can ask support which cookie category affected your session and request clarification about its purpose.

Retention

We retain records for the period needed to operate the account, resolve disputes, meet applicable duties or protect security. You can ask which retention reason applies to a particular account record.

Change requests

Send a correction, access or deletion question through account support, using the contact detail linked to your profile. We verify the request first, then explain what can change under local requirements.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account, device and wallet questions we expect before you continue. If your situation involves a specific receipt, phone verification step or sign-in event, use the support route inside your account so we can check the relevant record rather than giving a general reply.

It covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment-status references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

Phone verification helps us match a request or sign-in attempt to the correct account before discussing personal data. It also helps reduce mistaken access when your browser or device changes.

Yes. The policy can cover lobby and account activity connected with titles such as VIP Baccarat and Sugar Rush, including technical records needed to maintain sessions, investigate errors or answer account questions.

Use the signed-in account support form and ask for an account data access request. Include your linked email or phone detail; we verify ownership before discussing or sending personal records.

Yes, you can ask support to correct an inaccurate account detail. State what appears wrong and provide the linked contact detail; we assess the request against identity checks and local requirements.

We use DANA and QRIS references such as status, date and receipt details to reconcile account activity and investigate a mismatch. We do not ask for your wallet PIN or banking password.

Send a question through account support and name the cookie or record you mean. We can explain its purpose, the applicable retention reason and whether a change is available where local law permits.