Reference

beras66 Privacy Policy for Indonesia

beras66 Privacy Policy explains how we handle the details you provide when opening an account, checking DANA or QRIS wallet status, and entering the lobby.

Clear data purposesWallet record contextAccount access stepsPolicy contact path
beras66 beras66 Privacy Policy for Indonesia
REQUESTING HELP

Browse Account Wallet Help for Privacy Requests

A clear contact route matters when you want to ask about your Privacy Policy rights or a record connected to your account. Start with the account help path and include the phone number or account detail we can use to locate your request. We will ask for enough information to confirm ownership, while avoiding unnecessary personal details in your message.

Team online

Account access questions

If you cannot reach your account after phone verification, use Account Wallet Help and describe the device path you followed. We can check whether the request concerns an access record, a security check, or a policy question without asking you to repeat unrelated wallet details.

Wallet record queries

For a DANA, OVO, GoPay or QRIS record, include the payment rail and receipt reference shown in your account. Bank transfer and virtual account questions should identify the matching transaction so we can separate a privacy request from a status-check request.

Change or removal requests

Ask us to correct, provide, or remove personal details through the policy contact route attached to your account. We may verify your identity first, then explain which records can change and which must remain for security, dispute handling, or legal duties.

DATA HANDLING

Explore How We Protect Your Account Records

Privacy work is part of the account flow, not a separate promise hidden from the cashier path.

Account details

When you open an account, we use the details needed to create and maintain that account, including contact data and phone verification status. We do not treat a request about Live Blackjack Turbo or Fishing War Arcade as a reason to collect unrelated personal details.

Wallet records

Payment records help us match a wallet event with the correct account and investigate a receipt or status question. DANA, OVO, GoPay, QRIS, bank transfer and virtual account references can therefore appear in operational records without becoming a separate marketing profile.

Device signals

A mobile browser may provide device, browser and session signals that help us detect unusual access or keep your account path working. We use those signals for access and security checks, including when you move from login to the lobby on a phone.

Cookies

Cookies can support login continuity, basic settings and account security. You can clear or restrict them in your browser, although some account steps may then need to be repeated. The Privacy Policy explains which cookie purposes relate to access rather than advertising.

Retention approach

We retain records for as long as they are needed for account operation, security checks, payment matching, dispute handling, or legal duties. When a record no longer has a valid purpose, our handling process considers deletion or anonymisation where that is permitted.

Policy changes

If our data handling changes, we update the policy wording and show the current version on this page. Check it before opening an account or using a new payment path, especially when access or eligibility depends on local law.

Check Privacy Policy Answers Before Joining

These Privacy Policy answers focus on the questions we expect during account opening, mobile access, and wallet support. They explain the practical route for checking records, changing details, and asking about cookies or retention. If your question is not covered, use Account Wallet Help and refer to the current policy page.

The beras66 Privacy Policy covers account details, phone verification, device and browser signals, cookies, wallet and transaction references, support messages, retention, security checks, and requests to access or change your records. It also explains when legal duties may require us to keep specific information.

Phone verification helps us confirm account ownership and protect access when you sign in or ask about personal records. It can also help us distinguish your request from another account. We use the result for account and security purposes, not as a reason to request unrelated details.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account matching details. These records help us check receipts, connect a wallet event to your account, and handle a question about payment status.

Use the contact route in Account Wallet Help and state whether you want access, correction, or removal. Include a usable account reference, but do not send extra personal details. We may verify ownership before responding, and some records may remain where security or legal duties require them.

Cookies may support login continuity, basic preferences, and account security when you use a mobile browser. You can restrict or clear them in your browser settings. If you do, some access steps may need to be repeated, and the policy explains the purposes connected with your session.

We keep information only while it serves an account, security, payment matching, dispute, or legal purpose. The exact period can differ by record type and applicable requirements. When the purpose ends, we consider deletion or anonymisation where local rules allow that action.

Yes. Send your question through the policy contact path connected with Account Wallet Help, especially if it concerns account access, a wallet receipt, cookies, or a data change. Eligibility and available access depend on local law, so we will explain the relevant route for your request.