Reference

Open bosdepo Privacy Policy Clearly

bosdepo Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and contact our support desk.

Clear data purposesWallet record contextAccount access stepsCookie choices
bosdepo Open bosdepo Privacy Policy Clearly
CONTACT THE DESK

Check Privacy Help Through Support

A direct support path helps when you need to ask about a Privacy Policy request, an account record or a wallet reference.

Policy questions Use the support desk when you want to understand a Privacy Policy clause, the purpose of a requested account field, or the type of record linked to your phone verification. Include your account contact detail so we can identify the request without asking for your password.
Wallet records If a DANA, OVO, GoPay or QRIS receipt appears incorrectly, send its reference and status through support. We can compare the payment record with the account request, explain what is retained for tracing, and tell you which correction path applies.
Access requests Ask support to help with a copy, correction or deletion request connected to your account. We may confirm your phone or account step before changing records, because the request must come from the person connected with the data.
DATA HANDLING

Switch Through Our Privacy Controls

We keep this policy practical by linking each data use to an account action: opening access, checking a wallet status, maintaining a session or answering support.

Account details

We collect details you provide during account creation and phone verification so we can identify your account and respond to access requests. If a field changes, contact support with the old and new detail; we may verify the request before updating the record.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account request can create a reference and status record. We use that trail to match the cashier event to your account, investigate a mismatch and answer a receipt question without storing your wallet password.

Cookies and devices

Cookies and device signals can keep your session, remember a setting and help detect unusual access. You can manage browser cookie controls, but removing them may require another login or make parts of the Privacy Policy request path harder to use.

Account security

We use phone verification, session checks and account activity signals to reduce unauthorised access. Keep your password private and contact support if a sign-in or device looks unfamiliar; we may pause a request while confirming that you control the account.

Retention timing

We retain information only as long as needed for the stated account, payment tracing, support or legal purpose. When a record no longer has a valid purpose, we remove it or separate it from direct account identifiers, subject to duties that still apply.

Changes and contact

To request access, correction or eligible deletion, contact our support desk and identify the account record involved. We may ask for a verification step, then explain the result or any reason a record must remain. We will publish material policy changes on this page.

Browse Privacy Policy Answers

These Privacy Policy answers focus on the searches you may make before opening or using a bosdepo account. We explain the practical route for data access, wallet references, cookies, account checks and deletion requests. Where a rule depends on Indonesia or another location, access depends on local law, and support can clarify the process that applies to your account.

The bosdepo Privacy Policy covers account details, phone verification, device signals, cookies, payment references, support messages and activity needed for access or security. It explains why we use each category, how long we retain it, and how you can request access or correction.

We use phone verification to connect an account request with the person making it, protect sign-in access and confirm certain data requests. We do not need your wallet password for this step. If your number changes, contact support so we can explain the available account process.

Yes. The Privacy Policy covers references and statuses connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those records to match a cashier request, investigate a mismatch and answer a receipt question; wallet passwords are not requested through support.

Contact the support desk and state that you want an account data request under the Privacy Policy. Include the account contact detail and the record category, such as phone verification or QRIS receipt status. We may complete an identity check before sending or discussing the result.

You can ask us to correct inaccurate account data by contacting support with the affected field and the correct detail. We may compare the request with your phone verification or account step before making a change. We will explain if a record must remain unchanged for a valid purpose.

Cookies can keep your login session, remember a setting and help connect a Privacy Policy request with the right account. Browser controls let you remove or restrict them, although another login may be needed and some request steps may not work as expected.

Ask support for deletion of an eligible record and identify the account connected to it. We assess the request under applicable rules. Some details may remain for payment tracing, account security, support history or a legal duty; where local law permits, we remove or separate records when the purpose ends.