Reference

boskode Privacy Policy for Your Account

Our boskode Privacy Policy explains what we collect when you open an account, verify your phone and use DANA, OVO, GoPay or QRIS.

Account clarityWallet recordsCookie choicesDirect requests

Explore Our Lobby Read FAQ

How DANA and QRIS Data Are Handled

boskode Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy applies to information created through your boskode account and the actions you take after signing in. We receive details you enter, such as your name, phone number and verification results, then connect them with account activity, device type, browser settings and security events.

1
When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we may record the payment reference, amount, status and related account identifier so we can match a receipt or investigate a stalled wallet status. We use these records to provide account access, detect
2
unusual sign-in activity, answer requests and keep transaction history accurate. We do not ask for your wallet PIN. Access to our services depends on local law, and data handling may be adjusted when a lawful Indonesian request requires it.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

ACCOUNT HELP PATH

Where to Ask About Account Data

A clear account route helps when a phone check, sign-in record or wallet status needs attention.

Account access Tell us which phone verification step stopped, and include the device or browser path you used. We can then match your request with the relevant sign-in and security record.

Wallet records For DANA, OVO, GoPay or QRIS questions, share the transaction reference and status shown in your account. Please remove wallet PINs and unrelated private details before sending.

Policy requests Ask for a copy, correction or removal assessment through the account support route. We may request account verification first so a private record is not disclosed to the wrong person.

SECURITY PRACTICE

How We Protect Account Records

Privacy work is tied to practical account controls, not a separate promise outside the lobby. We limit record access to the work needed for verification, wallet matching, security checks and support, while…

Collected details

We handle the contact and verification details you submit, plus sign-in, device and transaction references created while your account is active. These records help us connect a request to the correct profile.

Cookies

Cookies can keep a browser session working and help us recognise account security events. You can clear or restrict them through your mobile or desktop browser settings, though some account steps may need a fresh sign-in.

Account security

Phone verification before account access helps us separate your request from an unknown sign-in. We examine unusual device or browser signals and may ask for another account check.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference lets us match a wallet event without requesting your wallet PIN. We keep the record tied to the relevant account activity.

Retention choices

When you ask us to correct or remove data, we review the account record, transaction context and any lawful need to retain it. We explain the outcome through the same verified support path.

Your request route

Use the account support area for access, correction, deletion or policy questions. Include your phone number and reference date, but never send a wallet PIN or another person’s private data.

Privacy Policy Answers for boskode Accounts

These answers address the questions we expect before you open an account or connect a local wallet. They explain the practical steps around access, records and requests, while the full Privacy Policy remains the controlling page. If your situation is specific, use the account support route with a verified profile.

It covers account details, phone verification, sign-in events, browser and device signals, cookies, game activity connected to your profile, and payment references created through DANA, OVO, GoPay, QRIS or bank transfer.

We use your phone number for account creation and verification before access. It helps us connect your request to the right profile and investigate an unfamiliar sign-in without asking for your wallet PIN.

Yes. We may store the QRIS reference, amount, status and account identifier needed to match a receipt or check a stalled payment. We do not need your QRIS wallet PIN to perform that check.

Yes. Send a correction request through the verified account support route with the affected field and a short explanation. We may confirm your phone verification before changing or disclosing private account details.

Use the account support route and ask for a deletion assessment. We review the request against active account needs, transaction records and any lawful retention requirement, then explain which records can be removed.

Cookies may support your sign-in session and security checks on a mobile browser. You can clear or restrict them in your browser settings, but doing so may require you to verify and sign in again.

Open the Privacy Policy page at /privacy-policy/ from the account or site footer. If access is discussed, it depends on local law; use the verified support route when the page or your records cannot be reached.

boskode Privacy Policy for Your Account

Where to Ask About Account Data

How We Protect Account Records

Collected details

Cookies

Account security

Payment matching

Retention choices

Your request route

Privacy Policy Answers for boskode Accounts

01 What does the boskode Privacy Policy cover?

02 Why does boskode need my phone number?

03 Does the Privacy Policy record my QRIS payment?

04 Can I ask boskode to correct my account data?

05 How can I request deletion under the Privacy Policy?

06 Does boskode use cookies on mobile browsers?

07 Where is the Privacy Policy available when I sign in?

Related Pages