Reference

Open the dewi11 link Privacy Policy

The dewi11 link Privacy Policy shows how we use account, device and wallet details when you open the lobby from Indonesia.

Account data explainedWallet records namedCookie choices coveredDirect request path
dewi11 link Open the dewi11 link Privacy Policy
ASK OUR TEAM

Contact Us About Privacy Policy

A clear contact path matters when you want to ask about the dewi11 link Privacy Policy. Use the account support route shown beside the sign-in and cashier areas, and include the email or phone detail linked to your account so we can locate the right record. If your question concerns a DANA or QRIS reference, keep the payment receipt available while we check the request.

Team online

Account privacy request

Use the account support path to ask what personal details we hold or why a phone verification record appears. Include your registered contact detail and a short description of the request, without sending your password or full wallet security code.

Wallet record question

For a DANA, OVO, GoPay or QRIS record, share the payment reference and approximate date through support. We use those details to locate the relevant transaction entry, while keeping your wallet PIN, one-time code and complete banking credentials out of the message.

Access and cookie help

If the Privacy Policy or its request form does not open on your phone, tell us the device type and browser path you used. We can help you reach the policy contact route without asking you to disable account security or reveal sign-in credentials.

DATA HANDLING

Browse How We Protect Your Policy Rights

We keep the Privacy Policy practical by linking each data use to an account, payment, security or support task.

Account details

We use your contact and verification details to create, maintain and protect your account. A phone verification step can be linked to access events, so we can examine an account question without relying only on a display name or an incomplete support message.

Payment references

DANA, OVO, GoPay and QRIS references help us match a wallet status or receipt to the correct account request. Bank transfer and virtual account identifiers are handled for the same checking purpose, not as a request for your banking password or wallet PIN.

Cookies and sessions

Cookies may retain a session choice or help us see whether a policy page loads correctly. You can review cookie controls in your browser, and clearing them may sign you out or require the phone verification step again when account access is checked.

Security signals

Sign-in time, device type and browser details can help us spot an unusual account access pattern. If a security check interrupts your path from a phone to the lobby, support may ask for account identifiers, but never your password or one-time code.

Retention approach

We retain records only for the period needed for the stated account, payment, security or support purpose, or when a legal duty requires longer storage. When a record is no longer needed, our handling process is designed to remove or anonymise it where applicable.

Your data request

You can contact us to request access, correction or deletion of eligible personal details, and to ask about processing connected with your account. We may verify your identity before acting, which protects the record from being changed by someone else.

Browse Privacy Policy Answers

These Privacy Policy answers address the searches we hear most often from people considering an account with dewi11 link. Each response points to a practical account step, payment record or privacy request route, so you can decide what to share and how to contact us. If your situation is not covered, use the support path rather than sending sensitive credentials in a message.

It covers personal details used for account creation, phone verification, sign-in security, payment reference checks, cookies and support requests. It also explains how you may ask about access, correction or deletion of eligible records, with access depending on local law.

We may collect contact details, phone verification results, sign-in events, device and browser details, plus messages you send to support. If you use DANA, OVO, GoPay or QRIS, we may also receive a payment reference needed to check account status.

Yes. The Privacy Policy covers payment references connected with QRIS, DANA, OVO and GoPay, along with bank transfer and virtual account identifiers. We use these records to match a receipt or status question, not to request your wallet PIN.

Use our privacy contact route through account support and state that you want access to your personal data. Include the contact detail attached to your account so we can verify the request. We may ask for an identity check before releasing records.

You can ask us to correct eligible account details through the same privacy contact path. Describe the field that needs changing and provide the updated value carefully. We may confirm your identity and account ownership before applying any change.

Cookies can preserve a session preference and help us see whether the Privacy Policy page works on your browser. Clearing or blocking them may sign you out, remove saved choices or require phone verification again when you return to account access.

You may ask for deletion of eligible personal data through our privacy contact route. We first check the request and may retain limited account, payment or security records where a legal duty or unresolved support matter requires it. Eligibility depends on local law.