Reference

jamda4d Privacy Policy For Your Account

jamda4d Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity.

Clear data purposesPhone verification recordsCookie choicesAccount access requests
jamda4d jamda4d Privacy Policy For Your Account
HELP WITH YOUR DATA

Privacy Policy Support Paths

A clear contact route matters when a name, phone number or payment reference looks incorrect. We handle Privacy Policy questions through our account support path, including requests connected with login, phone verification…

Account privacy request Use the account support path to ask for a copy of personal data linked with your jamda4d account. Include your registered phone number and the subject Privacy Policy so we can route the request to the correct team without exposing details to another account.
Wallet record question If a DANA, OVO, GoPay or QRIS reference appears unfamiliar, contact support through the cashier path and include the date and reference shown on your account. We use those details to check the record while limiting disclosure of unrelated transaction information.
Access or correction For a correction, deletion request or access concern, tell us exactly which field or record you mean. We may verify your phone before making a change, then explain whether local rules or account-security needs affect the requested action.
DATA HANDLING DETAILS

What We Do With Account Information

Privacy Policy decisions should be understandable before you commit details to an account. We separate information needed for account access from technical signals used to keep sessions secure.

Account details

We use your account name, phone number and verification status to create access, identify your records and respond to account requests. We do not treat a phone number as permission to discuss another person’s account, so a matching account step may be required.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create reference data such as amount, time, status and destination. We use those records to reconcile your account and investigate a disputed status, not to request your wallet password.

Cookies

Cookies can remember a session, support security checks and preserve selected settings between pages. You can manage cookies through your browser controls. Blocking some cookies may require you to repeat login or phone verification before account access is restored.

Device security

We may record device type, browser version, session time and connection signals when you open the lobby or account page. These records help us spot unusual access, including a sudden change from a mobile path to a desktop session.

Retention

We keep account and transaction records only for the period needed for account administration, security checks, dispute handling and applicable legal duties. When a record is no longer needed, we remove it, anonymise it or restrict access according to our internal process.

Your request

You can ask us to access, correct or delete eligible personal data, or ask why a record is retained. Send the request through account support with your registered phone number; we may verify identity and explain any limit that depends on local law.

Privacy Policy Answers For jamda4d

These Privacy Policy answers address the questions we expect before account opening, especially around phone verification, cookies, payment references and Indonesian access. If your situation is not covered, contact us through the account support path with the registered phone number and the specific record you want us to check. We will explain the next account step and any local-law restriction that applies.

It covers account details, phone verification, device and session signals, cookies, support requests, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security handling and how you can request access or correction.

We use your phone number to create an account record, complete phone verification and help protect login access. It also helps us match a Privacy Policy request to the correct account. We will not treat a phone number alone as permission to disclose private account details.

Yes. The policy covers references connected with DANA and QRIS, along with OVO, GoPay, bank transfer and virtual account records. We may retain status, timing and reference details to reconcile your account or investigate a payment question without requesting your wallet password.

On a mobile browser, cookies may keep your session, support security checks and remember selected settings. You can control them through browser settings. If you block required cookies, the account page may ask for login or phone verification again before access continues.

You can ask for a copy of eligible personal data linked with your account by contacting account support. Include your registered phone number and describe the records you need. We may verify identity first, and the response path depends on local law and security duties.

You can request a correction or deletion of eligible records through account support. Tell us which field or record is wrong and why. Some security, dispute or legal records may need to remain for a period, and we will explain that restriction when it applies.

Use the account support route, preferably while signed in, and include the subject Privacy Policy. For a wallet concern, add the date and reference shown beside the cashier status. We may request phone verification before discussing records, and availability is where local law permits.