Reference

Privacy Policy for depoboss Accounts

Our Privacy Policy explains how we collect, use and protect the details connected with your depoboss account, including phone verification, device access and wallet activity.

Account dataWallet recordsDevice accessCookie choices
depoboss Privacy Policy for depoboss Accounts
CONTACT THE TEAM

Privacy Help Beside Your Account

A clear contact path helps you ask about personal data without explaining your whole account history.

Account privacy request Ask us to locate the personal data connected with your account.
Wallet data question If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, include the visible status…
Access and correction Tell us which detail needs correction or which account record you want explained.
DATA CONTROL

Your Data Inside depoboss

Privacy depends on practical controls, not a general promise. We separate account details from the wider browsing context, use phone verification before account access, and limit internal handling to the purpose that…

Account security

Phone verification is part of the account access path. Keep your sign-in details private, sign out on shared devices and contact us if a session or profile detail does not match your activity.

Mobile and desktop data

Opening the lobby on a phone or desktop can create technical records such as device type, browser state and access time. We use this context to support sessions and investigate unusual access.

Cookie choices

Cookies can preserve sign-in state and help us understand which page produced a support request. Your browser controls some cookie settings, although changing them may affect account access or page functions.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may appear as status or reconciliation references. We use those records to connect a payment question with the correct account.

Retention decisions

We do not keep every record forever by default. Retention depends on the account purpose, unresolved support matters and applicable legal duties, including records needed to establish what happened.

Change or removal request

You can ask us to correct personal data or discuss removal of eligible records through the account support route. We verify ownership first, explain any limits and record the request outcome.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account actions you are most likely to take before using depoboss. They cover what we collect, why phone verification matters, how wallet references are handled, what cookies do and how to request a change. If your question concerns access, remember that it depends on local law. Share only the details needed for us to identify the relevant account or record.

The Privacy Policy covers account details, phone verification, device and browser records, cookie activity, support messages and payment references. It explains why we use each category, how retention is assessed and how you can ask about access, correction or removal where local law permits.

Phone verification helps connect account access with the correct person and reduces mistaken disclosure during support. We may use the verified contact detail when you ask about DANA, OVO, GoPay or QRIS status, but you should never send us a password or one-time code.

Yes. The Privacy Policy covers payment references that appear when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. These references help us check status and resolve an account question; they are not a request for your private wallet credentials.

When you sign in from a phone, tablet or desktop browser, technical records may include device type, browser state, access time and session details. We use this information to maintain access, understand errors and investigate activity that does not match your account.

Contact us through the support path connected with your account and identify the detail that needs correction. We verify account ownership before changing information, then explain the next step. Requests are handled according to applicable requirements and may have legal or record-keeping limits.

You can ask whether specific account data is eligible for removal under the Privacy Policy. We first verify the request, check whether the record is still needed for support or a legal duty, and tell you which information can be removed or retained.

Use the account support route and describe the privacy issue in plain English, such as a cookie concern, an unfamiliar wallet reference or a copy request. Include no password or verification code. We use the account details available to route your request correctly.