Reference

berkahslot Privacy Policy for DANA and QRIS

Our Privacy Policy explains how we use account, device and wallet details when you open berkahslot on mobile or desktop.

Account dataWallet checksDevice privacyPolicy requests
berkahslot berkahslot Privacy Policy for DANA and QRIS
CONTACT ROUTES

Privacy Help for Account and Wallet Status

A direct privacy question should not require you to explain your whole account history. We separate account access, wallet status and policy requests so you can point us to the exact issue. If you contact us from an account, include the relevant reference rather than sending a full wallet number. This helps us check the matter while limiting the personal details shared through support.

Team online

Account support route

Open the support route from your account when you need to ask how phone verification, login records or device details are used. We may ask for an account identifier before discussing private data.

Cashier status path

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, share the payment reference and date through the cashier support path. Do not send your wallet PIN or password.

Policy request path

Use the privacy contact path shown in your account to request access, correction or deletion details. We will first confirm that the request comes from the account owner before discussing records.

SECURITY PRACTICE

Six Checks Behind Your Account Data

Privacy protection works through small account steps rather than a single promise. We limit what is shown during support, check account ownership before discussing records, and separate payment references from credentials.

Purpose-based collection

We collect account details for account access, phone verification, support and security. Payment references from DANA or QRIS are used to identify a transaction, not to request your private wallet PIN.

Cookie controls

Cookies can keep your session active, remember settings and help us understand basic page performance. You can adjust browser cookie controls, though some login functions may not work as expected afterward.

Account security

We use login signals, phone verification and device details to help identify unusual access. Keep your password private and contact support if a device appears on your account without your approval.

Payment separation

Wallet and transfer references are handled separately from your password and wallet PIN. For OVO, GoPay, bank transfer or virtual account questions, share only the reference needed for a status check.

Retention periods

We retain records while they support account operation, security, payment status or a legal requirement. When a purpose ends and no further duty applies, the relevant record can be removed or de-identified.

Change requests

You can ask us to correct inaccurate account data or explain how a record is used. We may verify your identity first, then confirm what can be changed under local requirements.

Privacy Policy Questions for berkahslot

These answers cover the privacy questions most often connected with opening an account, checking a wallet reference or using the lobby from an Indonesian device. If your situation is not listed, use the privacy contact path while signed in so we can identify the correct record without unnecessary disclosure.

The Privacy Policy covers account details, phone verification, device signals, cookies, payment references and support requests. It also explains retention, security checks and how you can request access or corrections.

We do not ask you to send a wallet PIN through support. We may keep a transaction reference or status detail for DANA, OVO, GoPay or QRIS, but your credential should remain private.

Phone verification helps connect an account with its owner before access and support discussions. It can also help us investigate unusual login activity without exposing account details to an unverified contact.

Cookies can maintain your login session, remember selected settings and provide basic page-use signals. Browser controls let you adjust them, although turning off required cookies may affect account access.

Yes. Use the privacy contact path shown in your account and describe the record you want to access or correct. We may confirm account ownership before sharing or changing personal data.

Retention depends on the purpose of the record, including account security, payment status, support or a legal requirement. When no purpose or requirement remains, we remove or de-identify it where permitted.

The policy explains our handling of data for supported access, but eligibility depends on local law. If you are unsure, check the access wording shown for your location before opening or using an account.