Reference

Legal access for your kaset4d account

kaset4d sets out how Legal access, account records and policy requests work before you open an account.

Local-law accessAccount checksPolicy requestsPayment records
kaset4d Legal access for your kaset4d account
CONTACT ROUTES

Get help with a Legal request

A clear contact path helps you resolve a Legal question without sending the same request several times. Start from the account support route and include your registered phone detail, the relevant policy subject, and any receipt or reference connected to the request. We can then check access status, payment records, or a data change request against the correct account. If you are in Jakarta or elsewhere in Indonesia, the same account-based route keeps the request attached to your records.

Team online

Account access

If phone verification or an access decision affects your account, contact support from the account path and describe the exact message shown. Include your registered phone detail so we can match the Legal request without asking you to repeat unrelated account history.

Payment record

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, send the payment reference with your request. We use that reference to locate the relevant record and explain whether the issue concerns account matching, processing status or policy checks.

Policy change

To ask for a correction, deletion assessment or access to personal account details, identify the exact change you want. We may request account verification before acting, because Legal requests must not expose another person’s records or alter the wrong account.

RECORD HANDLING

How we handle policy and account records

Our Legal process is tied to practical account handling rather than broad promises. We record the details needed to maintain access, match payment activity and respond to policy requests.

Data access

You can ask what personal account details we hold and how those details relate to a Legal request. We may ask for phone verification before releasing account data, and we will limit the response to records connected with your verified account.

Data correction

If your account detail is inaccurate, tell us which field needs correction and provide the replacement detail. We check the request against the account record before changing it, especially where the detail also appears in a DANA, OVO, GoPay or QRIS payment trail.

Cookies

Cookies can keep your sign-in path consistent and help us recognise a security event across a session. If you clear them, your device may require another account check. Cookie controls do not remove records that we must retain for Legal or payment purposes.

Account security

We use phone verification and account-session checks to reduce mistaken access. Keep your sign-in details private and contact us if a device you do not recognise appears in your account history. We may pause an account review while we confirm who is requesting access.

Retention

Account, payment and support records may remain after a request when they are needed for dispute handling, accounting or a legal duty. We do not treat a deletion request as an automatic removal instruction; first we check which records the applicable rule requires us to keep.

Request owner

Our account support route is the starting point for Legal questions, including access, correction, retention and policy interpretation. State the request clearly, attach the relevant reference where applicable, and use the verified account path so the request reaches the correct record owner.

Answers about kaset4d Legal access

These Legal answers cover the account questions most often raised before access or after a policy request. We keep the wording practical: access depends on local law, account details must be verified when required, and payment records remain connected to the account that created them. If your situation is not covered, use the account support route with your registered details.

Access depends on local law. We do not describe the service as available in every location, and your eligibility may depend on the rules applying to you and the account details you submit. Check the current access wording before opening an account or continuing after a policy change.

Phone verification helps us connect a Legal request with the correct account and reduce mistaken access. We may use it before account access, a data response or a payment-record explanation. If the verification detail no longer works, contact support through the account path.

Yes. Send a clear correction request through the verified account support route and identify the field that is wrong. We may ask for additional confirmation before changing details that also appear in DANA, OVO, GoPay, QRIS, bank transfer or virtual account records.

Legal payment records show how an account transaction was matched and processed. We may retain references for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity when needed for account administration, dispute handling or a legal duty.

Cookies can support sign-in continuity and security checks, but clearing them does not remove account or payment records that we must retain. You can ask what data is held through the account support route, and we will assess the request against the applicable Legal requirement.

You can submit a deletion request through the verified account path. We first check whether the records are still needed for payment reconciliation, disputes, account security or a legal duty. Where retention is required, we explain that the affected records cannot be removed yet.

Use the account support route and label the request with the policy subject, your registered phone detail and any payment or access reference. This lets us identify the correct record and assess the matter under the current Legal wording where local law permits.