Reference

Privacy Policy For Your bakso108 Account

Your account details, wallet records and device choices are explained clearly in the bakso108 Privacy Policy, so you can decide what to share before opening an account.

Account clarityWallet recordsCookie choicesPhone verification
bakso108 Privacy Policy For Your bakso108 Account
PRIVACY HELP ROUTES

Reach Us About Your Privacy Policy

A clear contact path matters when a name, phone number or wallet reference needs attention.

Account support Open the support route from your signed-in account when you want to ask about the Privacy Policy, stored profile details or phone verification. Include the email or phone linked to your account, but never send a password, wallet PIN or one-time security code in your message.
Cashier questions For a DANA, OVO, GoPay or QRIS reference, use the cashier-linked support path and share the transaction date, amount and reference shown on your receipt. We use those details to locate the relevant record while limiting the personal data included in the request.
Correction requests If your profile name, phone number or contact detail is incorrect, tell us which field needs changing and why. We may request an account step or verification response before making the update, helping us avoid changing information for the wrong person.
DATA HANDLING DETAILS

How We Handle Login And Device Data

Privacy is easier to assess when each data use has a practical reason. We record the account actions needed to provide sign-in, cashier checks and access to the lobby, while cookie settings…

Account records

We use your name, phone number and account identifiers to create and maintain your account, complete the clear phone verification step and connect account activity with the correct profile. We do not need your wallet PIN to identify a DANA, OVO, GoPay or QRIS payment reference.

Payment references

Cashier records can include a payment rail, reference, amount, time and account link. Those details help us check whether a bank transfer, virtual account or QRIS entry belongs to your account. The Privacy Policy separates transaction references from sensitive wallet credentials.

Cookies on devices

Cookies can keep a session active, remember consent and support basic navigation between login, the lobby and cashier. You can adjust cookie behaviour in your browser settings, although some account paths may not work as intended when essential cookies are blocked.

Login protection

We use sign-in details, device signals and account events to help identify unusual access patterns. If a new phone or browser triggers an account check, follow the requested verification step and contact support through the signed-in route if the prompt does not match your activity.

Retention approach

We keep personal and payment records for as long as needed for the purposes described in the Privacy Policy, account support, dispute handling and applicable legal duties. When a record is no longer needed, we remove it or reduce its link to you where appropriate.

Policy requests

You can ask what personal data we hold, request a correction or raise a deletion question through our on-site support channel. We may verify account ownership before responding, and some records may remain where keeping them is required for a documented operational or legal reason.

Privacy Policy Answers For bakso108

These Privacy Policy answers address the account and payment questions we hear most often before registration. We keep the wording practical: what is collected, why it is used, how you can request a change and what happens when a phone, browser or wallet reference needs checking. For a matter specific to your account, use the signed-in support route.

The bakso108 Privacy Policy explains how we collect, use, store and protect account, device, cookie and payment-reference data. It also describes your request options, our contact path and the checks we may use before changing information linked to your account.

It covers details such as your name, phone number, account identifiers, sign-in events and phone verification status. We use these details to maintain the correct account and respond to support requests, rather than asking you to send passwords or wallet PINs.

We may store payment references connected with DANA, OVO, GoPay or QRIS, including a reference, amount, time and account link. The Privacy Policy concerns these records; it does not ask you to provide a wallet PIN or one-time security code.

Cookies can remember consent, support sign-in sessions and help the path between your account, lobby and cashier work correctly. You can change cookie settings in your browser. Blocking essential cookies may prevent some account functions from operating as intended.

Yes. Use the on-site support channel to ask what personal data we hold or to identify a field that needs correction. We may confirm your account phone number or another account step first, then assess the request under the Privacy Policy.

We retain account, support and payment-reference records only for the period needed for the purposes described in the Privacy Policy, dispute handling and applicable legal duties. When continued storage is not needed, we remove or reduce the link to your account where appropriate.

The policy can be read as our explanation of data handling, but account access and eligibility depend on local law. If you need help applying a policy request to your account in Indonesia, contact us through the signed-in support route.