Reference

Privacy Policy for jpwede Accounts

jpwede explains how we handle your account details, device access and wallet records when you use our Indonesia service.

Account dataWallet recordsDevice privacyYour requests
jpwede Privacy Policy for jpwede Accounts
HELP PATHS

Where Privacy Questions Go

A clear contact route helps you resolve a privacy question without sending sensitive details to the wrong place. Start with the support contact displayed after you sign in, then include the account phone number and the subject of your request without sharing a password or wallet PIN. If you are in Makassar or elsewhere in Indonesia, the same account path applies; where local law permits, we handle requests linked to your account and payment records through that route.

Team online

Account contact

Use the support contact inside your signed-in account for a Privacy Policy question. Tell us whether your request concerns phone verification, a device record or a DANA, OVO, GoPay or QRIS transaction, so we can locate the relevant account entry.

Receipt support

For a payment receipt or wallet status question, keep the transaction reference and date ready. We may ask you to confirm account ownership before discussing the record, while keeping wallet passwords, card secrets and one-time codes out of the conversation.

Access concern

If an unfamiliar device appears in your account activity, contact us through the same support path and change your account password from a known device. We use the report to check sessions, verification events and access changes connected with your account.

DATA PRACTICE

Account Security Across Your Devices

We keep this Privacy Policy practical by linking each data category to a clear account action.

Data we receive

We may receive your name, phone number, account credentials, verification status and messages sent through support. When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we receive transaction references and status details rather than your wallet password.

Cookies and sessions

Cookies and similar session tools help keep your signed-in account connected to the right browser and reduce repeated security checks. You can manage browser permissions, but limiting these tools may interrupt login, phone verification or movement between the lobby and account pages.

Security controls

Phone verification is part of the account access step, and session records help us investigate unusual activity. We ask you to protect your password, avoid sharing one-time codes and sign out after using a shared phone, tablet or desktop browser.

Retention purpose

We retain account, support and transaction records for as long as needed to provide access, match payment status, resolve disputes, protect the service and meet applicable legal duties. Retention periods can differ by record type and are not the same for every request.

Request a correction

If your phone number, account detail or payment reference is wrong, send a correction request through the signed-in support contact. Include the affected field and a safe way to confirm ownership; never include a password, wallet PIN or one-time code.

Request data access

You can ask us to describe the personal data connected with your account and how we use it. We may verify your identity before responding, and where local law permits, you can also ask about deletion or a restriction on a particular use.

Privacy Policy Questions for Indonesia

These Privacy Policy answers address the account, device and wallet questions we expect you to ask before creating access. They explain what to prepare, where to send a request and why a verification step may be required. If your situation is not covered, contact us through the signed-in support path and refer to the relevant account or transaction record.

The jpwede Privacy Policy covers account details, phone verification, support messages, cookies, device sessions and payment references. It applies when you use the Indonesia service through a mobile browser or desktop browser, including activity connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

We use your phone number to create and protect the account, complete the phone verification step and help confirm ownership during a privacy or access request. Keep the number current, and do not send one-time codes or wallet credentials through support messages.

No. Our Privacy Policy describes transaction references, payment status and receipt details needed to match account activity. We do not ask for your DANA, OVO, GoPay or QRIS password, wallet PIN or one-time code. Do not include those secrets in a support request.

Sign in from a known device and use the support contact shown in your account. State that you are requesting account data under the Privacy Policy, identify the phone number on the account and describe the record you need. We may verify ownership before responding.

Yes, you can ask us to correct an inaccurate account detail or explain a deletion request through the signed-in support path. Where local law permits, we assess the request against account security, payment reconciliation and legal record duties before confirming what action we can take.

We may record browser type, device type, session timing and security events so we can maintain account access and investigate unfamiliar sign-ins. Mobile and desktop sessions can appear separately. Sign out on shared devices and contact us if a session does not look familiar.

Yes. Account access and eligibility depend on local law. Our Privacy Policy still explains how we handle data for the Indonesia service, but it does not change local requirements. If you are unsure whether access is available in your location, contact support before opening an account.