Reference

Privacy Policy for Your jaheharum99 Account

The jaheharum99 Privacy Policy explains what we collect when you open an account, check wallet status, or enter the lobby from Indonesia.

Account dataWallet referencesCookie choicesSecurity requests
jaheharum99 Privacy Policy for Your jaheharum99 Account
CONTACT PATHS

Three Ways to Ask About Privacy

A clear contact path helps you resolve a data question without repeating your account story.

Account privacy request Use the account support path to ask what personal data we hold, why it…
Wallet record question For a DANA, OVO, GoPay, or QRIS reference, send the transaction date and the…
Access and device concern If a sign-in alert appears after using a mobile browser or desktop device, contact…
HANDLING DETAILS

What We Do With Your Account Data

We keep the Privacy Policy practical: each data type has a clear account, security, or support reason.

Collection at account opening

When you create an account, we collect the contact and verification details needed to establish access. A clear phone verification step helps prevent a stranger from using your account. We do not need a wallet password to connect your account with DANA or QRIS activity.

Payment references only

A cashier check may contain a payment rail, reference number, amount, and status so we can match the event to your account. For BCA, BRI, Mandiri, or BNI transfer questions, send the reference shown to you rather than private banking credentials.

Cookies and browser choice

Cookies can keep a signed-in session available and help us understand whether a policy page loads correctly. You can review or remove cookies in your browser settings. Removing some cookies may require another login, but it does not erase account records automatically.

Security around access

We use account checks, phone verification, session controls, and device signals to spot unusual access. If you move from mobile to desktop, a new sign-in may create a security check. Never send us a password, wallet PIN, or one-time security code.

Retention and deletion

We keep personal data for the period needed to operate access, investigate a payment status, address a dispute, or meet a legal duty where local law permits. When a valid deletion request applies, we remove or anonymise eligible records while retaining only what the law requires.

Changes to your details

Ask us to correct an incorrect name, phone detail, or account record through the support path. We may request verification before making a change, especially when it affects wallet status or access. Your request should identify the field to change and the reason it is inaccurate.

Privacy Policy Questions Before Account Access

These Privacy Policy answers address the searches we hear most often before account opening. We explain the account step, local wallet references, browser behaviour, and contact route in plain English so you can decide what to share. If your question involves eligibility or access, that outcome depends on local law and the details of your account request.

It covers personal data connected with account creation, phone verification, sign-in, support, cookies, and payment references. It explains how we use those records for access, security, and account assistance, including checks linked to DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

Phone verification confirms that you control the contact detail used for account access. We use it to reduce mistaken or unauthorised sign-ins and to help locate the correct record during a Privacy Policy request. We will not ask you to disclose your wallet PIN or one-time code.

Yes. The policy covers payment references and status details associated with DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity. We use those details to match an account event or answer a receipt question, while your wallet password and banking credentials remain outside our request.

Send a request through the support path connected with your account and identify the contact detail used for verification. Tell us whether you want access, correction, or another eligible change. We may confirm ownership first, then explain the records we can provide or amend.

We retain information for account operation, security checks, payment questions, dispute handling, or legal duties where local law permits. The period depends on the record and its purpose. When retention is no longer needed and deletion applies, we remove or anonymise the eligible data.

Yes. Use the cookie and site-data controls in your mobile browser to inspect, block, or remove cookies. A change may sign you out or require the lobby to load again. Cookie controls do not automatically delete your account, payment references, or a previous support request.

Change your account password first, then contact support with the device type and approximate sign-in time. Do not send a password, wallet PIN, or security code. We can review the access record and explain the next account-security step under the Privacy Policy.