Reference

bso118 Privacy Policy for Your Account

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

Account dataWallet recordsDevice choicesPrivacy requests
bso118 bso118 Privacy Policy for Your Account
REQUEST HELP

Ask About Privacy Through Account Help

A privacy question should have a clear route, so we keep requests close to the account help path rather than asking you to post personal details publicly.

Privacy request path Use the account help panel to ask what data we hold, why a record exists, or how to request a correction. We may ask for a matching account detail before discussing private records.
Wallet receipt check For a DANA, OVO, GoPay or QRIS question, attach the payment receipt reference rather than a wallet password. This lets us trace status while keeping secret wallet credentials outside our support exchange.
Access screen support When your phone verification or login fails, begin at the access screen and choose account help. We use the request details to separate an access issue from a privacy request before replying.
DATA PRACTICES

Browse How We Handle Your Records

Privacy is part of each account step, from the first phone check to a later wallet-status question.

Account details

We use the details you submit during account opening and phone verification to connect your sign-in with the correct account. Do not enter another person’s contact details or share your verification code.

Device signals

Login time, browser type, device signals and security events can help us spot unusual access. On mobile, clearing browser data changes local preferences; it does not automatically close or erase your account.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may be retained to reconcile your instruction. We need the reference for tracing, not your wallet PIN or full secret credential.

Cookies and storage

Cookies and similar browser storage can keep a session, language choice or access preference working. You can clear them through your browser settings, though doing so may require another phone verification.

Retention periods

We retain records for as long as needed for account operation, payment reconciliation, security checks, dispute handling or duties that apply where local law permits. Requests to remove data are assessed against those needs.

Security requests

If you suspect someone accessed your account, use account help promptly, change the account credential through the access path, and mention the affected device. We may restrict discussion until your account identity is checked.

Check Privacy Policy Answers Before Opening

These Privacy Policy answers focus on the account, device and payment questions you may search before opening an account. We keep the wording practical: you can see which records matter, how to request a change, and why a phone or wallet step may require a security check. For access or eligibility, the applicable position depends on local law.

The bso118 Privacy Policy covers account details, phone verification, login events, device signals, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use phone verification to connect you with the correct account and reduce mistaken or unauthorised access. If the check fails, start from the access screen and use account help instead of sharing a verification code.

No wallet PIN or secret password should be sent to us. The Privacy Policy allows us to retain a transaction reference or receipt detail needed to match DANA, OVO, GoPay or QRIS activity with your account request.

Open the account help panel, choose the privacy subject, and state which record needs correction. We may ask for a matching account detail before making a change, and the request remains subject to duties where local law permits.

Cookies can retain a session, language choice or browser preference. Clearing them through your phone or desktop browser may sign you out and trigger phone verification again, but it does not erase records held for account or payment purposes.

We keep data for the period needed to operate the account, reconcile a payment, investigate security events, handle a dispute or meet an applicable duty. Removal requests are assessed against each record’s purpose and legal need.

Yes. Use the privacy route shown in account help and ask what data would be collected during opening, phone verification or wallet use. Access and eligibility still depends on local law, including where local law permits.