Reference

What Governs Your Account on bosgg

Every account on bosgg operates under a clear set of terms that define how we handle your data, your wallet activity, and your access rights — with eligibility depending on local law and the region you access from.

Account TermsPrivacy & DataPayment PolicyDANA · OVO · GoPayUser Rights
bosgg What Governs Your Account on bosgg
DATA & SECURITY

How We Protect and Manage Your Information

Account security and data handling sit at the centre of how bosgg operates. From the moment you register, your session is protected and your wallet details — whether linked to DANA, OVO, or GoPay — are stored with access controls that limit who inside the platform can see them. Here is what that means in practice across six areas you can check against your own account.

Data Storage

Your account data is stored on servers with access restricted to authorised personnel. We do not retain payment PINs or full wallet credentials — only the reference IDs needed to match a transaction to your account.

Cookie Policy

We use session cookies to keep you logged in across your browser and the mobile lobby. You can clear these at any time from your device settings; doing so will log you out of your current session.

Account Security

Login uses OTP verification sent to your registered mobile number. If you switch devices — for example from Android to a different phone — the OTP step re-triggers automatically to confirm it is still you.

Data Retention

Transaction records linked to your DANA, OVO, or GoPay wallet are kept for the period required under applicable rules. After that period, records are deleted or anonymised unless a dispute is open.

Who to Contact

For any question about what data we hold on your account, email our support team with your registered mobile number and a description of what you need. Data requests are handled separately from general account help.

Requesting Changes

You can request a correction to your registered details, ask us to delete specific records, or request a full export of your account data. Submit via email; we will confirm receipt and give you a handling timeline.

CONTACT CHANNELS

Reach Us About Any Legal or Policy Question

If something in our terms is unclear, or if you want to make a formal request about your account data or transaction records, the fastest path is through the channels below. Our support team handles policy-related queries alongside account help, and they can escalate data requests to the relevant internal team. For formal written requests — such as data deletion or a record of all transactions tied to your DANA or OVO wallet — using the email channel ensures your request is tracked and responded to within our stated handling window.

Live Chat Available around the clock from the lobby. Use this for quick policy questions, account access issues, or to confirm what a specific clause means before you act on it.
Email Support Send formal data requests, account closure notices, or written policy queries by email. This channel creates a traceable record of your request and our response.
Account Help Center The in-app help section covers the most common policy questions — wallet verification steps, transaction records, how to update your registered details, and what triggers a review.

Common Questions About bosgg Legal Terms

These are the questions we hear most often about how our policies work in practice — covering account rights, data access, payment records, and what to do when something does not look right.

Access and eligibility depend on local law and the region you are in. If local law in your area permits access, then yes, these terms govern your account. If your region restricts access, we may limit or suspend account activity until eligibility is confirmed.

When you deposit via DANA or OVO, we record the transaction reference ID, the amount, the timestamp, and the wallet type. We do not store your DANA or OVO PIN. This record is linked to your account and is visible in your transaction history.

Yes. Send an email request with your registered mobile number and we will compile a summary of the data tied to your account — including transaction records, login history, and any account changes. We will confirm the handling timeline when we receive your request.

Email our support team with a deletion request. We will verify your identity using your registered mobile number and OTP before processing. Note that some transaction records may be retained for the period required under applicable rules even after deletion is requested.

If GoPay reverses a transfer, we reverse the corresponding account credit and update your transaction record to show the reversal. You will receive a notification. If you believe the reversal was an error, contact support via live chat with the GoPay reference number.

When we make a material change to our terms, a notification appears the next time you open the lobby. The updated terms take effect on the date stated in the notice. If you disagree with the change, you can close your account and withdraw your balance before that date.

Session cookies keep you logged in while you navigate the lobby on your phone or browser. They do not track your activity outside the platform. You can clear them from your device settings at any time, which will end your current session and require you to log in again.

A review may be triggered if we detect a login from a new device, a mismatch between your registered name and the wallet name on a DANA or OVO transfer, or unusual activity on your account. You will be notified and may be asked to re-verify via OTP.

Yes. Submit a change request via email or through the account help section. We will verify your identity before making any changes. Updating your linked wallet — for example switching from OVO to GoPay as your primary withdrawal method — requires re-verification of the new wallet details.

Formal requests submitted by email are escalated from the general support team to an internal team responsible for data and policy matters. You will receive a confirmation when your request is received, along with the expected response window.