Reference

mbs388 Privacy Policy for Your Account

The mbs388 Privacy Policy explains how we handle your account details, device data, wallet references and support messages when you use our site.

Account dataWallet referencesCookie choicesRequest support
mbs388 mbs388 Privacy Policy for Your Account
PRIVACY HELP PATH

Get Help With a Policy Request

A direct privacy question should not be mixed with a general lobby question, so we keep the request focused on your account record, device activity or payment reference. Tell us the phone number linked to the account, the issue you want checked and the date or transaction reference involved. We use that context to locate the right record without asking you to send a password or wallet PIN. Account access and eligibility remain subject to local law.

Team online

Account data request

Ask us to confirm what account information is associated with your verified phone number. Include the email or phone path you used, but never send a password, one-time code or wallet PIN. We may request reasonable proof that the request concerns your account.

Payment reference check

If a DANA, OVO, GoPay or QRIS reference appears incorrect, share the date, amount reference and displayed status through our support path. We use the reference to investigate payment records, while wallet credentials remain private and should not be included.

Access and correction

For a correction request, describe the field that needs changing and the accurate replacement. We can explain whether the update affects phone verification or account access. Requests about availability are handled with the wording where local law permits, because eligibility can vary by location.

HANDLING YOUR RECORD

How mbs388 Handles Privacy Details

Privacy work starts with separating account identity from the payment status needed for a transaction check.

Account information

We collect details you enter for account creation and phone verification, along with messages you send for help. These details let us identify the correct account and answer a privacy request. We do not need your wallet PIN to investigate a DANA or QRIS status.

Payment records

A payment check can contain a method name such as OVO, GoPay, bank transfer or virtual account, plus a reference and status. We use those fields to reconcile the account activity shown to you. The policy does not give us control of your external wallet.

Cookies and devices

When you move from login to a mobile lobby or use a desktop browser, technical data may record session, browser and device events. Cookies can preserve essential access settings or support measurement. You can manage cookie behaviour through browser controls, although some site functions may change.

Security checks

Phone verification, session controls and device signals help us identify unusual access. If a request involves a changed phone number or unfamiliar device, we may ask for additional account proof. Do not share passwords, one-time codes or payment credentials with anyone claiming to act for us.

Retention periods

We retain records for as long as they support account security, payment reconciliation, dispute handling or a legal requirement. A closed account may therefore leave limited transaction or support records for a period. When the reason for keeping data ends, we remove or anonymise it where applicable.

Your requests

You can ask what personal data we hold, request a correction or ask how a record is used. Include enough account context for us to verify the request, while keeping sensitive credentials out of the message. We explain any restriction when a request conflicts with security or legal duties.

Privacy Policy Questions for Indonesia

These answers address the searches we hear most often about the mbs388 Privacy Policy. They explain what we collect during account access, why payment references appear, how cookies behave on mobile devices and how to request a correction. If your question concerns eligibility or access, the answer depends on local law and applies where local law permits.

The mbs388 Privacy Policy covers account details, phone verification, device and session data, cookie use, support messages and payment references. It explains why we use each category, how we protect access, when records may be retained and how you can ask for access or correction.

No. Our payment records may show DANA or QRIS as the selected method, together with a transaction reference and status. You should never send us a wallet PIN, password or one-time code. We use the available reference to check account reconciliation without requesting wallet credentials.

Device and browser signals help us keep sessions secure when you sign in from a mobile browser or desktop. They can show session activity, browser type and unusual access patterns. We use this information for security and service operation, not as permission to read private content on your device.

Send a focused request through our support path with the phone number or account route linked to you and explain the records you want checked. We may ask for reasonable proof before releasing details. Leave out passwords, wallet PINs and one-time codes from every request.

Yes. Describe the incorrect field, provide the accurate replacement and explain which account it belongs to. We verify the request before changing information, especially when it affects phone verification or payment matching. Some records may need to remain unchanged for security, dispute or legal reasons.

We keep payment references and related account records while they support reconciliation, security checks, dispute handling or a legal requirement. The exact period depends on the purpose and applicable rules. Once the reason ends, we remove or anonymise the information where applicable.

It applies to our handling of data when you use the site in Indonesia, where local law permits. Account availability and eligibility depend on local law. If you are unsure how a local requirement affects your request, contact us with the account context and we will explain the relevant process.