Reference

botak123 Privacy Policy And Your Data

botak123 Privacy Policy explains what we collect when you open an account, verify your phone, use DANA or QRIS, and browse from a mobile device.

Account dataWallet recordsCookie choicesPrivacy requests
botak123 botak123 Privacy Policy And Your Data
CONTACT PATHS

Privacy Help Beside Account Support

A clear contact route helps you ask about the Privacy Policy without explaining your concern twice.

Account access If your phone verification or sign-in stalls, contact account support through the available site support channel. We use the account details you provide to locate the right record, and we do not need your password to assess an access request.
Wallet privacy For a DANA, OVO, GoPay or QRIS record, tell us the date, amount reference and wallet status shown in your account. We use those details to trace the relevant transaction without asking you to disclose a wallet PIN.
Data request To ask about access, correction or removal of personal data, send the request through our site contact route with your registered contact detail. We may ask for an account check before changing records, subject to duties that depend on local law.
DATA PRACTICES

Six Ways We Handle Privacy

Privacy work is part of the account flow, not a separate promise hidden from the cashier page.

Account creation

When you open an account, we collect the contact details needed to create and maintain that account. Phone verification confirms control of the contact route before access, while the Privacy Policy explains how those records support sign-in and account protection.

Device signals

A mobile browser or desktop session can provide device, browser, language and connection signals. We use these details to recognise unusual sign-in patterns, keep a session working and investigate access concerns without treating them as your wallet credentials.

Cookie choices

Cookies help remember session settings and measure how privacy pages are reached. You can manage cookies through your browser controls, although restricting them may require another sign-in or affect the way account pages remember your selections.

Wallet references

For DANA, QRIS, bank transfer and virtual account activity, we retain references such as status, time and account association rather than requesting your wallet PIN. These records help us answer a receipt question or investigate a mismatched cashier result.

Retention period

We retain personal data only while it supports account operation, security checks, a requested response or a legal duty. When a record is no longer needed for those purposes, we remove it or keep it only in a form that no longer identifies you.

Change requests

You can ask us to correct inaccurate account details or explain a stored record through the site contact route. We verify the request against the account, describe any lawful reason for keeping data and apply changes where local law permits.

Privacy Policy Answers For botak123

These Privacy Policy answers address the searches we expect before you open an account from Indonesia. Each response stays focused on personal data, device access, cookies, wallet references and contact steps. If your question concerns a specific record, include the registered contact detail and the relevant date so we can direct the request accurately where local law permits.

The botak123 Privacy Policy explains how we collect and use account, phone verification, device, cookie and wallet-reference data. It also describes retention, security checks, correction requests and contact routes, so you can understand the account records connected with your activity.

It covers details you submit for an account, such as your contact route and verification record, together with device and browser signals from sign-in sessions. Where a wallet is used, we may keep transaction references and status information linked to your account.

We do not need your DANA or QRIS PIN to check an account-linked wallet record. We use details such as the payment reference, time and status to investigate a cashier question, while the payment credential remains with the relevant payment service.

Send a data-access request through the site contact route and include the contact detail registered to your account. We may complete an account check before responding, because the request can contain private records and access depends on local law.

Yes. Tell us which account detail is inaccurate and what the corrected value should be through the site contact route. We compare the request with the account record, apply an eligible correction and explain any restriction required by local law.

We keep data while it is needed for account access, security review, a privacy response or a legal obligation. After that period, we remove it or make it non-identifying where appropriate. The exact period can depend on the record and local law.

Cookies can remember session settings and help us understand visits to privacy and account pages. Browser controls let you restrict them, but doing so may require another sign-in or prevent selected settings from being remembered during your next session.