Reference

Legal clarity for your ok4d account

ok4d Legal sets out how we handle account access, personal data, wallet records and policy requests before you enter the lobby.

Account termsData handlingLocal-law access
ok4d Legal clarity for your ok4d account
POLICY CONTACT

Where legal questions reach our team

A clear contact path matters when a policy question is connected to your account or a wallet record. Use the support route shown beside the account and cashier areas, then include the phone number on your account and the relevant receipt or reference. We use those details to locate the correct record without asking you to repeat the full history. Keep requests focused on access, data, account security or policy wording so our team can direct the next step.

Team online

Account access

If phone verification or account access stops at a policy check, send the account phone number through our support route. We can point you to the applicable Legal wording and explain which account step remains before access can continue where local law permits.

Wallet records

For a DANA, OVO, GoPay or QRIS record connected to a policy request, attach the receipt reference rather than sharing a wallet password or PIN. Our team uses the reference to separate payment status questions from broader Legal requests.

Policy requests

When you want a correction, copy of account data or clarification about retention, identify the request clearly in the contact form linked from your account area. We will use the supplied account details to assess the request and respond through the available support path.

DATA PRACTICE

How we apply ok4d Legal rules

Legal handling is tied to practical account events rather than broad statements. We record the details needed for phone verification, account protection, payment matching and policy requests, while keeping the account path…

Data handling

We use account data for phone verification, access checks, security controls and responses to Legal requests. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account records are used to match the correct account event.

Cookie use

Cookies can keep your signed-in session connected while you move from account pages toward the lobby. They may also support security checks. Browser settings can remove or restrict cookies, although that may require you to verify the account again.

Account security

We ask you to complete phone verification before account access and do not need your wallet PIN or password in a support message. If a request contains unusual account details, we may ask for another account check before changing records.

Record retention

Account, payment and support records are kept only while they serve an account, operational or legal purpose. A retention request can be raised through support, and we will assess which records can be removed against duties that may still apply.

Change requests

You can ask us to correct account details, clarify a Legal clause or explain how a particular record is used. Include the account phone number and a precise request so we can identify the relevant data without exposing another account.

Policy contact

Questions about access, data handling, cookies, retention or account security should use the support route connected to your account area. Keep your message factual, and never include a password, wallet PIN or full authentication code.

Answers about ok4d Legal access

These Legal answers cover the account decisions you are most likely to face before opening an account or requesting a policy change. We explain the local-law condition, the phone verification step, the treatment of payment references and the route for data questions. If your situation is specific, use the support path connected to your account and include only the details needed to identify the request.

ok4d Legal covers account access, phone verification, data handling, cookies, payment references, security checks, retention and policy contact routes. Access depends on local law, so the wording on this page should be read together with any account instruction shown during your access process.

Access depends on local law and may vary by location or circumstance. Before you continue, check the Legal wording displayed for your account and complete phone verification only if access is available to you. We cannot replace local legal requirements with an account request.

Phone verification helps connect the account to the correct contact detail before access is granted. It also helps us separate a genuine account request from an unauthorised change. We will not ask you to send a password, wallet PIN or full authentication code through support.

We use payment references to match a wallet or QRIS event with the correct account and support request. A receipt can help us locate that event, but it does not alter the Legal conditions or confirm access where local law does not permit the service.

Yes. Send a focused correction request through the account support route, including the phone number linked to the account and the detail you believe is wrong. We assess the request against account security and may ask for verification before changing personal records.

We retain records while they are needed for account operation, payment matching, security, support or a legal purpose. You can ask how a particular record is used or request a retention check. Some records may need to remain when another duty applies.

Use the support route linked from your account or cashier area and state whether the question concerns access, data, cookies, retention or a payment reference. Include only identifying details needed for the request, never your password, wallet PIN or authentication code.