Reference

jempolhoki Legal for Clear Account Access

jempolhoki Legal sets out how account access, wallet records and policy requests work before you open an account.

Account termsLocal-law wordingPolicy contact pathWallet record clarity
jempolhoki jempolhoki Legal for Clear Account Access
CONTACT ROUTES

Legal Help for Account and Wallet Questions

A clear contact route helps when you need a policy answer rather than a general lobby response.

Account access Use the signed-in account support route when Legal access is unclear.
Wallet records For DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri or BNI records, quote the visible…
Policy changes If you want to question, correct or remove account data, state the exact request…
DATA PRACTICE

How We Handle Legal Data Requests

We handle Legal requests around the records needed for account access and payment tracing, not as open-ended profile collection.

Account data

We use the details connected to your account to match an access or correction request.

Cookie choices

Cookies may support sign-in continuity and account settings on your device.

Security checks

We do not ask for your password in a Legal request. Keep your phone verification details private, and contact us…

Record retention

Some account, wallet and support records may need to remain available for policy, dispute or legal reasons.

Request owner

We treat the account holder as the person making a data request.

Policy updates

When a Legal term changes, we place the updated wording in the policy area and retain the applicable account context.

Legal Answers Before You Open an Account

These Legal answers address the questions we expect before an Indonesian account is opened. We focus on access wording, personal data, cookies, payment records and contact steps, so you can decide what to do before entering details or connecting a wallet.

Legal covers account access, policy terms, personal data, cookies, security requests, retention and wallet records. It also explains how to contact us when a question concerns DANA, QRIS or another listed payment record.

Access depends on local law. Check your local position before opening an account, and do not treat the presence of DANA, OVO, GoPay or QRIS as permission where local rules do not allow access.

Start from the signed-in account support route and identify the relevant request. We may ask for the phone verification step linked to your account, but we will not ask you to share your password.

We use the reference needed to match a wallet or transfer record to your account. This may include DANA, OVO, GoPay, QRIS, bank transfer or virtual account details shown in your account.

Yes, send the request through the account support path and state what should be corrected or removed. We explain the result after checking the record and any legal reason it must be retained.

Cookies can support sign-in continuity and saved account settings on your browser. For a cookie question, tell us whether you used a mobile browser or desktop browser so we can identify the relevant setting.

Yes. Contact us through the account support route and describe the access message you received. We can explain the policy wording and the next available account step without asking for public disclosure of private details.