Reference

blijitu Privacy Policy For Your Account

blijitu Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, contact support, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesSupport requests
blijitu blijitu Privacy Policy For Your Account
CONTACT ROUTES

Get Privacy Policy Help Quickly

A direct support route helps you resolve a data question without repeating your account story across several channels.

Account support chat Use the support chat from your signed-in account when you need a copy of…
Wallet status request If your question concerns DANA, OVO, GoPay or QRIS, send the payment reference through…
Data change request Ask us to correct an account detail or clarify a retention period through the…
DATA PRACTICES

What We Do With Your Data

We keep this Privacy Policy practical by linking each data use to an account, device, payment or support action.

Account details

We use contact and account details to create your profile, send account messages, complete clear phone verification before access, and answer support requests. If a detail changes, contact us through the data change route so we can check the request against the account record before making an update.

Device signals

When you sign in through a phone or desktop browser, we may record device, browser and session signals linked to that visit. These checks help us spot unusual account access and keep a support request attached to the right session. They are not a request for your device files.

Cookies

Cookies can keep a sign-in session active, remember selected settings and help us understand whether a page request completed. You can remove or restrict cookies in your browser. Some account actions may need a working session cookie, so changing browser settings can affect how you reach your account.

Payment records

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account requests, we may keep a reference, amount, status and related account details. We use this information to match a cashier event and answer a receipt question. We do not need your wallet PIN to check that record.

Account security

We use phone verification, sign-in checks and session signals to reduce the chance of another person entering your account. Keep your password and wallet credentials private, and contact support if a sign-in looks unfamiliar. We may pause a sensitive request until account ownership is confirmed.

Retention requests

We retain information only while it supports account operation, security, dispute handling or a legal need that applies where you are located. You can ask what we still hold and why. When a deletion or correction request cannot be completed, we explain the reason and the record affected.

Privacy Policy Answers For blijitu

These Privacy Policy answers address the account and wallet questions you are most likely to ask before opening an account. They explain the practical route for checking data, changing details, managing cookies and contacting us from Indonesia. If your question is not listed, use support chat and describe the account step or payment reference involved. When access or eligibility is discussed, it depends on local law, and we may need to confirm account ownership before giving record-specific details.

The blijitu Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages, and payment records linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account requests. It explains why we use these records, how we retain them and how you can ask about them.

Start a request through signed-in account support chat and ask for the personal data connected with your account. We may confirm your phone or another account step before responding. Please do not send a password, wallet PIN or unrelated identity documents in the first message.

Yes, you can ask us to check and correct an account detail through the data change route. Name the field that appears wrong and explain the requested change. We verify account ownership first, then tell you whether the record can be changed and what step is still needed.

Yes. The Privacy Policy covers payment references and status details connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account requests. We use those records to match a cashier event and answer a status question, without asking for your wallet PIN.

Cookies can support your signed-in session, remember page settings and show whether a request completed. You can restrict or remove them in your mobile browser. If you disable session cookies, some account pages may ask you to sign in again or may not complete an account action.

We retain account data while it is needed for account operation, security checks, dispute handling or a legal need that applies where you are located. You can ask what remains and why. If a record must stay, we explain the reason rather than treating every request the same way.

Use support chat from your account for a data, cookie, correction or retention question. For a wallet-related matter, include the DANA, OVO, GoPay or QRIS payment reference through the cashier support path. We confirm ownership before discussing private records and answer through the same request.