Reference

bolakita Privacy Policy Explained

bolakita Privacy Policy explains what we collect when you open an account, use the lobby, or check DANA and QRIS payment status.

Account dataWallet recordsCookie choicesSecurity requests
bolakita bolakita Privacy Policy Explained
CONTACT ROUTES

Privacy Help Beside Your Account

A direct support route helps you resolve a Privacy Policy question without guessing which account detail matters. Tell us the email or phone number linked to your account, describe the request, and include a payment reference only when it is needed for identification. We use the account support path for access questions, data corrections, cookie choices, and payment-status concerns. Do not send wallet PINs or full passwords. We may ask for an account step that confirms you are requesting information about your own data.

Team online

Account support

Use the signed-in support path when you want to ask about account data, phone verification, or a Privacy Policy request. We can check the account record linked to your message and explain which next step is needed before sharing or changing personal details.

Payment status

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, send the transaction reference through account support. We use that reference to locate the relevant record while keeping your wallet PIN, password, and unrelated payment details out of the request.

Access questions

If a Privacy Policy page or account setting does not open on your phone, tell us your device type and browser path. We can explain the available access route and whether a regional restriction applies, because access depends on local law.

DATA HANDLING

What We Do With Your Details

We keep the Privacy Policy practical: each data use has a reason connected to account access, payment matching, security, support, or a legal requirement.

Account information

We use the details you provide during account creation and phone verification to identify your account, send account messages, and…

Device signals

When you sign in on mobile or desktop, we may record device, browser, and login signals used to protect account…

Cookie choices

Cookies may keep a session active, remember selected settings, or help us understand page errors.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference can be used to match a payment event with…

Security steps

We may request phone verification or another account check before changing personal details or releasing account-specific data.

Retention requests

We keep personal data for the operational or legal period connected to its purpose, then remove or restrict it when…

Privacy Policy Answers For You

These Privacy Policy answers cover the account and payment questions we expect you to ask before opening or using an account. They explain the practical path for data access, corrections, cookies, device signals, and contact requests. If your situation is not listed, send the question through account support and we will identify the relevant record or explain why a local restriction applies.

The bolakita Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages, and payment references. It explains why we use each category, how we protect account access, how long records may remain, and how you can ask about or change your data.

Send an account support request using the contact detail linked to your account. State that you want access to your personal data and include the relevant account step, such as phone verification. We may ask for an identity check before giving account-specific information.

Yes. The Privacy Policy includes payment references connected with DANA, QRIS, OVO, GoPay, bank transfer, and virtual account activity. We use those references to match a payment event and answer status questions. We do not need your wallet PIN or full password.

Yes. Contact account support with the detail that needs correction and the account step that confirms your request. We may verify your phone or another account signal before changing the record. If a correction is limited by a legal duty, we will explain the restriction.

On a mobile browser, cookies can support sign-in continuity, saved page choices, and error checks. You can manage them through your browser settings. If you remove necessary cookies, you may need to sign in again or repeat a Privacy Policy access step.

We keep personal data for as long as it is needed for account access, payment matching, security, support, or a legal requirement. The period can differ by record type. Ask account support about a specific record, and we will explain the applicable retention position.

Yes. Account access and some data requests depend on local law. Where local law permits, we provide the relevant Privacy Policy details and a route for access, correction, or deletion questions. If a restriction applies, contact account support so we can explain the available path.