Reference

Privacy Policy for Your depobos Account

Our Privacy Policy explains how we collect, use, store and protect the details connected with your depobos account in Indonesia.

Account clarityWallet recordsCookie choicesPrivacy contact
depobos Privacy Policy for Your depobos Account
PRIVACY CONTACT

Where to Ask About Your Data

A clear contact route matters when you want to understand a record or correct an account detail. We handle privacy questions separately from game and wallet troubleshooting, while still using the same account checks to protect you from an unauthorised request. If you are in Jakarta or elsewhere in Indonesia, send the account identifier you can safely share and describe the requested change. We will explain the next step, any verification needed and whether local rules affect the request.

Team online

Privacy request

Use our support contact to ask what account or device data we hold. Include your registered phone detail without sending a password, wallet PIN or full payment credential.

Account correction

Tell us which personal detail needs changing and why. We may confirm your phone verification before editing the record, so another person cannot redirect your account.

Access concern

If a login appears unfamiliar, contact support promptly and mention the device path involved. We can review session details and help secure the account before discussing other requests.

HANDLING DETAILS

Six Practical Privacy Commitments

We keep this policy practical by connecting each privacy rule to an account action you can recognise.

Account details

We use your contact and verification details to create the account, confirm access and respond to requests. We do not need your password in a support message, and you should never include it.

Device signals

A mobile browser or desktop session can generate device, browser and login-time records. We use these signals to identify unusual access and diagnose why a verified session may stop.

Cookie controls

Cookies may remember a login state or page preference. Your browser settings let you remove or block them, although some account steps may then require another verification.

Wallet references

DANA, OVO, GoPay, QRIS and bank transfer activity may produce a rail name, status and reference. We use those details to match receipts without asking you to reveal a wallet PIN.

Retention steps

We keep personal records while they support account access, dispute handling, security checks or applicable duties. When a retention reason ends, the record is deleted or made unavailable where appropriate.

Request changes

Send a privacy request through support with the account detail involved. We may ask for phone verification, then explain the result, any limits and the route for a follow-up.

Privacy Policy Answers for depobos

These Privacy Policy answers focus on the questions you may have before opening an account or when checking a wallet record. We keep the wording direct, because your request may involve a phone number, a device session or a payment reference. If your question is not listed, contact us with only the details needed to locate your account. Access depends on local law.

The depobos Privacy Policy describes how we collect, use, protect and retain account, device, cookie and wallet-related data. It also explains how you can ask about your records, request a correction or contact us about an eligible removal request.

We may collect contact details used for account creation, phone verification results, security records, device and browser signals, login activity, support messages and wallet reference details. The exact records depend on the account action you take and the rail selected.

Yes. The Privacy Policy covers the DANA, OVO, GoPay and QRIS status or reference details connected with your account, as well as bank transfer and virtual account records. We use them to match requests and resolve receipt or status questions.

Device and browser signals help us identify unusual access and investigate a failed session. Cookies can retain login continuity or page preferences. You can manage cookies in your browser, though blocking them may trigger another account check.

You can contact support to ask what eligible account data we hold or to request a correction. We may confirm your phone verification first. We will explain the result, any required evidence and whether local law limits the request.

We retain records while they are needed for account access, security checks, support, dispute handling or applicable legal duties. Once the relevant reason ends, we delete or restrict the record where appropriate, subject to local requirements.

Contact our support route promptly and describe the account or device session you do not recognise. Do not send a password, wallet PIN or full payment credential. We can review the access details and explain the next security step.