Reference

Privacy Policy for Your jamur4d Account

Our Privacy Policy explains how jamur4d handles the account details, device signals and wallet records connected with your access.

Account clarityWallet recordsMobile access
jamur4d Privacy Policy for Your jamur4d Account
REQUEST HELP

Get Privacy Help Near Your Account

A clear contact path matters when you want to ask about personal data, a wallet reference or an account record.

Account route Open the support path beside your account area when you need to ask about…
Cashier context For a DANA, OVO, GoPay, QRIS or bank transfer record, refer to the payment…
Privacy request Tell us whether you want access, correction, clarification or removal of data that we…
DATA IN PRACTICE

How jamur4d Handles Privacy Requests

We apply the policy to practical account events rather than treating every record the same way.

Collected account data

We may receive the phone number and verification result you provide for account access, along with login timestamps, device type…

Payment references

A DANA, OVO, GoPay or QRIS payment can create a reference, amount status and processing timestamp connected to your account.

Cookies and devices

Cookies and similar device signals can keep your session connected, remember security choices and help us detect an unusual login.

Account security

We use phone verification, login records and device checks to help distinguish your account activity from an unfamiliar attempt.

Retention choices

We keep records for as long as they support account access, payment matching, security checks, dispute handling or a request…

Changes and contact

You can ask us to correct an inaccurate phone, contact detail or account record through the support route linked to…

Privacy Policy Answers for jamur4d

These Privacy Policy answers focus on the searches we expect before an Indonesian account is opened. They cover the data attached to login, mobile use, payment references and support requests without turning the policy into a general lobby description. If your question is not listed, use the account support route and point us to the relevant section or record.

It covers account details, phone verification, login and device signals, cookies, support messages, payment references and retention. It also explains why DANA, OVO, GoPay, QRIS, bank transfer or virtual account records may be linked to your account and how you can ask about those records.

Phone verification helps connect the person requesting account access with the correct account and supports security checks around unfamiliar logins. We record the verification result and related account event for those purposes, then handle it under the Privacy Policy and applicable local requirements.

Yes. The policy covers references created when you use DANA or QRIS, including a transaction status and processing time needed to match the payment with your account. It does not mean we receive unrestricted access to your wallet; the payment rail controls its own account data.

Use the support route shown in your account and name the field or record you believe is inaccurate. Add a safe account reference, not a complete wallet history. We may request phone verification before changing data, and the request remains subject to what we are permitted to amend.

Retention depends on the purpose of each record, such as account access, payment matching, security, dispute handling or an open support request. We keep data only for the period needed under the policy and applicable requirements, then handle deletion or further storage according to those rules.

You can ask through the account support path for clarification or access to data connected with your account. Describe the category, such as a login event, device signal, QRIS reference or support message. We may verify account ownership before responding to protect your private records.

Yes. Mobile access can create session cookies, device type, browser signals and login timestamps, and the Privacy Policy explains their purposes. These signals help keep the account path connected and identify unusual access; availability and eligibility still depend on local law.