Reference

Legal terms for your jiso4d account

jiso4d Legal explains how we handle account access, identity checks, payment records and policy requests before you open the lobby.

Account conditionsWallet recordsPolicy requestsLocal-law access
jiso4d Legal terms for your jiso4d account
POLICY HELP PATH

Where to ask about Legal terms

A clear contact path helps when a Legal question concerns your account rather than a general browsing issue. Start from the support route attached to your signed-in account and include the relevant policy topic, transaction reference or phone-verification status. We can then direct the request to account access, wallet records or a change request. Keep your receipt available when asking about DANA, QRIS or bank transfer activity, and do not send a password or one-time verification code.

Team online

Account access

If your Legal question concerns phone verification or a blocked sign-in, use the signed-in account support route where available and describe the exact step that stopped you. We use that account context to separate an access request from a wallet-status question.

Payment records

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, attach the receipt reference and date through the account contact path. We can check the matching account entry without asking you to disclose a password or one-time verification code.

Policy changes

To ask about a correction, deletion or wording change, name the Legal section and explain what you want changed. We may request account details needed to locate the record, while keeping the request tied to the applicable local-law access conditions.

RECORDS AND CONTROLS

How we handle Legal requests

We keep the Legal process practical: you can identify the account record, state the request and receive a response through the account contact path.

Data handling

We use the account details and transaction references needed to address a Legal request, such as confirming a DANA receipt or locating a phone-verification step. We keep the request focused on its stated purpose instead of asking for unrelated personal details.

Cookies

Cookies can preserve a signed-in session and remember the Legal page path on your device. Clearing them may sign you out or require the account steps again; it does not erase payment records, policy requests or account data by itself.

Account security

Phone verification comes before account access where our flow requires it, and we do not ask for your password or one-time code in a Legal contact request. Review the device session after signing out, especially when moving between mobile and desktop.

Data retention

We retain account, payment and policy-request records for the period needed to operate the account, address disputes and meet applicable duties. A retention question should name the record type, such as a QRIS reference or account contact request.

Requesting changes

You can ask us to correct account details or clarify how a Legal record is used through the account contact path. Include the affected field and your reason; we may verify account control before changing phone, wallet or identity data.

Policy contact

For a Legal interpretation, quote the section heading and describe the situation in plain English. Our response depends on the account record and local law, so the same wording may not apply when access is unavailable in your region.

Answers about jiso4d Legal access

These Legal answers address the searches we hear before an account is opened or a policy request is sent. They cover account rights, data handling, payment references, cookies and local eligibility. If your situation is specific, use the account contact path with the relevant section name and receipt or verification detail.

jiso4d Legal covers account creation, phone verification, use of the lobby, wallet records, cookies, retention and requests to correct or remove certain data. It also explains that access depends on local law, so read the current terms before opening Dragon Tiger or another available category.

You can send a data request through the account contact path and identify the records you need, such as profile details, policy requests or DANA and QRIS references. We may verify account control first, then assess the request under the applicable Legal terms and local law.

Legal treats wallet and QRIS details as account-linked payment records used to match status, receipts and related requests. Include the date and reference when asking about a transaction. We do not need your password or one-time code to begin that record check.

Tell us which account field or policy record is inaccurate and provide the reason through the account contact route. We may ask for verification before changing phone, identity or wallet-related details. The result depends on the record, retention duties and local law.

Yes. The same Legal terms apply when you sign in from a phone, tablet or desktop, although clearing cookies can require another sign-in or phone-verification step. Device sessions and account records remain connected when you move from mobile access to the lobby.

Where local law does not permit access, we do not present the account or lobby as available to you. Eligibility depends on local law, and the Legal wording should be read with that condition. Contact us through the account route if your location status appears incorrect.

Use the support route shown with your signed-in account and state whether the request concerns access, data, cookies, retention, payment records or policy wording. Add a receipt reference for bank transfer or virtual account questions, but never include a password or one-time code.