Reference

barunatoto Privacy Policy For Your Account

Our Privacy Policy explains how barunatoto handles the details you provide when opening an account, checking your phone, and using DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesPolicy requests
barunatoto barunatoto Privacy Policy For Your Account
CONTACT THE DESK

Privacy Policy Help Through Your Account

A clear contact path helps you ask about the Privacy Policy without sending sensitive details through an unrelated route. Start from your signed-in account support path and describe the request, such as a data copy, correction or question about a wallet record. We may ask you to complete phone verification before discussing account-linked details. If you are in Yogyakarta, use the same account route; location does not change the request steps where local law permits.

Team online

Account support path

Open support from your signed-in account and select a Privacy Policy question. We use the account context to locate your request, while you should avoid placing a password, wallet PIN or full payment credentials in the message.

Data request check

For a copy, correction or removal request, tell us which account detail is involved and provide a reachable contact route. Phone verification may be required before we act, so another person cannot change your record through a casual message.

Wallet record query

If your question concerns DANA, OVO, GoPay or QRIS activity, include the visible reference and date rather than secret wallet credentials. We compare the reference with our account record and reply through the support path connected to your account.

DATA HANDLING

What barunatoto Keeps And Why

We separate ordinary account operation from the controls used to protect your sign-in and payment references.

Account details

We may hold the name, contact route and account identifiers you enter during account creation. Phone verification helps connect a real account step to that record. We use these details for account access, support replies and policy-related requests, not for unrelated purposes.

Device and session data

Your browser can send session, device and sign-in signals when you move from login to the lobby. These records help us recognise unusual access and keep the account path working on Android or desktop without asking you to share device passwords.

Cookies on your browser

Cookies can remember a session, support security checks and record your selected page settings. You can manage cookies through your browser controls, although blocking some types may interrupt the sign-in path or require another verification step.

Payment references

When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we may store a reference, amount status and processing trail. We do not ask you to place wallet PINs or full banking secrets into a support message.

Retention and deletion

We retain account and transaction records for as long as needed to operate the account, answer disputes, protect against misuse or meet a legal requirement. A deletion request does not erase records that must remain for those purposes.

Changes and contact

To request correction, access or another policy change, contact us through the signed-in account support path. We may verify your phone before replying. We will place material Privacy Policy changes on this page with a new effective date.

Privacy Policy Questions About barunatoto

These answers address the Privacy Policy questions you are most likely to have before opening or using an account. We keep the route practical: check the policy page, use your account support path and complete phone verification when a request concerns private account records. Where access or eligibility is discussed, it depends on local law.

The barunatoto Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, support messages and payment references. It explains why we use each category, how we protect account access and how you can request a copy, correction or removal where local law permits.

Phone verification connects an account step to the person requesting access or a data change. We may use it before discussing private records or changing contact details. This check helps prevent another person from using a casual support message to access your account information.

Yes. The Privacy Policy covers references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These records help us match a payment event to the correct account and handle a support question without requesting your wallet PIN.

Use the support path inside your signed-in account and state that you are making a data access request. Identify the account detail or record you want reviewed. We may ask for phone verification before releasing account-linked data, subject to local law.

You can request a correction through signed-in account support. Tell us which detail is inaccurate and provide the updated value without sharing a password or wallet PIN. We may verify your phone and may retain the earlier record when a legal or dispute purpose requires it.

We keep records for the period needed to provide account access, answer disputes, detect misuse or meet a legal obligation. The exact period can differ by record type. A deletion request may therefore remove some data while transaction or security records remain.

This Privacy Policy page is where we publish material changes and their effective date. Check it before opening an account and after a policy update. If a change affects your account request, contact signed-in support so we can explain the relevant section.