Reference

MBET338 Privacy Policy For Your Account

Our MBET338 Privacy Policy shows how we use account details, phone verification data, device signals and wallet records when you access the service.

Account dataCookie choicesWallet recordsPhone verification

Explore Our Lobby Read FAQ

What We Collect Around Your Wallet

MBET338 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We collect the details needed to create and protect your account, such as your contact details, phone verification result, login events, device information and messages sent to support. When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we may receive payment status,

1
reference details and records needed to match the transaction to your account; we do not use those details to describe your private activity beyond the stated service purpose. Cookies and similar browser storage help keep a session open, remember selected settings and identify unusual login behaviour.
2
We use data to provide account access, check wallet status, respond to requests, prevent misuse and meet applicable obligations. Account access depends on local law, and we may limit processing where local law permits. We keep records only for as long as needed for these purposes
3
or an applicable retention period.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

REQUEST ROUTE

Get Help With A Privacy Request

A privacy request starts with the support path shown on your account or login screen, so we can connect the request to the correct account without asking you to post personal details…

Access request Ask us what account data we hold and how it is used. We may verify your phone or account details first, so the response reaches the right person.

Correction request Tell us which account field looks wrong, such as a phone detail or wallet reference. We will assess the request against the records linked to your account.

Wallet record help Include the DANA, OVO, GoPay or QRIS reference shown in your account when asking about payment data. This helps us locate the relevant status without broad disclosure.

SECURITY PRACTICE

How Your MBET338 Data Is Handled

We separate account access from privacy requests by checking the account details connected to the request before discussing personal records.

Account data use

We use contact details, phone verification and login records to create the account, protect access and respond to account requests. We do not need unrelated personal details for these steps.

Cookie controls

Cookies can keep your mobile browser session active and remember selected settings. You can clear browser storage through your device settings, though doing so may require another login.

Security signals

We examine sign-in time, device context and account activity when access looks unusual. A phone verification step may be requested before we discuss or change account data.

Retention approach

We retain account, support and wallet records for the period needed to provide the service, resolve disputes, protect access or meet applicable obligations, then assess them for removal.

Change requests

You can ask us to correct eligible details or explain how a record is used. Send the request through the account support path and identify the affected field clearly.

Privacy contact

For a Privacy Policy question, contact us through the support route displayed after login or beside the wallet status area. We may request account verification before sharing details.

Privacy Policy Questions Indonesian Accounts Ask

These Privacy Policy answers cover the account, device and payment questions we expect before you open access. They explain what to send, how checks work and where local law affects account data handling.

It covers account details, phone verification, login and device signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We may retain payment status, reference details and matching records needed for account support. The Privacy Policy does not mean we need unrelated wallet credentials, and requests can be sent through support.

Phone verification helps connect an account request to the correct account and helps protect access. We may ask for it before discussing stored data, changing details or resolving a wallet record.

Cookies can keep a mobile browser session active and remember settings. Clearing them through your device or browser may remove that session, so you might need to sign in again.

You can ask what eligible account data we hold and how it is used. Send the request through the account support route, and we may verify your phone or login details first.

Yes, you can identify an incorrect account field, phone detail or wallet reference and ask us to assess it. We will verify the request and update eligible records where appropriate.

Account access depends on local law. Where local law permits, we handle requests under the processes described here; applicable rules may affect retention, access or the response available to you.

MBET338 Privacy Policy For Your Account

Get Help With A Privacy Request

How Your MBET338 Data Is Handled

Account data use

Cookie controls

Security signals

Retention approach

Change requests

Privacy contact

Privacy Policy Questions Indonesian Accounts Ask

01 What does the MBET338 Privacy Policy cover?

02 Does MBET338 store my DANA or QRIS details?

03 Why does MBET338 ask for phone verification?

04 How do cookies affect my MBET338 account?

05 Can I request a copy of my account data?

06 Can I correct data in my Privacy Policy record?

07 Where does local law affect this Privacy Policy?

Related Pages