Reference

dewi12 Legal Terms For Your Account

dewi12 Legal sets out how account access, personal data, wallet records and policy requests are handled for Indonesia.

Account accessData requestsWallet recordsPolicy contact
dewi12 dewi12 Legal Terms For Your Account
CONTACT ROUTES

Get Help With A Legal Request

A clear contact route matters when your question concerns Legal rather than a lobby title or wallet screen. We ask you to keep the account identifier, the relevant date and any receipt reference ready, because those details help us locate the correct record without exposing unrelated account information. Use the support contact path shown inside your account, especially for access questions, data corrections or a request about a DANA, OVO, GoPay or QRIS record. Players in Yogyakarta can follow the same online account route as customers elsewhere in Indonesia.

Team online

Account contact

For a Legal question about your account, open the support contact path after signing in and include your account identifier. We use that step to connect the request with the correct profile before discussing access, phone verification or a change to your submitted details.

Payment record

If your question concerns a DANA, OVO, GoPay or QRIS entry, send the receipt reference and date through the account support route. A bank transfer or virtual account reference can also help us separate a payment-status query from a broader Legal request.

Access query

When access is unavailable, tell us the device path you used, such as a mobile browser or desktop browser, and describe the message shown. We can then assess the account step and explain whether access depends on local law or requires further verification.

DATA PRACTICE

How We Handle Legal Details

Legal questions often involve information that should not be repeated across several channels. We keep the handling process tied to your account, the specific request and the record needed to resolve it.

Data handling

We use account details for clear operational purposes such as phone verification, access checks, payment matching and responding to a Legal request. When you contact us, share only the information needed to identify the relevant account event rather than sending unrelated personal records.

Cookie choices

Cookies and similar browser records can help retain an account step or recognise a session on your mobile or desktop browser. Your Legal question can include a request about these records, and we will explain the available handling route connected with your account.

Account security

Phone verification is part of the account access path before account details can be discussed. Keep your sign-in information private and contact us through the signed-in support route when a Legal request involves an unfamiliar access event or a detail you did not submit.

Retention records

We retain records for the operational and policy reasons attached to an account, payment reference or support request. If you ask how a particular record is kept, identify its date and type so we can assess the request against the applicable Legal requirements.

Change requests

To request a correction to your name, phone detail or account record, sign in and use the account support contact path. We may ask for verification before changing information, because the request must relate to the account holder and the specific record.

Policy owner

Our support contact path is the starting point for Legal questions, including data access, correction, cookie handling and account closure requests. Include a short description and the relevant account step; we route the matter internally without requiring you to repeat it publicly.

Legal Questions About dewi12

These Legal answers address the account and data questions you may have before opening an account or contacting us. We keep the wording practical: what information is checked, which payment references may be used, how a request starts and why local conditions matter. If your question is not covered, use the support contact path inside your account and include the relevant date or account step.

The dewi12 Legal policy covers account access, phone verification, personal data, cookies, payment references, retention and requests to correct or discuss account information. It also explains that access depends on local law, so you should check your eligibility before continuing with the account path.

No single access statement applies to every location or situation. Our Legal position is that access depends on local law and may require account or phone verification. If you are in Jakarta or elsewhere in Indonesia, use the stated account path and follow any location-based restriction shown.

Sign in, open the account support contact path and describe the exact data you want changed, such as a phone detail or name record. Add the relevant account identifier, then complete any verification we request before the Legal change can be assessed.

Yes. A Legal request can concern a DANA or QRIS receipt when the question involves account records, payment matching or data handling. Send the date and receipt reference through the signed-in support route. OVO, GoPay, bank transfer and virtual account records can be handled in the same way.

Cookies and browser records may support a session or preserve an account step on mobile and desktop browsers. For a Legal question about cookie handling, contact us through the account route and identify the device path involved. We will assess the request against the applicable policy.

Use the account support contact path and state which record you mean, such as a phone verification event, payment reference or support message. Include its approximate date and your account identifier. We may verify ownership before discussing stored information or the available Legal response.

Describe the access problem through the available support contact route and include the device path, date and message shown. Do not send private sign-in details in a public message. We may need to confirm account ownership before discussing data, access or a policy request.