Reference

Privacy Policy For Your boswd Account

Our Privacy Policy explains what data we collect when you open a boswd account, use the mobile lobby, or check DANA and QRIS status.

Account dataDevice choicesPayment recordsContact path
Explore Our Lobby Read FAQ
boswd Privacy Policy For Your boswd Account
CONTACT WHEN NEEDED

Privacy Help Beside Account Support

A clear contact path helps you act on the Privacy Policy without searching through the lobby. Ask us about a data copy, a correction, a deletion request, or the reason a payment reference is connected to your account. Include the phone number linked to your account and the relevant DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference. We use those details to locate the right record while limiting unnecessary disclosure. Your request remains subject to identity checks and applicable local law.

Team online

Account data request

Ask for the account data we hold by using the support path attached to your signed-in account. We may ask you to confirm your phone number before sending a copy, so private account details do not go to the wrong person.

Payment record question

If a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account entry looks unfamiliar, send its reference through support. We compare the payment record with your account details and explain what we can disclose under this Privacy Policy.

Correction or removal

You can ask us to correct inaccurate account data or remove eligible details. Tell us which field needs action and why. We first verify ownership, then explain any records we must retain for security, transaction matching, or local legal duties.

HOW DATA IS HANDLED

What We Do With Your Account Data

The Privacy Policy is practical: it connects each data use to an account step you can recognise. Phone verification supports account ownership checks; device signals help us spot unusual sign-in patterns; payment…

Account and phone details

We use your account identifier and verified phone detail to link sign-in activity with the right account. Before discussing private records or completing a data request, we may repeat an account step so the request comes from you.

Device and session signals

When you move from login to the mobile lobby, we may receive browser, device, session, and security signals. These help us maintain the session and investigate unusual access; they are not a reason to collect unrelated content from your device.

Cookies and saved choices

Necessary cookies can keep a signed-in session working and remember choices made during account access. Your browser can manage cookie settings, although changing them may affect the account path, payment status display, or return from a QRIS step.

Payment matching

Payment references from DANA, OVO, GoPay, QRIS, bank transfer, or virtual account routes help us match a transaction with your account. We do not need your wallet password to make that match, and support only asks for relevant reference details.

Retention and removal

We keep records for as long as needed for the purpose described in this policy, account security, transaction reconciliation, or a local legal requirement. When a retention reason ends, we delete, anonymise, or restrict the record where the available process allows it.

Requesting policy changes

To request a copy, correction, restriction, or eligible removal, use the support contact shown with your account and describe the action clearly. We confirm your identity, assess the request under local law, and explain the result or any reason a record must remain.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the account steps that matter most before you open access. We explain the data connected to phone verification, device use, payment references, cookies, and requests made through support. If your question concerns a specific record or transaction, include the account phone detail and payment reference so we can respond to the correct account. Eligibility and access depends on local law.

The boswd Privacy Policy covers data created through account opening, phone verification, sign-in, device sessions, lobby activity, cookie choices, support requests, and payment references. It explains why we use each category, who may handle it for an account task, and how you can request access or correction.

We may collect the account details you submit, your verified phone detail, device and browser signals, session events, and records needed to match payment activity. The Privacy Policy does not give us access to your DANA, OVO, GoPay, or QRIS wallet password.

Phone verification helps connect account access with the person who opened the account and gives support a way to confirm ownership. We may ask for that same account step before discussing a data copy, correcting a detail, or handling a request about a payment record.

DANA and QRIS references help us match a payment request with the correct account and check whether its status reached our records. We use the reference for reconciliation and support, not for unrelated purposes. Bank transfer, virtual account, OVO, and GoPay records follow the same policy logic.

Yes. Send a clear request through the account support path and identify the data you want corrected or removed. We verify ownership first, then assess the request under local law. Some records may remain when needed for security, transaction matching, or a legal requirement.

We keep each category only for the period needed for its stated purpose, account security, payment reconciliation, or a local legal duty. The period can differ between a phone verification record, a device security event, and a DANA or QRIS transaction reference.

Use the support contact linked to your signed-in account and state that your request concerns the Privacy Policy. Include your account phone detail and, if relevant, a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference so we can locate the right record.

Related Pages

boswd Indonesia About Us bola885 celebsroulette kliat77