Reference

Open jy4d legal terms with clarity

Clear account terms, DANA, OVO, GoPay and QRIS wallet rules, and eligibility wording are set out here before you open your account.

Access depends on local lawDANA wallet rulesOVO receipt checksGoPay and QRIS recordsSupport 10:00-24:00 WIB
jy4d Open jy4d legal terms with clarity
LEGAL CONTACT

Contact us about legal questions

Legal questions should reach a person who can trace your account, not a generic mailbox with no context. We keep contact paths open from 10:00 to 24:00 WIB through live chat, WhatsApp and email, and we may ask for your account ID, wallet reference, device type and the term you are asking about. For privacy requests, use the same name and mobile number that sit on your account.

Team online

Live chat

Use live chat from the account menu when you need a fast legal clarification. Share your account ID, the policy line you mean, and any DANA, OVO, GoPay or QRIS reference linked to the issue.

WhatsApp line

Send a WhatsApp message during 10:00-24:00 WIB if you cannot reach the account menu. We confirm your mobile number first, then route wallet, access or data requests to the right internal queue.

Email desk

Email [email protected] for requests that need written follow-up. Include your registered name, account ID, payment rail used, device path and the exact legal term you want us to check.

DATA HANDLING

Manage data, cookies and account security

Legal care also means knowing what happens after you create an account. We store account, wallet and session records so we can verify access, settle disputes, secure logins…

Account data

We keep the name, mobile number, login history and account ID you provide so access can be checked.

Payment records

DANA, OVO, GoPay and QRIS records are stored with amount, time and reference code.

Cookies

Cookies remember session status, language choice and device behaviour such as mobile browser size.

Security checks

When a new device signs in, we may ask for an extra code or account detail.

Retention period

We retain legal, account and payment records only as long as needed for operations, dispute handling, security checks and lawful…

Change requests

Ask for correction through chat, WhatsApp or [email protected] using your registered contact.

Find answers before you open account

These questions cover the legal matters we are asked about most often before and after account creation. Use them to understand account access, wallet records, cookies, correction requests and contact timing. If your case involves a payment reference or device issue, keep the DANA, OVO, GoPay or QRIS receipt ready before you message us.

Our account terms cover access, identity checks, wallet records, cookies, security steps and dispute contact paths. By opening an account, you agree that access depends on local law and our account checks must be completed.

Yes. Account access and eligibility depends on local law. If a rule in your area affects access, we may ask for more detail, pause a feature, or explain the term before you continue.

We keep payment rail name, amount, time, reference code and account match status. These records help us trace wallet disputes, confirm withdrawal checks and answer legal questions tied to your account activity.

Yes. Contact us through live chat, WhatsApp or [email protected] using your registered mobile number. We check your request against account history and wallet references before changing name, contact or security data.

Cookies help remember session status, language choice and device behaviour while you read terms or move back to your account. Clearing cookies may end your session and require another login check.

Chat agents first confirm your account identity, then route legal, privacy or wallet questions to the relevant queue. Complex requests may move to email so you receive a written reply with clear next steps.

A name mismatch can delay wallet checks or withdrawal processing. We may ask for a corrected account detail, a clearer receipt, or confirmation from the registered mobile number before the request moves forward.