Reference

jokerindohub Privacy Policy Explained Clearly

jokerindohub Privacy Policy explains what we collect when you open an account, verify your phone and use payment routes such as DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesSecurity requests
jokerindohub jokerindohub Privacy Policy Explained Clearly
CONTACT ROUTES

Get Privacy Help Near Your Account

A clear contact route helps when a data request and a wallet receipt meet in the same account. We ask you to use the support path linked to your account so we can confirm ownership before discussing private details. Include the relevant date, device and payment reference, but never send a password or wallet PIN.

Team online

Account data request

Ask through the account support path for a copy of personal data linked to your profile. We may request phone verification before releasing records or discussing a change.

Wallet record question

For a DANA, OVO, GoPay or QRIS status question, include the receipt reference and time shown on your account. We use those details to locate the correct payment record.

Privacy correction

Tell us which account field needs correction and why. We compare the request with your verified account details, then explain any step needed before changing the record.

HANDLING DETAILS

Inside jokerindohub Data Handling

We separate everyday account operation from a privacy request, so each question reaches the right check.

Account creation

When you open an account, we collect the details needed for account access and phone verification. The verification step helps us distinguish your request from an unauthorised change attempt.

Payment references

DANA, OVO, GoPay and QRIS may return a transaction reference or status. We use that reference to reconcile your account record, not to request your wallet password or PIN.

Cookies on mobile

Our mobile browser path may use session cookies for login continuity and selected settings. You can inspect or delete them in your browser controls, though clearing them may require another login.

Account security

Phone verification, login records and session checks help us protect account changes. If a device behaves unexpectedly, contact support from the account path and avoid sharing passwords or wallet credentials.

Retention period

We keep account and payment references for the time needed to operate the account, resolve disputes and meet applicable obligations. When that need ends, records can be deleted or anonymised.

Requesting changes

You can ask for access, correction or clarification through our support route. State the account field concerned, and we will explain identity checks, available action and any legal reason for keeping a record.

Privacy Policy Questions From Indonesia

These answers address the privacy searches we hear most often before an account is opened or a wallet is connected. If your case involves a specific receipt, device or account field, use the support path so we can check the relevant record.

It covers account details, phone verification, login events, cookies, payment references and privacy requests. It also explains retention, security checks and how you can ask for access or correction.

No. We use payment references and status details from DANA, OVO, GoPay or QRIS to match activity to your account. We do not ask you to provide a wallet PIN or password.

Phone verification helps us confirm that the person requesting account data or a correction controls the relevant account. It reduces the chance of private details being sent to the wrong person.

Use the support path connected to your account and ask for a data copy. Include the account contact detail you can verify; we may complete an identity check before responding.

Yes, you can request a correction through account support. Tell us which field is wrong and provide the replacement detail where needed. We will explain the verification step before making a change.

Session cookies can keep your mobile browser connected to the current account step and remember selected settings. You can clear them in browser controls, but doing so may require another login.

We retain payment references for account operation, receipt matching, dispute handling and applicable obligations. When those needs end, we remove or anonymise the records where appropriate.