Reference

Privacy Policy for ban388 Accounts

Our Privacy Policy explains how we handle the details connected to your ban388 account, from phone verification and mobile sign-in to wallet status for DANA, OVO, GoPay and…

Account dataWallet checksCookie choicesPhone verification
Browse Our Lobby Read FAQ
ban388 Privacy Policy for ban388 Accounts
PRIVACY CONTACT ROUTES

Get Help With a Policy Request

A clear contact route helps you ask what data is attached to your account or request a correction without guessing which payment page to use.

Account privacy request Send your request through the account support path and identify the phone or email used for sign-in. We may ask for an account step that confirms you are asking about your own data before discussing stored details.
Wallet record question For a DANA, OVO, GoPay, QRIS, virtual account or bank transfer question, include the payment reference and date shown in your receipt. We use that reference to separate wallet status from unrelated account activity.
Policy access issue If the Privacy Policy page or your account support route does not load on mobile, try the same page from your device browser and send the account contact details shown there. We use the submitted path to trace the access issue.
DATA HANDLING DETAILS

What We Do With Account Signals

We separate the data needed for account access from the records used to check a wallet request.

Account identity

We use the phone or email connected with your account to support sign-in checks and privacy requests. If those details change, ask us to update the record through the account support path so the request is matched correctly.

Mobile cookies

Cookies and similar browser storage can keep session settings working when you move from sign-in to the lobby on a phone. Clearing them may remove remembered settings, so you may need to complete the account access step again.

Wallet matching

A DANA, OVO, GoPay or QRIS reference is used to match a payment status with the account request that created it. Bank transfer and virtual account references follow the same matching purpose rather than becoming public profile content.

Account security

Phone verification and session checks help us distinguish an account holder from an unverified sign-in attempt. We may request a further account confirmation before discussing personal records, wallet references or a requested data change.

Retention period

We retain account, payment and support records only for the period needed for the stated account, payment, security or legal purpose. The applicable period can differ by record type and may depend on local law.

Change request

You can ask us to correct eligible account details, explain a stored record or address a deletion request through the account support path. Include the affected field and your connected contact detail so we can assess the request.

Privacy Policy Answers for Your Account

These Privacy Policy answers address the questions we expect before you open an account or send a wallet-related request. Each answer stays tied to ban388 account data, browser access, payment references and contact steps. If your situation is not covered, use the account support path and include enough detail for us to locate the correct record.

The ban388 Privacy Policy covers account contact details, phone verification, device and cookie signals, payment references, support messages, retention and requests to change eligible records. It applies when you use the account path, wallet status pages or the mobile browser route where local law permits.

Phone verification helps connect a sign-in attempt with the correct account and supports a safer response to a privacy request. If you ask about DANA, OVO, GoPay or QRIS records, we may use the verified account contact to check that the request belongs to you.

Yes. The Privacy Policy covers payment references and status details connected with DANA, OVO, GoPay and QRIS. For bank transfer or virtual account records, we may also retain the reference, date and bank context needed to match the request with your account.

Use the account support path and state which detail appears incorrect, such as a phone number, email address or wallet reference. Include the contact detail connected with your account. We may request an account confirmation before changing or disclosing the record.

Mobile cookies and browser storage can keep required session settings available between sign-in and the lobby. Clearing them may remove those settings and require another account access step. The Privacy Policy explains their purpose, while your browser controls whether they remain stored.

We keep each record for the period needed for its account, payment, security, support or legal purpose. Account data, wallet references and support messages may follow different periods. The applicable retention approach depends on local law and the nature of the record.

You can ask through the account support path which categories of data are connected with your account and why they are used. We assess the request against account security and local requirements, then respond through the contact detail used to verify your request.

Related Pages

ban388 Indonesia ban388 Casino Access guide Account information About Us