Reference

kepo66 Legal for Clear Account Access

kepo66 Legal brings our access rules, account duties and data-handling approach into one readable page, so you know what applies before opening an account.

Access depends on local lawPhone verification may applyPolicy requests stay account-linkedMobile and desktop access
kepo66 kepo66 Legal for Clear Account Access
POLICY CONTACT ROUTES

Where Legal Questions Reach Our Team

A clear contact route helps when you need a clause explained, an account detail corrected or a policy request linked to your profile. Sign in when possible, open the support area, and include the phone number connected with your account so we can locate the right record. If you are in Jakarta or elsewhere in Indonesia, our team can also check whether the requested access is available where local law permits.

Team online

Account policy request

Use the account support route for questions about Legal terms, phone verification or an access decision. Include the relevant section and your account phone number; we use those details to reduce back-and-forth before replying.

Wallet record question

If a Legal question concerns DANA, OVO, GoPay or QRIS records, send the payment reference shown in your account. We can review the account-linked status without asking you to share a wallet password or private authentication code.

Change request path

For a correction, deletion request or policy clarification, select the policy contact option in support and describe the requested change. We may ask for phone verification before discussing account-specific records or applying an approved update.

DATA HANDLING DETAIL

How We Handle Legal Requests

Legal requests are handled against the account record rather than through public messages. We use the details needed to verify identity, assess access where local law permits, answer the request and maintain…

Account details

We use account details such as your registered phone number to connect a Legal request with the correct profile. Keeping that number current helps us identify the request without exposing another person’s account record.

Cookies and sessions

Cookies can support login sessions, policy preferences and basic security checks in your browser. You can review browser cookie controls, but switching them off may affect the policy page, account session or phone verification path.

Security checks

Phone verification may be required before we discuss account-specific Legal details. Never send a wallet password, bank PIN or one-time code to support; our team does not need those secrets to process a policy request.

Record retention

We retain request records for the period needed to answer the matter, protect account security and meet applicable legal duties. Retention can differ by record type, so ask support which category applies to your request.

Request changes

You can ask us to correct account details, explain a policy decision or review a data-handling question. Describe the change clearly and include your registered phone number; verification may come before any account record is amended.

Account security path

If you suspect that someone accessed your account, contact support through the signed-in account route when available. We can focus the check on login history, phone verification and linked wallet status without requesting your private payment credentials.

Legal Questions Before Your Account

These Legal answers address the questions we expect you to ask before opening an account with kepo66. They cover eligibility, data requests, browser access, phone verification and payment records without replacing the policy wording itself. Read the full Legal terms first, then contact support through the account route if your situation needs a specific response.

Our Legal page covers access conditions, account duties, data handling, cookies, security checks, record retention and policy requests. It also explains how payment references such as DANA or QRIS may connect to an account record. The full policy wording applies where local law permits.

Access depends on local law and may differ by location or personal eligibility. Check the access wording before opening an account. If the account route asks for phone verification, complete that step only with your own current number and contact support if the result seems unclear.

Phone verification helps us connect a policy request with the correct account and reduce unauthorised disclosure. You may be asked to complete it before account access or before we discuss account-specific data. We will not ask for your wallet password or one-time authentication code.

Sign in, open the support area and select the policy contact route. State which account detail needs correction and include your registered phone number. We may verify your identity before changing the record, and we will explain if a legal or security duty prevents the requested change.

Yes. Legal explains how payment references may be connected with account records and used for security or request handling. DANA, OVO, GoPay and QRIS names provide context only; never send a wallet password, PIN or one-time code when asking about a record.

Cookies may keep a browser session active, remember required settings and support security checks. Your browser controls can restrict them, although that may affect login or phone verification. The Legal terms explain the relevant handling, and support can clarify a cookie-related account question.

Use the support route inside your account and identify the Legal section or decision you want explained. Add your registered phone number and any reference shown on screen. We may request verification before discussing private records or confirming whether access is available where local law permits.