Reference

dewi28 Privacy Policy for Your Account

Our dewi28 Privacy Policy explains what we collect when you open an account, sign in, use DANA or QRIS, and move through areas such as Live Dealer Lobby…

Account dataWallet recordsCookie choicesPrivacy requests
dewi28 dewi28 Privacy Policy for Your Account
CONTACT PATHS

Where To Ask About Privacy

A clear contact route helps you act on this Privacy Policy without searching through the lobby. Start from your signed-in account support panel and include the phone number linked to your account, the subject of your request, and any relevant payment reference. We use those details to confirm the account before discussing records, and support can direct wallet-status questions to the correct review queue.

Team online

Account support panel

Open the support panel after signing in and select the privacy subject. We can explain stored account details, verification records, or a correction request without asking for your wallet password.

Payment reference route

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account questions, send the payment reference and date. We use that match to locate status records while limiting unnecessary account details.

Access assistance

If your phone verification blocks account access, contact support from the available account route and provide the registered number. We can explain the privacy check before directing you back to sign-in.

DATA PRACTICES

How We Protect Account Records

We treat privacy as an operating task tied to each account step, from phone verification through wallet status and sign-in on mobile or desktop.

Data handling

We collect account, device, session, support, and payment-reference details for stated operational purposes. DANA or QRIS status helps us match a transaction, while wallet passwords remain outside our records.

Cookies and sessions

Cookies help maintain your signed-in session and remember privacy choices on the device you use. You can adjust browser cookie controls, although restricting them may interrupt account access or policy settings.

Account security

Phone verification is used before account access and when a security check is needed. Never send a wallet PIN or password through support; we use account details and references instead.

Retention process

We retain records while they support account operation, payment matching, security checks, disputes, or legal duties. After that need ends, records are removed, restricted, or kept only where required.

Correction requests

You may ask us to correct inaccurate account details by using the signed-in support panel. Include the requested change and registered phone number so we can verify the request safely.

Deletion questions

Where local law permits, you can ask whether deletion or restricted handling applies to your records. We will explain any account, payment, security, or legal reason that prevents immediate removal.

Privacy Policy Questions Before Opening

These questions address the privacy points you may check before opening a dewi28 account. Each answer relates to account access, payment references, cookies, security, or a direct request under the Privacy Policy, so you can decide what to provide and where to ask for help.

It covers account and phone verification details, sign-in and device signals, cookies, support messages, lobby activity records, payment references, retention, security controls, and requests to access or correct your data.

No. We may record a DANA or QRIS transaction reference and status to match activity to your account, but you should not send wallet passwords, PINs, or secret codes through our support route.

Phone verification connects account access to the registered number and helps us handle privacy or security requests. It may be required before sign-in or when a change needs confirmation.

Where local law permits, use the signed-in account support panel to ask what records we hold. Include your registered phone number and request subject so we can verify the account first.

Send a correction request through account support with the inaccurate field and the replacement detail. We will check the account before changing records, especially when the request affects payment matching or access.

We keep payment references while they are needed for transaction matching, account security, disputes, or legal duties. When that need ends, our retention process removes or restricts the records.

Yes. It applies when you sign in from a mobile browser or desktop, including cookies, session data, device signals, and phone verification. Cookie restrictions may affect the privacy settings shown.