Reference

vsbdt Privacy Policy for Indonesian Accounts

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

Account clarityWallet recordsDevice choicesContact route
vsbdt vsbdt Privacy Policy for Indonesian Accounts
HELP WITH PRIVACY

Get Clear Answers About Your Data

Our support path is designed to keep privacy questions close to the account details they concern.

Account privacy request Use the support route linked to your account when you want to ask what personal details we hold, why they are used, or which account step created the record. We may ask for account confirmation before discussing private details.
Wallet record question For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, share the payment reference and date rather than your secret credentials. We use those details to locate the relevant record without asking for your wallet PIN.
Access or correction help If your phone verification details are outdated or you cannot reach the privacy page from mobile, contact support from the account path. We will explain the identity check and the next step for correcting or accessing your data.
DATA CONTROL DETAILS

What You Can Check And Change

We apply this Privacy Policy to the information created through your account, wallet requests and visits from supported devices.

Data we receive

We may receive your account contact details, phone verification result, login events, device and browser signals, support messages, and payment references. A DANA or QRIS reference helps us match a wallet event, while it does not reveal your private wallet PIN.

Why we use it

We use account data to provide access, confirm a requested wallet action, answer a support question, detect unusual login behaviour and maintain service records. We do not turn a privacy request into a general account message; each request stays tied to its stated purpose.

Cookies and device signals

Cookies and similar device signals can help keep a signed-in session working, remember a security choice and show whether a browser has changed. You can manage browser cookies, although removing them may require another phone verification step when you return.

Account security

Phone verification comes before account access, and login events can be checked when a device or location changes. Keep your password and wallet PIN private, and contact us if a login alert or payment record does not match your own activity.

Retention of records

We retain account, support and payment records only for the service, security and legal purposes that apply to them. Retention can differ by record type and local requirement, so support can explain the applicable request path without promising an immediate deletion.

Your request route

You can ask to access, correct or clarify personal data through support. Include the account contact and the specific record, such as a phone verification detail or GoPay reference. We may verify ownership before releasing or changing information.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we expect from someone checking vsbdt before opening an account. They cover the data connected with login, mobile browsing, local wallets and payment records without replacing the full policy text. Where a request depends on location or a legal requirement, we will explain the available route after confirming the account details you provide.

The vsbdt Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages, and wallet or bank payment references. It explains why we use those records, how we protect them, how long handling may continue, and how you can ask for access or correction.

We use phone verification before account access to confirm that the contact route belongs to you and to reduce mistaken or suspicious entry. The verification result becomes an account security record. If your number changes, contact support so we can explain the correction steps.

Yes. The Privacy Policy covers payment references and status details created when you use DANA, OVO, GoPay or QRIS, as well as bank transfer and virtual account records. We use these details to match a requested transaction and answer receipt questions, not to request your wallet PIN.

We may record device type, browser signals, login time and security events connected with your account session. These details help us identify unusual access and keep the mobile path working. You can manage cookies in your browser, though doing so may trigger another account check.

Contact support through the account route and state that you are making a personal data request. Name the record you want, such as your phone verification detail, login event or QRIS reference. We may confirm account ownership before explaining, providing or correcting the requested data.

You can ask us to correct inaccurate account details or clarify whether a record can be removed. We assess the request against service, security and legal retention needs, so deletion is not automatic. Where local law permits, support will explain the available result and next step.

Yes. Privacy rights, retention duties and account eligibility can vary by location, so access depends on local law. We use the policy page to explain our general handling, then support can confirm the route relevant to your account and the Indonesian payment record you mention.