Reference

pakbostogel Privacy Policy In Plain English

pakbostogel explains how we collect, use, protect and retain the details connected with your account and wallet activity.

Account detailsWallet referencesCookie choicesPrivacy requests
pakbostogel pakbostogel Privacy Policy In Plain English
PRIVACY HELP PATH

Ask Us About Your Account Records

A privacy question should not require you to search through payment screens.

Account request Ask us to correct a phone number, contact detail or account reference through the…
Wallet record query For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, include the…
Access concern If a new device or phone verification step looks unfamiliar, contact support from the…
SIX DATA CONTROLS

Six Ways We Handle Privacy Carefully

We keep this policy practical by linking each data use to an account action you can recognise.

Purpose-based collection

We collect account details, phone verification results, device signals and transaction references for access, payment matching, security checks and support responses rather than unrelated uses.

Cookie choices

Cookies can remember a signed-in session and help us understand whether a page request is working. You can adjust browser cookie controls, although some account steps may then need repeating.

Device security

We may compare a new browser or phone with earlier access signals. An unusual pattern can lead to an additional account check before private wallet or profile details are shown.

Retention by purpose

We keep account and payment records only for the period needed for the stated account, security, support or legal purpose. When that purpose ends, records are removed or separated where practical.

Correction requests

You can ask us to correct inaccurate profile or contact details. Send the request through the signed-in support path, and we may ask for phone verification before making a change.

Privacy contact

For access, deletion or use questions, contact us through the support link beside your account path. Include enough detail to locate the request, but never share a wallet password.

Seven Privacy Policy Answers For You

These Privacy Policy answers focus on the account and payment records you are most likely to ask about before opening an account. They also explain the practical route for access, correction and deletion requests when the service is available where local law permits.

It covers account details, phone verification, device and browser signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps confirm that you control the account before access or a profile change. We record the verification result and related account event, not your private wallet password.

No. Our payment records may contain a route, reference, status, amount and timestamp for DANA or QRIS, but you should never send us a wallet password or secret code.

You can ask through the signed-in support path beside your account or cashier area. We may request phone verification and enough account detail to make sure the response reaches the correct person.

Send a correction request through support and identify the inaccurate phone, contact or transaction reference. We will check the request against your account before updating the relevant record.

Retention depends on the purpose for the record, such as account security, payment matching, support or a legal requirement. We remove or separate records when the applicable purpose ends.

You may request deletion through the privacy support route. We assess the request under applicable rules, because some security, payment or legal records may need to remain for a defined purpose.