Reference

Privacy Policy For Your beli jitu Account

beli jitu Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, and use wallet options such as DANA, OVO…

Account clarityWallet statusCookie choicesPolicy requests
beli jitu Privacy Policy For Your beli jitu Account
CONTACT ROUTES

Three Ways To Ask About Privacy

A clear contact path helps you resolve a data question without guessing which account screen to use. We keep privacy requests separate from ordinary lobby questions, so you can explain whether you need a copy, correction, deletion request or clarification about a device record. Include the phone number linked to your account and the relevant payment reference when it helps us locate the right record.

Team online

Privacy request form

Use the privacy contact form linked from our policy area when you want to ask what personal data we hold, request a correction or ask how a record connected with your account is used. We may ask for account details to confirm that the request comes from you.

Account support path

If login or phone verification blocks a privacy request, start through the account help link beside the sign-in path. Tell us whether the issue concerns your device, wallet status or account details, and we will route the question to the appropriate support queue.

Payment record query

For a question about a DANA, OVO, GoPay, QRIS, bank transfer or virtual account record, include the payment reference and approximate time. This lets us compare the wallet or bank status with the account record without asking you to resend unrelated personal details.

DATA PRACTICES

Six Privacy Controls We Keep Visible

Your privacy choices matter most when the handling is easy to understand at the point of account use.

Account data

We use details such as your account identifier and verified phone number to connect you with the correct sign-in record. Phone verification before account access helps us distinguish an account request from an unknown device attempt and gives support a clear reference when you ask for a data change.

Device signals

A mobile browser or desktop session can provide technical signals such as browser type, operating system and session timing. We use these details to maintain a working sign-in path, investigate unusual access and understand why a page may behave differently on your device.

Cookie settings

Cookies and similar storage can keep a session connected to the right account and remember settings between pages. You can manage browser permissions through your device or browser controls, although restricting essential storage may interrupt sign-in, verification or payment-status displays.

Wallet matching

When you use DANA, OVO, GoPay or QRIS, we may retain the account-facing payment reference and status needed to reconcile the action. We do not need unrelated wallet content for that check, and support can use the reference when you question a pending record.

Security handling

We limit account details to operational roles that need them for access checks, support handling, security review or payment reconciliation. Never send a password through a support form. If a sign-in alert or phone change looks unfamiliar, contact us through the account help path.

Retention requests

We keep records only as long as needed for the stated account, security, support or payment purpose, subject to legal and operational requirements. You can ask what remains, why it is retained and whether a correction or removal request can apply to a particular record.

Privacy Policy Questions Before Account Access

These answers address the searches we hear before someone opens an account or sends a privacy request. Each answer stays focused on how beli jitu handles account, device, cookie and payment-related data, so you can choose the right contact route before sharing details.

The beli jitu Privacy Policy covers account details, phone verification, device and browser signals, cookies, support records and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account actions. It also explains purposes, retention and ways to request access or correction.

We use your phone number to create and identify the account record and to complete phone verification before account access. It can also help support locate the right record when you ask about a device change, wallet status or Privacy Policy request.

Yes. The Privacy Policy includes technical signals from the mobile browser or desktop session, such as browser type, operating system and session timing. We use them for session continuity, security checks and troubleshooting when the login or payment-status path behaves differently.

We use the account-facing reference and status needed to reconcile a DANA, OVO, GoPay or QRIS action. The purpose is to match the payment event with your account and answer a support query; unrelated wallet content is not needed for that process.

You can send a request through the privacy contact form and identify the account record involved. Ask for a copy, correction or clarification, and include your verified phone number when appropriate. We may confirm your identity before responding, with handling subject to local law.

We retain information for the account, security, support or payment purpose that requires it, then assess whether it is still needed under applicable requirements. The Privacy Policy does not make every record permanent. Ask through the privacy route which category and retention reason applies.

Use the account help path beside sign-in and tell us that the session or device is unfamiliar. Do not send your password in a message. We can check the relevant access record, help protect the account and explain which security data was used.