Reference

dewagame88 Privacy Policy for Your Account

dewagame88 Privacy Policy explains how we handle the account details behind your lobby access, including phone verification and wallet records for DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesContact requests
dewagame88 dewagame88 Privacy Policy for Your Account
CONTACT ROUTES

Check Privacy Questions Beside Wallet Help

A clear contact route matters when a privacy question appears during login or a cashier check. Use the support path shown beside the account and wallet area, and include the email or phone detail linked to your account only when needed for identification. We can then locate a request, explain its status and direct you to the right next step without asking for an unnecessary payment credential.

Team online

Account access

If phone verification or login creates a data question, contact us through the account support path. Tell us which step appeared and we can match the request with the relevant account record.

Wallet status

For a DANA, OVO, GoPay or QRIS reference, share the transaction date and status shown in your account. Do not send a wallet PIN; we need only enough detail to locate the record.

Data requests

Ask us to access, correct or clarify your account data through the policy contact route. We may request account details before responding so private records are not sent to the wrong person.

DATA PRACTICES

Browse How dewagame88 Handles Your Data

Our handling process follows the account journey rather than collecting every detail by default. We separate login and phone-verification records from payment references, use security checks around account access, and keep device…

Account records

We use phone verification details to connect you with the correct account and reduce mistaken access. Keep your phone number current, because an account change may require a matching verification step.

Payment references

A cashier record can include a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference. We use that reference to match status, not to request your private wallet PIN.

Cookies

Cookies may retain session settings or help us understand whether a page works correctly. Your browser controls can remove or restrict them, although some account steps may then need to load again.

Device signals

When you move from a mobile login to the lobby, limited device and session signals can support security checks. These signals help identify unusual access without replacing your account credentials.

Retention

We retain records for the period needed for account operation, security checks, dispute handling and applicable legal duties. Different records can therefore have different retention periods under this policy.

Your requests

You can contact us about a copy, correction, deletion request or policy question. We may verify your account first, then explain what can be changed and when the request is completed.

Find Privacy Policy Answers Before You Join

These Privacy Policy answers focus on the questions you may have before opening an account or using the lobby from Indonesia. We explain what data connects to phone verification, how wallet references are handled, what cookies do and where to send a request. Access remains subject to local requirements.

It covers account creation, phone verification, login sessions, device signals, cookies, support requests and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number for account identification and a verification step before access. This helps connect the correct person with the correct account and supports security when account details change.

Yes. It explains how we handle payment references and status details connected with DANA, OVO, GoPay and QRIS. We do not need your private wallet PIN to locate a cashier record.

Limited device and session signals may be recorded when you sign in or move from a mobile browser to the lobby. We use them for session operation and checks linked to account security.

Cookies can remember session settings and help us identify page problems. You can control them through your browser, but restricting cookies may require some account pages or verification steps to load again.

Yes. Send a correction request through the policy contact route and include enough account detail for identification. We may verify ownership before changing a phone, account or payment reference.

Use the support path shown beside the account or wallet area and state that your request concerns the Privacy Policy. We can explain data access, retention, correction and request status.