Reference

jamur4d Privacy Policy For Your Account Data

Clear control over account details, wallet records and device access is the purpose of our Privacy Policy.

Account dataCookie choicesAccess requestsRetention steps
jamur4d jamur4d Privacy Policy For Your Account Data
REQUEST SUPPORT

Get Help With A Privacy Request

A clear request path helps you ask about data without guessing which account screen to use.

Account access Ask us which account details we hold and how they were collected.
Wallet record For a DANA, OVO, GoPay or QRIS record question, send the transaction reference through…
Data change Tell us which detail needs correction or removal, such as an outdated phone number.
HANDLING DETAILS

How We Handle Your Account Data

We keep the Privacy Policy practical by connecting each data purpose to an account action you recognise.

Account details

We use your submitted account details to create the account record, complete phone verification and respond to requests tied to that account. We do not need unrelated profile details for those steps.

Device signals

Login time, browser type and device signals can help us spot unusual access. On mobile, these checks may appear after you return from the lobby or switch between account screens.

Cookie controls

Cookies can keep a session connected and remember selected settings. Your browser controls whether they remain, while disabling them may require another login during the same account visit.

Account security

Phone verification supports account protection before access is completed. Never send a password or one-time code in a support message, even when asking about a wallet record.

Retention period

We retain account, login and transaction references only for the operational, security or dispute purpose described in the policy. When a record is no longer needed, our handling moves toward removal.

Change requests

You can ask for access, correction or deletion through support beside the cashier path. We confirm account ownership first and explain if a security or transaction record must stay.

Privacy Policy Answers For jamur4d Accounts

These Privacy Policy answers address the account questions you may have before opening an account or while checking a wallet record. They cover collection, cookies, phone verification, retention and the request path used by Indonesian account holders. If your situation is not listed, contact support from the route beside the cashier and include only the details needed to locate your account.

It covers account details, phone verification, login and device signals, cookies, wallet references and support requests. It also explains why we use each category, how long records remain and how to request a change.

We use the phone number connected to your account for verification before access and for matching an account request. It helps us distinguish your request from an unrelated DANA, OVO or QRIS query.

Yes. The policy covers references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These references help us confirm a status question without needing unrelated personal details.

Use the support route beside the cashier area and ask for an account data access request. Include your account identifier, then complete ownership checks before we discuss the records connected with you.

Yes. State which detail is incorrect, such as an outdated phone number, through the same support route. We verify ownership, update eligible account details and explain why some transaction references may remain.

Cookies may keep your session and selected settings available while you move between login and the lobby. Browser controls can remove or block them, although you may need to authenticate again.

Our handling applies where local law permits and account access depends on local law. If a local rule affects your request, we explain the relevant limitation through the account support path.