Reference

Privacy Policy for Your dwg388 Account

Our Privacy Policy explains what we collect when you open a dwg388 account, use DANA or QRIS, and move between the lobby and cashier.

Account dataWallet recordsCookie choicesSecurity requests
dwg388 Privacy Policy for Your dwg388 Account
REQUEST ROUTES

Where To Ask About Your Data

You can ask us about this Privacy Policy from the account help route when a data question is connected to your login or wallet record.

Account help Use the account help route for questions about your phone number, verification record, sign-in…
Wallet status For a DANA, OVO, GoPay or QRIS privacy question, share the transaction reference and…
Security concern If a device session looks unfamiliar, contact us through account help and describe the…
DATA CONTROLS

Six Privacy Practices Behind Your Account

Our handling of personal data follows the practical steps you encounter while using the account: phone verification, wallet status checks, browser sessions and support requests.

Account details

We may collect your phone number, account identifier and verification result when you open an account. These details help us connect sign-in activity with the correct record and respond to a request about access. We do not need your password in a support conversation.

Payment references

When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we may keep a reference, amount status and processing time. The record helps us match a cashier event without requiring you to disclose a wallet password, card secret or one-time code.

Cookie operation

Cookies and similar browser storage may keep an account session active, remember a language or show whether a page loaded correctly. You can adjust cookie controls in your browser, though blocking certain storage may require another sign-in or affect policy access.

Device security

Browser type, operating system, approximate session timing and security events may be recorded when you sign in from a phone or desktop. We use these signals to spot unusual access and protect the account, not to request private device passwords.

Retention choices

We retain personal data while it supports account operation, payment reconciliation, security checks, dispute handling or a legal requirement. When a record no longer serves one of those purposes, our internal process can remove or separate it according to applicable local requirements.

Change requests

To request correction, access or deletion where available, contact account help with your account identifier and a clear description of the record. We may verify ownership before making a change, and we will explain if a payment or legal record must remain stored.

Privacy Policy Questions About dwg388

These answers focus on the account and payment questions we hear most often before someone opens access. They explain what the Privacy Policy covers, how to send a request and why we may need a verification step. If your case involves a specific wallet reference, use the account help route so we can look at the correct record.

The dwg388 Privacy Policy covers account details, phone verification, device sessions, cookies, support messages and payment references linked with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security handling and ways to request access or correction.

We use your phone number to create and identify your account, complete the required verification step and help protect sign-in access. If you contact us about a record, the number helps us locate the correct account. Never include a password or one-time code.

Yes. The Privacy Policy covers payment references connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. We may keep status, timing and reference details so we can reconcile an account event without asking for your wallet credentials.

Use the account help route and state which detail needs correction, such as a phone number or account identifier. Include enough information for us to locate your record, but not your password. We may verify account ownership before changing or disclosing personal data.

Cookies or browser storage may keep your session available, remember a language choice and show whether account pages load correctly. You can manage cookie settings in your browser. Removing them may sign you out or require phone verification again when you return.

We keep data while it is needed for account operation, payment reconciliation, security checks, dispute handling or a legal requirement. Retention can differ by record type and local rules. When a record is no longer needed, our process can remove or separate it.

You can contact account help to request details about the personal data linked with your account. Tell us the account identifier and the area concerned, such as verification, cookies or a QRIS reference. We may confirm ownership before providing a response.