Reference

bolagg Legal for Clear Account Access

bolagg Legal sets out how we handle your account, payment records, cookies, security checks and requests to change personal details.

Account termsPayment recordsData requestsLocal access
bolagg bolagg Legal for Clear Account Access
CONTACT PATHS

Browse Legal Help Through Your Account

A clear contact path matters when a Legal question affects your account or payment record.

Account access Use the account support route when a phone verification step, location check or policy…
Wallet records For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, include the transaction…
Policy requests Ask through the account contact path when you need a copy of policy wording…
DATA PRACTICE

Explore How Legal Controls Your Details

We apply the Legal policy to the information needed for account access, payment matching, security checks and support handling.

Account data

We use the details attached to your account to manage sign-in, phone verification, access decisions and policy acknowledgements. Keep them accurate so a later request or payment check can be matched correctly.

Cookies

Cookies and similar storage can remember session choices and help keep the account path working across a mobile browser and desktop browser. Your browser settings control whether some cookies are accepted.

Security checks

A verification request may compare your account details with payment or access records. We do not need your password or one-time code in a support message, and you should never place either in a request.

Payment retention

Records for DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri or BNI transfers may be retained when needed to reconcile an account, investigate a dispute or meet a legal record duty.

Correction requests

If your name, phone number or other account detail is inaccurate, use the policy contact route after login. State the field needing correction and provide the account reference requested by our team.

Access questions

For a question about eligibility, location or a policy decision, ask through account support. We can explain the applicable step, while access remains dependent on local law and the details available.

Check Common Legal Questions

These Legal answers cover the points most often raised before account access: what data we use, how payment records are handled, how requests are made and why local eligibility matters. Read them alongside the policy wording shown in your account, particularly before submitting phone or wallet details.

bolagg Legal covers account details, phone verification, payment matching, cookies, security checks, retention and request procedures. Read the policy before opening an account, because access depends on local law.

Yes. Legal explains that DANA, QRIS, OVO and GoPay records can be matched with your account to confirm payment status. Bank transfer and virtual account references may be handled in the same way.

Yes. Use the account support route and identify the name, phone number or other field that needs correction. We may ask for an account reference so the request reaches the correct record.

Legal covers cookies used to maintain a session and remember account-path choices. Your mobile or desktop browser settings control cookie acceptance, although refusing some cookies may affect sign-in or policy access.

Phone verification helps connect the account to the details you submitted and supports security checks around wallet activity. We will not ask you to place a password or one-time code in support messages.

You can use the account contact route to ask about an access decision or eligibility step. We can explain the policy process and available request path; access itself depends on local law.

Retention depends on the record and the operational, security or legal reason for keeping it. Payment references and account history may remain when needed for reconciliation, disputes or a legal record duty.