Reference

dewi788 Terms & Conditions for Your Account

Our Terms & Conditions set the rules for opening an account, using DANA or QRIS, entering the lobby and requesting account help.

Account stepsWallet rulesLocal access
dewi788 dewi788 Terms & Conditions for Your Account
HELP WITH TERMS

Where to Ask About Account Rules

A clear support route helps when a Terms & Conditions question affects your account or wallet status.

Account questions Send your question through the account help route when a clause affects login, phone verification or access to the lobby. Include the wording you are asking about so we can respond precisely.
Wallet status For DANA, OVO, GoPay or QRIS questions, provide the payment reference and receipt status. We use those details to separate a wallet delay from an account rule or verification request.
Policy changes Ask us to clarify a revised clause before continuing. We will point you to the relevant Terms & Conditions wording and explain which account step or access rule it affects.
DATA AND SECURITY

How We Handle Policy Requests

Our policy process connects account security with clear data handling. We use the details needed to verify your account, record wallet activity and answer Terms & Conditions requests, while access from a…

Account data

We use submitted account details for account access, phone verification, payment matching and support replies. Keeping your registered details current helps us apply the Terms & Conditions to the correct account.

Cookie settings

Cookies can keep a session connected while you move from login to the lobby. Your browser controls whether cookies remain available, but changing them may affect access to account pages.

Login security

Keep your password and phone access private, and sign out on a shared device. We may pause an account check when login details or verification records appear inconsistent.

Record retention

We retain account, receipt and policy-contact records for the period needed to operate the service, check account history and respond to Terms & Conditions requests.

Change requests

To request a correction, explain which account detail or policy record is inaccurate through account support. Include your registered phone details so we can locate the right record.

Policy contact

Questions about data use, cookies or account clauses belong in the same support path. Mention the section or wording concerned, and we can direct the request to the relevant team.

Terms & Conditions Questions Answered

The answers below address the account and access points we are asked about most often. They are written for Indonesian account holders comparing the wording before opening an account, using a local wallet or asking for a policy change.

They are the rules covering account creation, phone verification, lobby access, wallet activity, data handling, policy changes and support requests. Read them before opening an account so you understand each required step.

Yes. Account eligibility and service access depends on local law. We provide access where local law permits, and you are responsible for checking that your use is allowed in your location.

Yes. They explain how wallet records and receipts relate to your account. DANA and QRIS activity must match the account details shown to us, while the final status appears in your account.

Phone verification helps connect the account to the correct contact detail before access begins. If the registered number cannot be confirmed, the account may need a support check under the stated terms.

Yes. Use the account help route and state which detail is incorrect. Include your registered phone details and the relevant record, such as a receipt or account field, for a focused check.

A revised Terms & Conditions version applies from its stated publication date. Before continuing, read the changed wording and contact support if you need a clause explained or an account step confirmed.

Include your registered phone details, the section or wording concerned, and any related DANA, OVO, GoPay, QRIS or bank transfer reference. This gives us enough context to check the request.