Reference

Privacy Policy For Your baja303 Account

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

Clear data purposesWallet activity explainedPhone access controlsPolicy contact path
baja303 Privacy Policy For Your baja303 Account
PRIVACY SUPPORT

Three Ways To Ask About Your Data

A clear contact route matters when your phone verification, wallet reference or account record needs attention.

Account support path Open the support area from your signed-in account and select a Privacy Policy request. Add your registered phone number and a short description so we can match the request to the correct account record.
Wallet record check For a DANA, OVO, GoPay or QRIS question, provide the payment reference and date rather than your wallet password or full security code. We can use the reference to check which account event needs attention.
Access correction request If your name, phone detail or account record needs correction, tell us which field is inaccurate and how we should reach you. We may ask for an account check before changing personal data.
DATA CONTROL

Six Practical Privacy Safeguards

We keep this policy useful by describing the controls you encounter during normal account activity.

Account identity

Your phone number and verification result help us connect a sign-in to the right account. We use this account step to reduce mistaken access and to make a privacy request about the correct personal record.

Device signals

The phone or computer used to sign in may create device, browser and session details. These signals help us investigate unusual access without requiring you to share a password in a support conversation.

Cookie choices

Cookies can keep a sign-in session and remember basic page settings. Your browser provides controls for removing or restricting them, although changing those settings may affect account access or policy pages.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can be stored with its event time and status. We use that record to reconcile a receipt or answer a wallet-data question.

Retention decisions

We retain personal records for account operation, security checks, dispute handling or a legal requirement, then remove or restrict them when the applicable purpose ends. The period can differ by record type and request.

Request handling

To request access, correction or deletion, contact us through the signed-in support route with enough account detail to locate your record. We may verify ownership before discussing or changing personal data.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the questions we expect before you open an account or send a wallet-related request. Each answer focuses on personal data, access records, cookies, payment references and the contact steps we can use to identify your account.

The baja303 Privacy Policy covers account details, phone verification, device and sign-in records, cookies, wallet references and support requests. It also explains why we use those records, how retention works, and how you can request access, correction or deletion where local law permits.

We use your phone number to create and identify your account, complete the access check and route support to the correct record. The number can also help us investigate an unexpected sign-in. Do not place your password or security code in a support message.

Yes. The Privacy Policy covers DANA, OVO, GoPay and QRIS references connected with your account, including status and event time. Bank transfer and virtual account references may also be retained so we can match a receipt or answer a wallet-data request.

Use the signed-in support path and ask for an account-data access request. Include your registered phone number and a clear description of what you want to see. We may verify account ownership before sharing records, and the outcome depends on local law.

Yes. Send a correction request through the account support route and identify the inaccurate field, such as a phone detail or account name. We may ask for an ownership check, then update the record or explain why a restriction applies.

Cookies can maintain a sign-in session and remember basic page settings when you access the site from a phone or computer. Your browser lets you remove or restrict cookies. Some account functions may not work as expected after those settings change.

Start with the signed-in support route and label your message as a Privacy Policy concern. State whether it involves account access, device activity, cookies or a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference.