Reference

bosku33 Privacy Policy and Your Account

Our bosku33 Privacy Policy explains what we collect when you create an account, enter the lobby, or connect DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account.

Clear data purposeWallet-linked recordsMobile access controlsPrivacy request path
bosku33 bosku33 Privacy Policy and Your Account
PRIVACY HELP ROUTES

Where to Ask About Your Data

A direct support route helps you resolve a privacy question without placing sensitive details in a game or wallet message. From your signed-in account, use the contact path shown near account help and include the email or phone detail attached to your account. We can then identify the correct record, explain a wallet status, or route a data request to the right team.

Team online

Account access path

If you cannot enter your account, contact us through the account help route and provide the registered phone detail only. We use an account step to check identity before discussing stored records.

Wallet status path

For a DANA, OVO, GoPay, or QRIS reference, send the transaction code and timestamp through support. Do not send a wallet PIN, password, or full payment login details.

Privacy request path

Ask us to access, correct, or remove eligible account data through the privacy contact path. We may request account verification so a change is applied to the right record.

DATA CONTROL DETAILS

What We Do With Account Records

Our handling starts with the account step you choose: account creation, phone verification, login, wallet connection, or a privacy request.

Account details

We may store your registered phone number, account identifier, login events, and verification result.

Device sessions

A mobile browser or desktop session can create technical records such as device type, browser details, IP address, and login…

Cookies

Cookies can remember sign-in state, language selection, and pages needed for the account path.

Account security

Phone verification comes before account access when our security flow requests it.

Record retention

We retain account, payment-reference, and support records for the period needed for account operations, security checks, dispute handling, and legal…

Change requests

You can ask us to correct an account detail or explain a stored record through the privacy contact path.

Privacy Policy Questions About bosku33

These answers address the searches we hear most often about the bosku33 Privacy Policy. They cover account access, wallet references, cookies, device records, retention, and the steps needed when you want to ask about or change your data.

The bosku33 Privacy Policy covers account details, phone verification, login events, device records, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account use.

We use your registered phone number to create an account link, complete phone verification when requested, protect account access, and identify the correct record when you ask for a privacy change.

Yes. The Privacy Policy covers transaction references, timestamps, status results, and matching details received when you use DANA, QRIS, OVO, GoPay, bank transfer, or a virtual account.

You can contact us through the privacy request path shown in your signed-in account. We will verify your account contact detail before explaining which stored records can be provided under applicable local requirements.

Send a correction request through the account privacy contact path with your registered phone or email detail. After verification, we can assess the requested change and update eligible account records.

We keep records for the period needed for account operation, security checks, payment reconciliation, support handling, dispute matters, and legal duties. The applicable period can depend on local law.

Use the privacy contact path to ask which cookie or device record relates to your session. You can also clear browser cookies, but doing so may sign you out and require another login.