Reference

calon4d Legal Terms for Your Account

calon4d sets out the Legal terms behind account access, payment records and policy requests in one place.

Account termsData handlingPolicy requestsLocal access
calon4d calon4d Legal Terms for Your Account
CONTACT ROUTES

Find Policy Help Beside Your Account

Legal questions are easier to resolve when you send the account detail connected to the request.

Account access If a Legal question concerns login or phone verification, use the support link inside your account and state which step stopped. We can then match the request to the relevant account record.
Wallet records For a policy question about DANA, OVO, GoPay, QRIS or a bank transfer, open the cashier support route and include the transaction reference. Do not send a wallet PIN.
Data requests To ask about stored details, cookies or a correction, choose the policy contact path displayed on the site. We may ask you to confirm account ownership before discussing personal records.
DATA PRACTICE

Understand How We Handle Policy

Legal practice is part of the account flow rather than a separate promise. We record the details needed to operate access, confirm account ownership and trace payment status, while keeping requests tied…

Account data

We use the account details you submit to create access, complete phone verification and respond to account-specific Legal requests. Keeping your name and contact details current helps us match later requests correctly.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account action can create a transaction record. We use that record to check status and resolve a cashier question, not to request your wallet PIN.

Cookies

Cookies may keep your session connected to the correct account and remember essential page settings. You can manage browser cookie controls, although changing them may interrupt login or policy-request steps.

Account security

Phone verification is an account step before access, and support may ask for ownership confirmation before discussing stored details. Never place a password, wallet PIN or full security code in a support message.

Record retention

We retain account, support and transaction records for the period needed for account operation, security checks and applicable Legal duties. A deletion request may not remove records we must keep for those purposes.

Policy changes

When wording or account conditions change, we place the current Legal text on this page or the connected account path. Check the displayed version before opening an account or submitting a policy request.

Check Legal Answers Before Joining

These Legal answers cover the questions we expect you to ask before opening an account. If your situation is different, use the account support route and describe the exact policy point, payment record or access step you need us to check.

It covers account conditions, phone verification, data handling, cookies, transaction records, retention and policy requests. It also explains that account eligibility and access depends on local law.

Access is available only where local law permits. Check the current Legal wording for your location before creating an account, and do not continue if local rules prevent this type of access.

Phone verification helps connect an account to the correct contact detail and supports ownership checks. It may be required before account access or before we discuss a data or cashier request.

DANA and QRIS activity can produce transaction records used to check cashier status and resolve account questions. We do not need your wallet PIN, and you should never include it in a message.

Yes. Use the policy contact path shown on the site, identify the account detail that needs correction and complete any ownership check we request before changes are made.

You can submit a removal request through the displayed support path. Some account, security or transaction records may remain when retention is needed for applicable Legal duties.

Use the support route inside your account or the policy contact path connected to the site. Include the relevant reference and policy subject, but omit passwords, wallet PINs and security codes.