Reference

jaheharum99 Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open a jaheharum99 account, use DANA or QRIS, and move between the lobby and cashier area.

Account dataWallet recordsCookie choicesAccess requests
jaheharum99 jaheharum99 Privacy Policy for Your Account
CONTACT PATHS

Get Privacy Help Near Your Account

A clear support path helps you ask about the Privacy Policy without sending sensitive details through an unsafe route. Use the support link inside your logged-in account and include the phone number linked to your profile, the relevant date and the type of request. From Yogyakarta or Jakarta, the same account path applies, while payment receipts and status references help us locate the correct record.

Team online

Privacy request

Use the account support path to ask what personal details we hold, why a record is used, or whether a correction request can be opened for your profile.

Wallet record query

For DANA, OVO, GoPay or QRIS questions, provide the payment reference rather than a wallet password. We use that reference to check the linked account record.

Access assistance

If phone verification or a login check stalls, contact us from the account route and describe the device path. We use the request to confirm ownership before discussing details.

DATA PRACTICES

Inside jaheharum99 Privacy Handling

We keep this policy practical by linking each data use to an account action you can recognise, such as phone verification, a wallet status check or a security alert.

Data collection

We collect details needed for account creation, phone verification, login protection, payment matching and support handling. Optional details are identified where applicable, so you can understand why a field appears.

Cookie use

Cookies and similar browser storage can remember a session, protect login continuity and help us understand basic page errors. You can manage browser cookie settings, though some account functions may then stop working.

Account security

Phone verification, login events and device signals help us detect unusual access. We may ask for account details before discussing a wallet record, reducing the chance of disclosure to the wrong person.

Retention periods

We retain account, payment and support records only for the period needed for security, dispute handling and legal duties. When that need ends, records are deleted or changed so they no longer identify you.

Changing details

If your phone number or account detail is incorrect, send a correction request through logged-in support. We may verify ownership first, then record the change and keep an audit entry.

Who to contact

Our support route is the starting point for Privacy Policy questions, data access requests and deletion queries. Include your account phone number and request type, but never send a wallet password.

Privacy Policy Questions About jaheharum99

These Privacy Policy answers cover the account, device and payment questions you are most likely to ask before creating access. They also explain how to contact us, what verification does and how local payment references are treated. If your situation is not listed, use the support path connected to your account so we can identify the correct record.

It covers account creation, phone verification, login events, cookies, device signals, wallet references, support requests, retention and requests to access, correct or delete eligible personal details.

Yes. The Privacy Policy explains how we use DANA, OVO, GoPay and QRIS references to match payment status with your account. Wallet passwords are not required for that matching process.

Phone verification helps connect account access to the correct person and supports security checks when login activity looks unusual. We may request it before discussing account or wallet records.

Yes. Send an access request through logged-in account support with your linked phone number and request type. We may confirm ownership first, then explain the eligible records connected to your account.

Open a correction request through the account support path and identify the field that needs changing. We may verify ownership, update the record and retain a trace of the request.

We keep account, payment and support records while they are needed for security, dispute handling or legal duties. After that period, we delete or anonymise them where appropriate.

You can send a deletion query through logged-in support. We assess which records can be removed, because some account, payment or legal records may need to remain for a defined period.