Reference

Privacy Policy for Your jiso4d Account

jiso4d Privacy Policy explains what we collect when you open an account, sign in, use the lobby or check wallet status.

Account dataWallet recordsCookie choicesContact route
jiso4d Privacy Policy for Your jiso4d Account
CONTACT OPTIONS

Get Privacy Help Through Your Account

A clear contact path matters when a privacy question is tied to a login or wallet status. We ask you to contact us from the account route where possible, because that lets us match your request with the right account record without exposing details to an unknown sender. Include the phone number on the account, the subject of your request and any payment reference that helps us locate the event. Do not send a wallet PIN, password or one-time verification code.

Team online

Account message

Use the account support path for a request about your phone number, verification record, sign-in history or stored profile details. We may ask you to confirm an account step before discussing personal data, so the request stays connected to the correct jiso4d account.

Wallet status

When a DANA, OVO, GoPay or QRIS reference appears in a privacy question, include the reference and approximate transaction date. We use those details to locate the relevant record while keeping your wallet password, PIN and one-time code out of the support conversation.

Security concern

If you see an unfamiliar sign-in or device event, contact us through the account support route promptly and change your account password. We use the reported time, device path and verification status to investigate access without asking you to reveal private wallet credentials.

DATA PRACTICES

How We Handle Privacy Requests

We handle privacy as an account process rather than a vague promise. Data is collected for a stated operational reason, reviewed when a request arrives and restricted to…

Account data

We use your phone number and verification result to connect sign-in activity with your account.

Cookies

Cookies and similar browser signals help keep your session connected while you move from login to the lobby.

Account security

We use sign-in events, device details and phone verification signals to identify unusual account access.

Payment references

A DANA, OVO, GoPay or QRIS reference can help us reconcile an account event without storing your wallet PIN.

Retention period

We keep information only for as long as it supports account operation, security checks, payment reconciliation or a required legal…

Policy requests

You may ask what eligible personal data we hold, request a correction or ask about deletion where local law permits.

jiso4d Privacy Policy Questions

These Privacy Policy answers cover the searches we hear most often from Indonesian account holders. They explain the practical difference between account data, device signals, wallet references and support records. If your situation involves another person’s information, an unfamiliar sign-in or a request linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, use the account contact path and describe the record clearly.

The Privacy Policy treats your phone number and verification result as account data used to connect you with the correct sign-in. We may request a confirmation step before revealing or changing details. Keep verification codes private, because support will not need your one-time code to process a privacy request.

No wallet PIN should be sent to us. The Privacy Policy allows operational payment references, such as a DANA or QRIS transaction reference, to help reconcile an account event. Your wallet provider handles its own credentials and separate privacy practices, so keep those credentials inside its service.

Send a clear correction request through the account support path and identify the phone number attached to your account. State which detail is inaccurate and what it should say. We may verify account ownership before making a change, then retain a request record for audit and follow-up.

We may use device type, browser details and sign-in events to maintain session security and identify unusual access. These signals are not a substitute for your account details. Browser cookie controls can affect session continuity, so contact us if a privacy concern follows a device change.

Retention depends on the kind of record and why we need it. Account, security, payment-reference and support records may remain while they support operation, reconciliation or a legal process. Ask us about a specific record and we will explain the retention reason where local law permits.

You can send a deletion request through the account contact route. We first confirm that you control the account, then assess which information is eligible for removal. Some records may need to remain for security, payment reconciliation or a legal process where local law permits.

Use the account support path and include your account phone number, the Privacy Policy topic and a useful date or transaction reference. For an unfamiliar sign-in, mention the device and time. Never include a password, wallet PIN or one-time verification code in your message.