Reference

Privacy Policy For jp sonic Accounts

jp sonic Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Account clarityWallet contextCookie choicesSupport requests
jp sonic Privacy Policy For jp sonic Accounts
HELP WITH REQUESTS

Get Policy Help Beside Your Account

A clear contact path matters when your Privacy Policy question concerns a login, wallet status or account record.

Account access If you cannot sign in, tell us the account contact and device path you used, such as a mobile browser. We can check the access record and explain which verification step is needed without asking for your account password.
Wallet status For DANA, OVO or GoPay status questions, send the transaction reference and selected wallet name through account support. We compare the payment signal with your account record and tell you whether a further check is needed.
Data request To request access, correction or deletion of eligible information, identify your account and describe the request in plain English. We may ask for an account verification step before changing or disclosing personal data.
HANDLING DETAILS

What We Do With Your Personal Data

We keep this policy practical: your account details help us recognise a returning sign-in, connect a payment reference and protect records from unauthorised changes.

Account records

We may store the contact details and verification information you provide when opening an account. These records help us distinguish your account from another person using the same phone or shared device during an access check.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can be retained with transaction status. We use it to reconcile your account activity, investigate a receipt question and support a payment dispute.

Cookies

Cookies and similar session tools can remember sign-in state, language choices and security context. If you clear them, you may need to complete the account access step again on your phone or desktop browser.

Account security

We use sign-in events, device signals and verification steps to identify unusual account access. Never send us your password or wallet PIN; support uses account details and transaction references instead.

Retention

We keep personal data for the period needed for account operation, payment reconciliation, dispute handling, security and legal duties. When a record is no longer needed for those purposes, we remove or de-identify it.

Your changes

You can contact us to ask for a copy, correction or deletion of eligible personal data. We may verify ownership first, and access to the account remains subject to local law and where local law permits.

Privacy Policy Questions About jp sonic

These Privacy Policy answers focus on the account steps and payment records you are most likely to ask about before opening an account. We explain what can appear in our records, how to contact us and why an identity check may be required. If your situation is not covered here, use the account support path with the smallest useful set of details. Do not include passwords, wallet PINs or full payment credentials in a message.

It covers personal data connected with your account, including contact details, verification records, sign-in events, device signals, cookies and payment references. It also explains how we use, retain, protect and amend those records when access is available where local law permits.

We may retain a transaction reference, selected rail and status for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We use those details to match a payment with your account and handle receipt or dispute questions.

Yes. Send a data access request through the account support route, identify the contact attached to your account and describe the records you need. We may complete an ownership check before disclosing personal data, subject to local law.

Contact support with the account detail that is incorrect and the correction you want made. We may ask for a verification step before changing contact or identity information, which helps prevent another person from altering your account.

We may use cookies or similar tools for session continuity, language choices and security context on a mobile browser or desktop. Clearing cookies can end your session and require you to complete the account access step again.

We retain records while they are needed for account operation, payment reconciliation, security, disputes or legal duties. When those purposes end, we remove or de-identify the data according to our retention process and applicable local requirements.

Use the account support route shown on our site and include your account contact plus a short description of the concern. For DANA or QRIS matters, add the reference and date. Never send a password, wallet PIN or full credential.