Reference

Privacy Policy for Your baru01 apk Account

baru01 apk Privacy Policy explains how we use the account, device and wallet details you provide when you access our lobby from Indonesia.

Account clarityWallet referencesMobile accessPrivacy requests
baru01 apk Privacy Policy for Your baru01 apk Account
PRIVACY CONTACT

Get Privacy Help Beside Login

A clear contact path matters when a name, phone number or wallet reference needs attention. Our account support route is the place to ask about the Privacy Policy, request a copy of data connected with your account or report a concern about an access record. Include your account identifier and the subject of your request, but never send a wallet password or one-time code. We use the details in your message only to locate the relevant record and respond to the privacy issue.

Team online

Account access

If login stalls after your phone verification, contact our account support route and state that your request concerns the Privacy Policy. We can check the account record, explain which details are held and direct you through the appropriate identity check without asking for your DANA or OVO password.

Wallet record

For a DANA, GoPay or QRIS reference that appears incorrectly, send the account identifier and transaction reference through support. We compare the stored status with the relevant account event, explain the result and keep the request limited to the payment record needed for your privacy question.

Data request

To ask for access, correction or removal of eligible personal data, identify the account and describe the requested change. We may ask for a matching account step before acting, because a privacy response must go to the person connected with the record.

DATA CONTROLS

Account Security Across Mobile Devices

We apply the Privacy Policy at each point where account data moves through the service: account creation, phone verification, login, wallet status checks and support contact.

Account details

We use the name, phone contact and account credentials you submit to create and maintain your account. Phone verification confirms that an access request relates to the contact supplied. The Privacy Policy does not give us permission to use those details for an unrelated purpose.

Device signals

When you open the lobby on a phone or desktop browser, technical signals such as browser type, session time and approximate connection details may be recorded. We use them to protect login activity, troubleshoot access and understand whether a request is genuine.

Cookies

Cookies can keep a session active, remember a selected language or help us understand whether a page request completed. You can manage cookies through your browser settings, although turning them off may affect login, account steps or the display of the Privacy Policy.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account event may leave a reference and status connected with your account. We use those fields to reconcile the request and answer payment-related privacy questions, not to collect your wallet password.

Retention

We keep personal data while it is needed for account access, security checks, transaction reconciliation or an active privacy request. When a record no longer serves one of those purposes, our handling follows the retention requirements that apply where local law permits.

Your request

You can contact us to ask what account data we hold, request a correction or ask whether deletion is available. We may verify ownership through an account step before responding, and we explain any limit when a record must remain for security or legal reasons.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we hear around baru01 apk account access in Indonesia. They explain the practical points that matter before you submit a phone number, open the mobile lobby or connect a local wallet. If your question is not covered, use the privacy contact path with your account identifier and a short description. Please leave passwords, verification codes and full wallet credentials out of every message.

It covers account details, phone verification, login activity, device signals, cookies, payment references and messages sent to support. It also explains why we use each category, how retention works and how you can ask about access, correction or removal where local law permits.

No. For DANA and QRIS activity, we use a transaction reference and status connected with your account request. Do not send a wallet password or one-time code to us. The Privacy Policy describes these limited payment records and their account-support purpose.

Device and browser signals help us recognise a normal mobile login, investigate an unusual access attempt and diagnose a page problem. The Privacy Policy limits that use to account operation and security needs; it does not turn those signals into a separate personal profile.

Contact our account support route and state that you are making a Privacy Policy data request. Include your account identifier and the categories you want to ask about. We may complete an ownership check before explaining which records can be provided.

Yes. Send the account identifier, identify the incorrect field and describe the correction you need. We may ask you to complete a matching account step before changing a phone contact, name or wallet reference, so the Privacy Policy request stays linked to the right account.

We retain payment references and status details while they support account security, transaction reconciliation or an active privacy request. The period can depend on the record and applicable requirements. We remove or stop using data when the stated purpose and required retention period end.

Yes, the policy explains our handling for Indonesian account access, including mobile sessions and local wallet references from DANA, OVO, GoPay and QRIS. Account availability depends on local law. If your location or eligibility is unclear, contact support before submitting personal data.