Reference

Legal details for your cika4d account

cika4d keeps its Legal page focused on the rules behind account access, wallet checks, data use and policy requests.

Account termsData and cookiesPolicy contact
cika4d Legal details for your cika4d account
POLICY HELP

Three ways to resolve Legal questions

A clear contact route helps when a Legal clause affects your account or wallet status. Start with the support route shown beside the account and cashier areas, then include the phone number on your account and the payment reference if your question concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use those details to locate the relevant record without asking you to resend unrelated documents. If access depends on local law, our team can explain the applicable policy wording, but cannot promise access where local law does not permit it.

Team online

Account policy path

Use the account support route for questions about phone verification, identity details, access status or a policy clause. Include the exact wording you want clarified and the account phone number, so we can keep the reply tied to your own record.

Wallet status check

For a Legal question about DANA, OVO, GoPay or QRIS, send the payment reference and the wallet name shown at checkout. For bank transfer or virtual account matters, add the bank rail, such as BCA, BRI, Mandiri or BNI.

Policy change request

If a stored account detail is wrong, ask support to review the specific field and explain why it should change. We may request a matching account step before editing records, especially when the request affects phone verification or payment ownership.

RECORDS AND SAFETY

How we handle policy duties

Our Legal process is practical: we connect each request to the account record, payment reference or device session that created it.

Data handling

We use account details to operate access, connect a phone verification step with the right account, and match payment references to the requested transaction. A request about your data should identify the account field or record involved rather than only naming a general concern.

Cookie controls

Cookies can keep your session connected while you move from login to a Legal page or the lobby. If you clear them, you may need to verify the account again. Your browser settings control cookie removal, while our policy explains their operational purpose.

Account security

Phone verification is part of the account access path. Keep your phone details current and do not share account codes. If a device session looks unfamiliar, contact support with the account phone number so we can identify the access record and explain the next policy step.

Payment records

Wallet and bank records are handled by their named route: DANA, OVO, GoPay, QRIS, virtual account or bank transfer. A receipt reference helps us locate the event. BCA, BRI, Mandiri and BNI references should remain readable when you send a bank-related request.

Retention requests

Some records may need to remain available for account, payment or legal duties. You can ask which category applies to a record and request a change where local law permits. We assess the request against the current terms rather than removing a record automatically.

Contact ownership

Policy requests should come from the account holder through the account support path. We may compare the request with phone verification and payment details before discussing a record. This protects your account when another person knows a wallet reference or device detail.

Answers about cika4d Legal terms

These Legal answers address the questions you may search before opening an account or asking us to change a record. They cover access, data, cookies, payment references and contact steps without replacing the current terms. Where a rule depends on your location or a specific account record, the policy page and support route remain the right place to check the next step.

Our Legal page covers account access, phone verification, wallet and bank records, cookies, data handling, retention and requests for changes. It also explains that access depends on local law. Read the current terms before opening an account, then contact support if a clause or account step is unclear.

Access depends on local law and your eligibility under the current account terms. If your location permits access, use the normal account path and complete phone verification. We cannot describe access as available where local law does not permit it, so check the Legal terms before proceeding.

The Legal terms explain that each payment route creates its own status or reference. DANA, OVO, GoPay and QRIS are not treated as one shared wallet record. If a status needs checking, send the named rail and payment reference through support so we can match it to your account.

Phone verification connects the account request with the person asking for access and helps protect account records. Keep your phone details accurate and do not share verification codes. If the step fails, contact support with your account phone number instead of creating another account.

Send a request through the account support path and name the exact field you want changed, such as a phone detail or contact record. We may ask for an account step to confirm ownership. We assess correction or deletion requests where local law permits and explain any retention duty.

Cookies can preserve the session between login, the Legal page and the lobby on your browser. Clearing them may sign you out or require phone verification again. Your browser controls removal, while our terms describe the operational cookie purpose and the account effect of clearing them.

Use the support route beside your account or cashier area and describe the exact policy issue. Add your account phone number and any relevant payment reference, such as QRIS, virtual account or bank transfer. We will explain the applicable process, while access remains subject to local law.