Reference

bansos138 Privacy Policy for Indonesia

Our Privacy Policy explains which account, wallet and device details we use when you open an account, sign in and reach the lobby.

Account dataWallet recordsDevice choicesPolicy requests
bansos138 bansos138 Privacy Policy for Indonesia
REQUEST SUPPORT

Privacy Help Through Your Account Path

A clear request path helps you ask about the Privacy Policy without sending sensitive details to the wrong place.

Account privacy request Use the account support route to ask what personal data is held, why it is used or which records relate to your sign-in and verification step.
Wallet record question When your question concerns DANA, OVO, GoPay or QRIS, provide the payment reference rather than a wallet password. We use that reference to locate the relevant record.
Device access concern Tell our support desk if a phone or browser entry looks unfamiliar. We can review the account event, explain the security step and help you request a correction.
HANDLING DETAILS

How We Manage Privacy Requests

Our handling process follows the account journey rather than collecting unrelated details. We separate identity checks from payment references, use security controls around sign-in data and keep policy requests attached to a…

Data collection

We collect details needed for account creation, phone verification, sign-in security, payment matching and support. Browsing events may include device type, browser settings and pages opened.

Cookie choices

Cookies and similar tools can remember session settings, protect account pages and show whether a page request is valid. You can adjust cookie controls through your browser settings.

Account security

We use sign-in events, phone verification records and device signals to identify unusual account activity. Do not send passwords or wallet access codes in a privacy request.

Retention practice

We keep account, payment and support records for the period needed to operate services, resolve disputes or meet legal duties. After that period, records are removed or de-identified.

Change request

Ask us to correct inaccurate contact or account details through the support route linked to your account. We may request a verification step before changing data that affects access.

Third-party handling

Payment providers may handle their own records when you use DANA, OVO, GoPay, QRIS or bank rails. Their separate privacy terms apply to data they process directly.

Privacy Policy Answers for Your Account

These questions address the privacy points most often checked before account access. We keep the answers tied to real account steps, payment references and device behaviour, so you can decide what request to make and where to begin. If your situation involves eligibility, access depends on local law and the details available for your account.

It covers account details, phone verification, sign-in events, device data, payment references and support cases created through our services. It also explains retention, cookies, security use and requests to correct or remove data.

DANA and QRIS create payment records that may be matched to your account, such as a reference, amount status or receipt time. We use those details to check account records, not to request your wallet password.

Yes. Send a correction request through the account support route and identify the affected detail. We may ask for phone verification or another account check before changing data connected with access or payment matching.

We may record browser type, device signals, language settings and sign-in events to protect account pages and identify unusual activity. You can review browser cookie controls, while security records may remain for the stated retention period.

We retain payment and account records while they are needed for service operation, dispute handling, security checks or legal duties. When the period ends, we remove or de-identify the records under our retention practice.

Use the support route connected to your account and state whether your request concerns account data, a wallet reference, cookies, device access or retention. Include only the details needed to identify the issue safely.

The policy explains data handling during account access, but eligibility itself depends on local law. We may use verification and security records to protect the account where local law permits access to the service.