Reference

Terms & Conditions for cawan 4d

cawan 4d Terms & Conditions explain how you open, use and protect your account before you enter the lobby.

Account accessWallet checksLocal eligibilityPolicy contact
cawan 4d Terms & Conditions for cawan 4d
TERMS SUPPORT

Where To Ask About Account Conditions

A clear contact path matters when a condition affects your account, so we keep policy questions connected to the account and cashier areas.

Account access questions If phone verification or a sign-in condition stops your account path, contact us from the support route shown after you open the account area. Include your account identifier and the exact message on screen so we can match the question to the relevant Terms & Conditions clause.
Payment condition checks For a DANA, OVO, GoPay or QRIS record, send the reference shown in your account rather than a full wallet password or security code. We use that reference to check whether the stated payment condition, verification step or account-name rule applies to your request.
Policy change requests If you need clarification about a wording change, account correction or data request, identify the section and explain the result you need. We will route the message to the policy contact path and tell you what account evidence is required before action is taken.
ACCOUNT SAFEGUARDS

How We Apply These Conditions

We apply the Terms & Conditions through ordinary account checks rather than hidden steps. Phone verification confirms the account path, payment references help us match a transaction, and browser or device details…

Phone verification

Before account access is completed, we may ask you to verify the phone detail attached to your account. This step helps us distinguish an account-holder request from an unfamiliar sign-in and gives our support team a specific record to check when a condition is questioned.

Payment records

A wallet or bank record is handled against the account details and reference supplied during the transaction. DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI may appear in the available payment path, subject to the conditions shown for your account.

Cookies and browsers

Cookies can keep an approved session consistent and help us detect unusual access across a phone, tablet or desktop browser. Clearing them may require another sign-in or phone check; that device behaviour does not remove your duty to follow the Terms & Conditions.

Account security

Keep your sign-in details private and tell us promptly if the account path looks unfamiliar. We may pause a request while checking ownership, payment evidence or phone verification. We do not ask you to place a password or security code in a support message.

Record retention

We keep account, payment and support records for operational handling, dispute checks and applicable legal duties. The period can depend on the record type and local requirements. A request about stored details should name the account and the specific record you want us to examine.

Correction requests

You can ask us to correct an inaccurate account detail or explain how a policy condition was applied. Send the request through the account support route, include the relevant section and complete any ownership check needed before we alter or disclose account information.

Terms & Conditions Questions Answered

These Terms & Conditions answers focus on the decisions you may face before opening an account or requesting account help. We explain the practical path for Indonesia, from local-law eligibility to phone verification, payment records and data requests. If your situation is not covered here, quote the relevant clause when you contact us so the answer stays tied to the written policy rather than a general lobby description.

You can read the Terms & Conditions on this policy page before completing account access. Keep the page open while you check phone verification, wallet records or a request involving DANA, OVO, GoPay and QRIS. The written clause controls if a general message elsewhere appears different.

Eligibility depends on local law. Your location, account details and the applicable access rules can affect whether an account or feature is available. If you are in Jakarta, Surabaya or another Indonesian location, use the account path shown to you and ask support about any restriction.

Phone verification links the account request to the contact detail supplied during opening. It helps us check ownership before account access, payment handling or a sensitive account change. If the code does not arrive, contact support with the screen message and avoid sending your security code.

DANA and QRIS may be shown as payment rails for an eligible account, alongside OVO, GoPay, bank transfer or virtual account. Follow the displayed account-name and reference steps. A payment option being visible does not remove phone verification or other Terms & Conditions checks.

We use account, device, payment and support details to operate access, check requests, protect the account and meet applicable legal duties. Cookies may support session security. Ask us to examine or correct a specific record through the account support route after ownership checks.

Quote the section that concerns you and describe the account step or payment record involved. We will review the request against the written Terms & Conditions and tell you which ownership or transaction evidence is needed. A policy explanation does not override local-law requirements.

We may update the Terms & Conditions when operating requirements or applicable law changes. Check the current policy page before using an account feature or sending a payment request. If a change is unclear, contact us with the section heading and the account action you planned.