Reference

bayarjitu Privacy Policy: Your Data Path

Our Privacy Policy explains what bayarjitu collects when you create an account, verify your phone and use DANA, OVO, GoPay or QRIS.

Account clarityWallet recordsCookie choicesContact requests
bayarjitu bayarjitu Privacy Policy: Your Data Path
POLICY HELP DESK

Contact bayarjitu About Privacy Policy

A clear contact route matters when you want to ask what we hold or why a record appears.

Account privacy request Ask us to explain account data connected with your registered phone number. We use the account step first, then confirm the request before discussing records linked to DANA, OVO, GoPay or QRIS.
Wallet record check If a payment reference looks unfamiliar, share the date, rail and reference shown in your account rather than a PIN. Our support route can assess the record without asking you to reveal secret wallet credentials.
Correction request Tell us which profile detail needs correction and why. We may request phone verification or another account check, helping us change the correct record while limiting disclosure during the process.
DATA CONTROL PRACTICES

Account Security From Login To Retention

We handle this policy area through defined account steps rather than broad promises. Phone verification helps us distinguish the account holder before a data request, while session controls help protect the mobile…

What we collect

We may hold your registered phone number, account settings, login events, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Why records are used

We use account and transaction records to provide account access, reconcile a wallet status, investigate an unusual request and answer your privacy questions without mixing separate account histories.

Cookies on mobile

Cookies or similar session tools can remember sign-in state and page preferences on your phone. You can manage browser settings, although changing them may require another login or limit session functions.

Protecting your account

We do not ask for your full password, wallet PIN or one-time code in a privacy request. Keep those secrets private, and contact us through the account support path if a message seems unusual.

How long we retain

We keep records for as long as needed for the stated purpose, account support, transaction reconciliation or an applicable legal requirement. When a record is no longer needed, handling follows our retention process.

Your available requests

You can ask what personal data is linked to your account, request a correction, raise a use objection or ask about deletion where applicable. We verify the requester before taking action.

Privacy Policy Questions For Your Account

These Privacy Policy answers address the searches we hear most often from Indonesian account holders. They cover wallet records, cookies, phone verification, correction requests and the conditions that may affect access. If your question is not listed, use the account support path and describe the specific record you want us to check.

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

Your registered phone number supports the account access step and helps us verify who is asking about personal data. We may request an additional account check before sharing or changing records.

Yes. The Privacy Policy explains how we use DANA and QRIS references to match a transaction, check its status and handle support questions. The provider may also have separate privacy terms.

You can send a correction request through the account support route, naming the detail that is wrong. We verify the request, assess the record and update it where applicable under local requirements.

Cookies or similar tools may remember your session and page settings on a mobile browser. You can adjust browser controls, but doing so may sign you out or affect session-related functions.

You may ask about deletion through support. We assess the request against account support needs, transaction reconciliation and applicable retention duties, so some records may need to remain for a period.

Use the support path linked from your account area and identify the request clearly. Include your registered phone number and relevant wallet reference, but never send a password, PIN or one-time code.