Reference

Legal Terms Before You Open Account

Legal clarity comes first: we show how your account, wallet records, cookies and access rules work before you join.

Indonesia access termsDANA record trailOVO wallet checksGoPay and QRIS receipts
king1 Legal Terms Before You Open Account
CONTACT ROUTES

Three Legal Contact Paths

A legal question should reach the team that can act on it, not a generic inbox. We route account access, wallet trace and data-change requests through channels that keep a record, so…

Live chat record Use live chat from the account menu when you need a timestamped conversation about terms, cookie consent or a wallet record. Our chat team is available daily from 09:00 to 23:00 Indonesia time.
Email request Send account or data-change requests by email when you need to attach DANA, OVO, GoPay or QRIS proof. Use the same email on your profile so we can match the request.
Account menu ticket Open a ticket from Profile, then Help, then Legal Request if you can still access your account. That path carries your account ID, device type and current contact details.
DATA CONTROLS

Six Ways We Handle Legal Requests

Your legal rights need clear handling, so we separate data access, cookie consent, wallet records and account-security actions.

Account matching

We match legal requests against your registered phone, email and recent login device before changing account details. This helps us avoid handing access to someone who only has a payment screenshot.

Payment record handling

DANA, OVO, GoPay, QRIS and bank transfer references are stored as wallet records for tracing deposits, withdrawals and disputes. We use them to confirm timing, amount and account ownership when you contact us.

Cookie choices

Cookie settings help keep sessions active, remember device preferences and support security checks. You can clear browser cookies on Chrome or Safari, but some account steps may repeat after clearing them.

Security alerts

If a login pattern changes, such as a new phone model or location shift, we may ask for an extra account check. Legal access still depends on local law and account status.

Retention requests

You may ask what account data we hold or request a correction when details are wrong. Some wallet and transaction records may need to stay for dispute handling and system audit purposes.

Change channel

For name, phone or email changes, start from Profile or email support with matching account details. We do not process legal data changes through public social comments or unrelated chat handles.

Questions About Your Legal Rights

These answers cover the legal points you are most likely to check before opening or using an account. They focus on eligibility, data access, wallet records, cookies, account changes and the contact route we use when you need a written response.

Access depends on local law, and you should only continue where local law permits. We may also apply account checks based on your location, device session and payment method before wallet access is enabled.

We may collect your name, phone number, email, device session, login timestamps and wallet references. These details help us manage account access, payment tracing, security checks and legal requests tied to your profile.

Send the request from your registered email or open a ticket from Profile, Help, then Legal Request. We may ask you to confirm your phone number or recent DANA, OVO, GoPay or QRIS reference.

Yes, but we check the request against your current account details first. Use Profile if you can log in, or email support with matching identity details and any recent wallet reference we can verify.

We keep DANA, OVO, GoPay, QRIS and bank transfer references so deposits, withdrawals and disputes can be traced. These records help confirm account ownership, timing and whether a wallet action was completed.

You can clear cookies from your browser settings on your phone or computer. After clearing them, you may need to log in again, repeat a security check or reset saved lobby preferences.

Start with live chat or email so the request is logged. If it involves account data, payment records or access rules, we route it to the team that can check records and reply in writing.