Reference

bola07 Privacy Policy for Your Account

bola07 Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity.

Account dataWallet referencesDevice accessPolicy requests
bola07 bola07 Privacy Policy for Your Account
REQUEST A HAND

Where Privacy Questions Go

A clear contact path helps when you want to ask about a Privacy Policy request, an account record or a payment reference. We ask you to contact our support team through the support route shown after sign-in and include the phone number linked to your account. A receipt reference, device type and approximate access time can help us locate the right record without asking you to send a wallet password. If login or wallet status stalls, keep the request focused on the data question so we can route it correctly.

Team online

Account request

Use the signed-in support path to ask what account details we hold or to request a correction. Include your verified phone number and the relevant account step, such as phone verification or a sign-in attempt, so we can match the request to your record.

Payment record

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, send the payment reference and date through support. We use that reference to check the account ledger while avoiding requests for your wallet PIN, password or full banking credentials.

Access concern

If you think another device reached your account, tell us the device type, approximate time and last action you recognise. We can review the access record and explain the next account step without asking you to disclose a sign-in password in a support message.

HOW WE HANDLE DATA

Privacy Controls Behind Your Account

Privacy Policy choices should be practical, not hidden behind broad wording. We separate account details, access records and payment references so a support request can address the right category.

Collected account details

We may receive your phone number and account details when you open an account or complete phone verification. We use them to create the requested profile, support sign-in and answer account questions. We do not need your wallet PIN for a DANA, OVO, GoPay or QRIS request.

Device and cookie use

When you move from login to the lobby on a phone or desktop browser, technical signals can record device type, browser session and access time. Cookies or similar storage can support session continuity. You can clear or restrict them in your browser, although some account steps may then need to load again.

Account security

Phone verification gives an account request a direct identity check, and sign-in records help us spot access that does not match your usual pattern. Keep your password private and contact support if a device action looks unfamiliar. We will not ask for your password inside a support message.

Payment references

A payment record can contain a route such as QRIS, DANA, OVO, GoPay, bank transfer or virtual account, together with a reference, amount and status. We use those fields to match account activity and answer receipt questions, while wallet credentials remain with the relevant payment service.

Retention approach

We keep records for the period needed to operate the account, resolve a payment or access question, maintain security records and meet applicable legal duties. When a record is no longer needed for those purposes, we remove it or separate it from direct account identifiers where the process allows.

Changes and requests

You can ask us to correct an inaccurate account detail, explain a data use or address an eligible deletion request through the signed-in support route. Include your verified phone number and request type. We may need to confirm account control before changing or releasing personal details.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and payment questions we hear most often from people considering bola07. They explain what to send, what we use a record for and how local access wording applies. If your case involves a specific sign-in, wallet reference or phone verification step, include that detail when you contact us.

The bola07 Privacy Policy covers account details, phone verification, sign-in records, device signals, cookies, support messages and payment references. It explains how we use those records for account access, security, payment matching and requests. Access or eligibility depends on local law and applies where local law permits.

No. Our Privacy Policy concerns payment references and status details used to match an account record. We do not ask you to send a wallet PIN or password through support. For a DANA, OVO, GoPay or QRIS question, provide the receipt reference and date instead.

We may record device type, browser session, sign-in time and related technical signals when you access the account on mobile or desktop. The Privacy Policy explains that these records help maintain sessions and investigate unusual access, including a move from phone verification into the lobby.

Use the signed-in support path and ask for a Privacy Policy data correction. Include the phone number linked to your account, identify the inaccurate field and describe the account step involved. We may confirm account control before changing personal details so the request reaches the right profile.

You can submit an eligible removal request through support, and our Privacy Policy team will assess which records can be removed. Some account, security or payment records may need to remain for an applicable legal duty or an unresolved account question. Where local law permits, we explain the outcome.

We retain payment references only for the period needed to match account activity, answer receipt questions, protect access and meet applicable legal duties. A reference may identify DANA, OVO, GoPay, QRIS, bank transfer or virtual account status, but it is not your wallet credential.

Contact us through the support route shown after sign-in and state that your request concerns the Privacy Policy. Add your verified phone number, request category and any relevant device or payment reference. Do not include a password or wallet PIN; those details are not needed for a policy response.