Reference

808ball Privacy Policy For Your Account

Our Privacy Policy explains how 808ball handles the details you provide when opening an account, checking your wallet status, or entering the lobby from a phone or desktop.

Clear data purposesWallet record careAccount access choicesCookie controls
808ball 808ball Privacy Policy For Your Account
CONTACT ROUTE

Get Privacy Policy Help Near Wallet Support

A clear contact path matters when a Privacy Policy question concerns your login, device record, or payment reference.

Account data request Ask us which personal details are connected to your account and why we use them. Include your account identifier so we can verify ownership before sending a response or making a record change.
Wallet record question For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, send the payment date and reference shown in your account. We use that limited context to trace status without requesting private wallet credentials.
Security concern If your login, verification step, or device access looks unfamiliar, contact support through the account area promptly. We may ask ownership questions before changing access details, helping keep the account history tied to you.
DATA HANDLING

What We Do With Your Account Details

Privacy Policy decisions affect the whole account journey, from the first phone verification to a later request about a wallet status or device session.

Collection at account opening

We collect the contact and verification details needed to create your account and confirm that a request comes from you. A clear phone verification step helps us connect later login or wallet questions to the correct account.

Device and cookie signals

Your browser or mobile device can send session, language, and security signals when you open the lobby. Cookies help maintain access and remember security choices; you can manage them through your browser settings, though some account functions may then need another check.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference helps us match a wallet event with your account. We use the reference and status, not your private wallet password, when investigating a receipt or delayed update.

Account protection

We use verification steps, session controls, and access records to identify unusual login activity. Never send us your password or one-time code. If a device path looks unfamiliar, we may pause a change until account ownership is confirmed.

Retention and removal

We keep personal records only as long as needed for the stated purpose, account security, dispute handling, or a legal duty. When a valid removal request is accepted, we delete or separate data that no longer needs to remain linked to your account.

Correction requests

You can ask us to correct inaccurate contact or verification details through the support route in your account area. We may request matching account facts before changing the record, then keep a short change history to protect against unauthorised edits.

Privacy Policy Answers For 808ball Accounts

These Privacy Policy answers address the searches we expect before you open an account or ask about a stored record. They explain what we collect, how wallet references are used, what happens on mobile devices, and how to contact us. If your question involves a location or eligibility rule, access depends on local law.

The 808ball Privacy Policy covers account details, phone verification, device and cookie signals, payment references, support records, and security logs. It explains why we use each category, how long records may remain, and how you can request access, correction, or removal.

Yes. Our Privacy Policy covers the payment reference, status, date, and account link connected with DANA, OVO, GoPay, or QRIS activity. We use those details to match a wallet event or receipt question, and we do not ask for your private wallet password.

A clear phone verification step connects your contact detail with the account before full access. If you ask us to change access data or investigate an unfamiliar session, we may ask matching account facts under the Privacy Policy before completing that request.

When you use a phone or tablet, we may receive session, browser, language, and security signals needed for account access. The Privacy Policy treats these as device data, while cookie choices remain available through your browser settings and may affect how sessions work.

We retain each record for the time needed for its purpose, account security, payment disputes, or a legal duty. The Privacy Policy does not set one period for every category. You can ask support which retention reason applies to a particular account record.

Use the support contact shown inside your account area and state whether you want access to a record or correction of a detail. Include your account identifier and the affected date where possible. We verify ownership before sharing or changing personal data.

You can submit a removal request through the account support path. We assess it under the Privacy Policy and may retain limited records for security, unresolved payment questions, disputes, or legal requirements. We will explain if any data must remain and why.