Reference

boskuda Privacy Policy for Your Account

Your account details, wallet references and device sign-in records are explained in the boskuda Privacy Policy, so you can decide what to share before opening an account.

Account dataWallet recordsCookie choicesRequest changes
boskuda boskuda Privacy Policy for Your Account
SUPPORT ROUTES

Reach Us About Privacy Questions

A clear support path helps when you want to ask about account data rather than a game or wallet result. Use the support route linked from the account area and include the email or phone detail attached to your account. For a QRIS, DANA or bank transfer record, adding the reference helps us locate the relevant entry without asking you to resend unrelated details.

Team online

Account data request

Send a request through our account support route when you want to see, correct or clarify personal data connected with your boskuda account. We may ask you to confirm ownership first.

Wallet record question

For DANA, OVO, GoPay or QRIS records, include the payment reference and approximate date. This lets our support team separate wallet status from account identity details during a privacy response.

Access assistance

If you cannot reach the account area, use the support link beside the login path and describe the device used. We will explain the next verification step before discussing private account details.

DATA PRACTICE

Check How We Handle Your Data

Our Privacy Policy is applied through practical account steps: we separate identity details from payment references where possible, protect sign-in activity and keep records only for stated purposes.

Data categories

We may handle account contact details, verification responses, sign-in events, device details and payment references. The Privacy Policy explains how each category supports account access, payment matching or a requested support response.

Cookie choices

Cookies can remember a session setting and help us identify unusual sign-in behaviour. Your browser controls can limit cookies, although changing them may affect account access checks or saved preferences.

Account security

Before we disclose private account details or change a contact field, we may compare the request with the account sign-in and verification record. This reduces the chance of an unauthorised change.

Storage periods

We retain account and payment references for the periods described in our Privacy Policy, taking account of operational needs, dispute handling and applicable legal duties. Older records are removed or separated when no longer needed.

Your access request

Ask us to confirm the personal data linked to your account and explain its use. Include your account contact detail, and we may request an ownership check before sending a response.

Corrections and changes

If a phone number, email detail or account field is inaccurate, contact support with the corrected value. We will explain whether the change can be made directly or needs another verification step.

Ask About the Privacy Policy

These Privacy Policy answers focus on the questions you may have before opening an account or requesting help with a data record. We keep the route practical: identify your account, describe the request, and include a payment reference only when it is relevant to the question.

It covers account details, verification records, device and sign-in activity, cookies, payment references and support requests. It also explains purposes, storage periods, request routes and access that depends on local law.

A DANA or QRIS reference helps us match a cashier event with your account request and investigate a status question. We do not need unrelated wallet details when handling a privacy enquiry.

Yes. Contact us through the account support route with the email or phone detail attached to your account. We may verify ownership before confirming which personal data and records are connected with you.

Send the existing detail, the corrected value and your account contact through support. We may request a verification step before changing a phone number, email address or other field used for access.

Yes. It explains how cookies or similar device markers can remember access settings and help identify unusual sign-in activity. Browser controls can limit them, though some account checks may then work differently.

The Privacy Policy sets out storage periods by record type. Account and payment references may remain for operational needs, dispute handling or legal duties, then are removed or separated when the stated purpose ends.

Use the support route linked from your account or login area and describe whether the request concerns access, correction, cookies or a payment reference. Access is available where local law permits and may require verification.