Reference

bpjs777 Privacy Policy for Indonesia

The bpjs777 Privacy Policy explains what we collect when you open an account, verify your phone, browse Dragon Tiger or use DANA, OVO, GoPay and QRIS.

Clear data purposesWallet records explainedPhone access controlsPolicy request path

Browse Our Lobby Read FAQ

How Wallet And Account Data Are Used

bpjs777 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy applies to details you submit during account opening, including your contact number and verification result. We also record sign-in events, device signals, selected lobby pages and transaction references when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. These records

1
help us connect a wallet status to the correct account, investigate an incomplete payment and protect access from unusual activity. We do not describe a payment rail as a separate identity; the rail reference is handled as part of your account record. Where local law permits,
2
we may retain records for the period needed for security, dispute handling or a legal request. If access or eligibility is discussed, it depends on local law. Read the current Privacy Policy before opening an account, and contact us if a section is unclear or your
3
circumstances change.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

PRIVACY HELP ROUTE

Where To Ask About Your Privacy Policy

A privacy question should reach us through the support route shown inside your account, so we can match the request with the correct contact record.

Account help panel Open the help panel after signing in and choose the privacy subject. This keeps your request beside the account record and lets us confirm which Privacy Policy section applies.

Wallet record query For DANA, OVO, GoPay or QRIS questions, share the transaction reference rather than a wallet password. We use that reference to locate the relevant payment record without asking for secret credentials.

Access request Ask us to correct, export or remove eligible account data through the listed support route. We may verify your phone before changing records, protecting your account from an unapproved request.

DATA CONTROL DETAILS

What Our Privacy Policy Covers

We keep the Privacy Policy practical by connecting each data purpose to an account action you recognise.

Data we receive

We may receive your phone number, verification result, sign-in time, device details, selected pages and payment references. The Privacy Policy explains why each category is needed and when it enters our records.

Cookies and sessions

Cookies and similar session tools can remember an active sign-in, language choice or page state. Clearing browser data may sign you out and require phone verification again before account access.

Account protection

We use phone verification and sign-in signals to reduce unauthorised access. If a device change looks unusual, we may ask for an account step before showing wallet records or allowing a data request.

Retention choices

We retain account and payment references only as long as needed for the stated purpose, security checks, disputes or legal duties where local law permits. The applicable period can depend on the record type.

Correction requests

If your phone number or account detail is wrong, contact us through the support route in your account. We will verify the request, correct eligible records and explain any data that must remain.

Device access path

You can read this Privacy Policy from the account menu on mobile or desktop. The same policy path applies in Jakarta, Surabaya and other supported Indonesian locations where local law permits.

Privacy Policy Answers For Your Account

These Privacy Policy answers cover the searches we hear most often before an account is opened or a wallet record is checked. If your request is not listed, use the account support route and include enough detail for us to identify the relevant record without sending private login credentials.

It covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps us confirm that an account access or data request comes from you. We may ask for this step before changing contact details, showing records or processing a correction request.

Do not send a wallet password or one-time code to us. The Privacy Policy concerns payment references and account status, while secret wallet credentials remain outside the support request.

Yes. Use the support route shown after account sign-in and request a copy of eligible records. We may verify your phone and will explain the format, scope and any lawful restriction.

Send a correction request through the account help panel, identify the field that needs changing and complete any requested phone check. We will confirm which record was updated or explain why it remains.

Retention depends on the record and its purpose, including account security, payment disputes and legal duties. Where local law permits, we remove or de-identify records when the required period ends.

Contact us through the privacy route inside your account and describe the requested change. Include your account phone number, but never include a password or one-time code in the message.

bpjs777 Privacy Policy for Indonesia

Where To Ask About Your Privacy Policy

What Our Privacy Policy Covers

Data we receive

Cookies and sessions

Account protection

Retention choices

Correction requests

Device access path

Privacy Policy Answers For Your Account

01 What does the bpjs777 Privacy Policy cover?

02 Why does the Privacy Policy mention phone verification?

03 Does bpjs777 store my DANA or QRIS password?

04 Can I ask for my account data?

05 How can I correct details under the Privacy Policy?

06 How long does bpjs777 keep wallet records?

07 Where can I request a Privacy Policy change?

Related Pages