Reference

jari4d Privacy Policy For Your Account

Your account records, wallet details and access choices are explained clearly in the jari4d Privacy Policy.

Clear data purposesWallet record controlsAccount access choicesPrivacy request path
jari4d jari4d Privacy Policy For Your Account
PRIVACY HELP

Contact Us About Account Data

A clear support path helps when a privacy request and an account check meet at the same time.

Account access Ask us to confirm which account details are held after your phone verification step. We may ask for matching account facts before discussing records, helping prevent another person from receiving your data.
Wallet records For DANA, OVO, GoPay or QRIS questions, share the transaction reference rather than wallet credentials. We can check the payment status attached to your account and explain what record is retained.
Privacy changes Request a correction, access copy or deletion through account support. Include the exact change you want, and we will explain any verification or retention step that affects the request.
DATA PRACTICES

Browse jari4d Data Safeguards

We handle privacy as an account process rather than a short notice hidden after sign-in. Our records connect a verified phone number with access events, device behaviour and payment references so we…

Data we receive

We may receive your phone number, verification result, sign-in time, device type, browser signals, support messages and payment references. We use only the connection needed to maintain account access and check a transaction.

Cookie choices

Cookies and similar device signals can keep your session active, remember selected settings and help us detect unusual access. You can manage browser permissions, although some account steps may then need repeating.

Account security

Phone verification comes before account access, while sign-in and device signals help us identify unusual activity. Never send a password, one-time code or wallet PIN through a support request.

Retention periods

We keep account and payment records only as long as needed for access support, transaction disputes, security checks or legal duties. When a record is no longer needed, our process removes or de-identifies it.

Sharing boundaries

We may share limited records with payment or technical providers when required to process a status check, protect an account or resolve a transaction. We do not ask those providers for unrelated profile data.

Requesting changes

Contact account support to request a copy, correction or deletion. Tell us the phone number on the account and the requested action; we verify ownership before releasing or changing personal records.

Find Privacy Policy Answers

These Privacy Policy answers address the account and wallet questions we expect before registration. They explain the practical route for checking data, changing details and contacting us, while the full policy above remains the controlling text for jari4d accounts where local law permits.

It covers account details, phone verification, device signals, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number to verify account ownership, support sign-in checks and connect a privacy request with the correct record. We will not ask for your wallet PIN through support.

Use the account support path and state that you want an access copy. Include the phone number linked to your account; we verify ownership before discussing or sending personal records.

Yes, you can request a correction through account support. Identify the inaccurate field and explain the requested change. We may verify your account before updating the record.

We keep payment references and status details needed to match a transaction with your account. We do not need your DANA or QRIS password, wallet PIN or unrelated wallet content.

Retention depends on the purpose: access support, payment disputes, security checks and legal duties can require different periods. When a record is no longer needed, we remove or de-identify it.

Use the support route inside your account and include your linked phone number plus the subject of your request. We can then direct the question to account data support.