Reference

Privacy Policy for Your dewaasia Account

Our Privacy Policy explains how dewaasia handles the details you provide when you open an account, sign in, use the lobby or check DANA, OVO, GoPay and QRIS…

Account dataWallet recordsDevice cookiesPolicy requests
Browse Our Lobby Read FAQ
dewaasia Privacy Policy for Your dewaasia Account
CONTACT THE TEAM

Privacy Help Beside Your Account Path

A clear contact route matters when a Privacy Policy question concerns your own account rather than a general page. We ask you to sign in first when possible, because the account help route lets us identify the relevant record without asking you to send sensitive details in an open message. If login or wallet status stalls, describe the issue and include the receipt reference available in your account. We use the same route for access, correction and deletion requests where local law permits.

Team online

Account help route

Sign in and send your Privacy Policy question through account support. We can connect the request to your phone verification and account record, helping us avoid confusion between separate DANA, OVO, GoPay or QRIS activity.

Receipt and status check

If a wallet record needs attention, include the payment method and receipt reference shown in your account. We use those details to locate the relevant event without requesting your full wallet password or unnecessary personal content.

Access request

Ask us to explain, correct or provide account data through the same support path. State the request clearly, complete any identity check we require, and tell us whether it concerns login, cookies, payments or another policy item.

DATA HANDLING

What We Protect Behind the Lobby

Our Privacy Policy is designed around practical account events: opening access, verifying a phone, returning to the lobby on mobile and checking a payment record.

Account details

We use the details connected with your account to create access, complete phone verification and respond to account requests. Keeping those details accurate helps us identify your record when you ask for a copy, correction or explanation under the Privacy Policy.

Wallet records

A DANA, OVO, GoPay or QRIS event may create a reference, status and account link needed to check a receipt. Bank transfer and virtual account records can require the same trace. We use these records for the stated payment and support purpose.

Cookies and devices

Cookies and device signals can support a continuing login session, remember a selected path and help identify unusual sign-in behaviour. On mobile, these signals relate to the browser or device path you use to reach the account and lobby.

Security controls

Phone verification is an account step before access, and security checks can accompany a support request or account change. We do not ask you to place a wallet password in a support message. Share only the reference needed to locate your record.

Retention choices

We keep a record while it serves the purpose explained in the Privacy Policy or while a legal, security or account matter requires it. When that need ends, handling follows our retention process and applicable local requirements rather than an open-ended schedule.

Policy changes

If the Privacy Policy changes, we present the updated wording on this page and identify the practical subject affected. Check this page before opening an account or changing wallet details, then contact us if a clause needs clarification for your situation.

Privacy Policy Questions Before Account Access

These Privacy Policy answers focus on the questions you may have before phone verification, mobile login or a wallet status check. We keep the wording tied to dewaasia account activity, rather than describing unrelated services. If your question depends on your location, payment record or account history, use the support path after signing in where possible. Access depends on local law, and we may need enough detail to confirm which record your request concerns.

The Privacy Policy covers data connected with browsing, account creation, phone verification, login, device cookies, wallet status and support requests. It explains why we use those records, how retention applies and how you can ask about access or correction where local law permits.

Phone verification connects an account request to the correct access record and helps us handle sign-in or support questions safely. The Privacy Policy explains how that phone detail is used for the account purpose, rather than treating it as a general marketing contact.

Yes. A DANA or QRIS action can produce a payment reference, status and account link used to check a receipt or resolve a support question. OVO, GoPay, bank transfer and virtual account records follow the same policy purpose when connected with your account.

Cookies can support a continuing session, remember a device path and help us identify unusual login behaviour. They do not remove your Privacy Policy rights. Ask support what cookie or device record is relevant, and we will explain the available request path where local law permits.

You can request access, correction or an explanation through account support. Sign in first when possible, name the record or issue, and complete an identity check if requested. We assess the request under the Privacy Policy and local requirements before responding.

Retention depends on the record and its purpose. Account, security and payment references may remain while they support access, receipt checks, disputes or legal duties. The Privacy Policy does not treat every record alike, and support can explain the relevant category.

Yes, you can ask us to delete or restrict a relevant record through the account support path where local law permits. We first confirm your account and assess whether security, payment tracing or a legal duty requires some data to remain.

Related Pages

dewaasia Indonesia About Us FAQ Speed Blackjack Live Ceme Keliling Room