Reference

buat123 Privacy Policy For Your Account

Our Privacy Policy explains how buat123 handles the details you provide when opening an account, checking wallet status or entering the lobby.

Clear data purposesWallet reference handlingAccount access controlsPrivacy contact route
buat123 buat123 Privacy Policy For Your Account
HELP WITH PRIVACY

Get Privacy Policy Help Before Access

A direct support route helps you deal with a privacy question before you continue from login to the lobby. Tell us whether your request concerns account access, a wallet reference, a device record or a correction to personal details. Include the email or phone connected with your account, but do not send a password or full payment credentials. We use the account trail to locate the right record and explain the next step. If you are in Semarang or elsewhere in Indonesia, the same request path applies where local law permits.

Team online

Account privacy request

Ask us to explain, correct or locate personal details linked with your buat123 account. We may request an account check before discussing the record, so your information is not disclosed to someone using another device.

Wallet reference question

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the transaction date and visible reference only. We can compare the account trail and payment status without asking you to share a wallet PIN or full credential.

Access and security concern

Report a login event or device change that you do not recognise through our account help route. We can review the access trail, explain the security step and point you to the Privacy Policy section that applies.

HOW WE HANDLE DATA

Privacy Controls Behind Your Account Path

Privacy work is part of the account path, not a separate promise shown after a transaction.

Account details

We use details such as your contact data and verification result to create, secure and maintain your account.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references can identify a transaction status.

Cookies and device signals

Cookies and device signals can help keep a login session working and identify unusual access.

Security checks

Phone verification can be required before account access or a sensitive change.

Retention choices

We keep account and transaction records while they support service operation, security review or legal duties.

Policy contact

You can ask about your stored data, request a correction or question a device or payment record through our support…

Privacy Policy Answers For buat123

These Privacy Policy answers address the account questions you are most likely to have before opening or using buat123 from Indonesia. We focus on the details that affect a real account path: what we collect, why wallet references appear, how device access is handled and how you can ask for a change. If your situation is not covered, use the support route with a limited account reference rather than sending secret credentials.

The buat123 Privacy Policy covers account details, phone verification, login events, device signals, cookies, payment references, retention and privacy requests. It applies to the account path from registration through lobby access, including sessions used on a phone or desktop browser.

DANA, OVO, GoPay and QRIS appear because their transaction references can help us match a deposit or status question to your account. We use those references for reconciliation and support, not to request your wallet PIN or unrestricted wallet access.

Yes, you can ask what personal details are linked with your account or request a correction through our support path. We may verify your account first, then explain what can be supplied or changed under applicable requirements and local law.

Phone verification can confirm that the person requesting account access or a sensitive change controls the connected account route. We record the verification result for security and account handling, while limiting discussion of private details until the check is complete.

We may keep cookie and device signals that help maintain a login session, detect unusual access or protect an account. The Privacy Policy limits their use to stated operational, security and legal purposes, with retention ending when the record is no longer needed.

Retention depends on why the record exists. Account, payment and security records may remain while needed for operation, dispute handling, fraud prevention or legal duties. When that purpose ends, we remove or anonymise the record through our retention process.

Use our account support route and state that your request concerns the Privacy Policy. Provide your connected email or phone and a short description, such as a correction or wallet reference question. Do not include passwords, wallet PINs or complete payment credentials.