Reference

Privacy Policy For Your os911 Account

The os911 Privacy Policy explains what we collect when you open an account, check DANA or QRIS status, and move between the mobile lobby and casino tables.

Account accessWallet checksCookie choicesPolicy requests
os911 Privacy Policy For Your os911 Account
CONTACT ROUTES

Get Help With A Privacy Request

A clear contact route helps you resolve a privacy question without repeating your account history.

Account contact Use the account support channel when you need to access, correct, or remove personal…
Payment evidence For a wallet or bank-transfer question, share the transaction reference, date, rail name, and…
Access assistance If a privacy request is blocked by login or phone verification, contact support with…
DATA HANDLING

How We Handle Account Information

Privacy choices should be understandable at the point where they affect your account. We separate identity checks, payment status, device activity, and lobby preferences so a request can target the right record.

Account records

When you open an account, we may store your name or contact details, phone verification result, login events, and messages sent to support. This lets us confirm which record a request concerns and explain an access issue without exposing another account’s information.

Payment status

A deposit or withdrawal check can include a rail, amount, timestamp, account reference, and processing status. We use this information to match receipts and investigate a stalled status. Wallet credentials and one-time security codes should remain with DANA, OVO, GoPay, or your bank.

Cookies

Essential cookies can keep your session active as you move from login to the lobby. Optional cookies may help us understand page loading and device behaviour. You can adjust cookie settings in your browser; changing them may require you to sign in again on the mobile path.

Device security

We record limited device and connection signals when needed to protect account access, detect unusual sign-in patterns, and keep phone verification consistent. We do not describe a device signal as your identity by itself. A support request can help when a familiar phone or browser is flagged.

Retention period

We keep personal information while it serves account access, payment reconciliation, security, support, or a legal requirement. When a record no longer has a valid purpose, we remove it or separate it from direct account details where practical. A deletion request may have lawful exceptions.

Your requests

You can ask for access, correction, deletion, restriction, or an explanation of processing where local law permits. We may verify the request through the registered phone or another account detail. Send one clear request at a time so we can answer the exact Privacy Policy issue you raised.

Privacy Policy Questions About os911

These answers cover the account and payment questions we hear most often about the os911 Privacy Policy. They explain what to send, what we use, and how access checks affect a request, without asking you to disclose a wallet password or security code.

The os911 Privacy Policy covers contact details, phone verification, login events, device signals, cookie choices, support messages, and payment status. We use them for account access, security, reconciliation, service communication, and legal needs where local law permits. You can request access or correction through support.

We do not need your wallet password or one-time security code to check a payment status. We may keep a transaction reference, rail name, timestamp, and result so we can match the account record. Send only visible receipt details when asking about DANA, OVO, GoPay, or QRIS.

Contact account support using the phone number or email attached to your account and ask for an access request under the Privacy Policy. Describe the records you need, such as login history, cookie choices, or payment status. We may verify account ownership before releasing information where local law permits.

You can ask us to correct inaccurate details or remove information where local law permits. Include the specific field or record, such as an old phone number or duplicated payment reference. We may retain information needed for security, payment reconciliation, disputes, or a legal requirement.

The Privacy Policy applies when you use a mobile browser or desktop browser to sign in and reach the lobby. We may process session, device, and connection signals to keep access secure. Essential cookies may be required for login, while optional cookie choices can be changed in your browser.

Send the bank name, transaction reference, date, account reference, and visible processing status. Do not send your banking password, PIN, or security code. We use those limited details to compare a bank transfer or virtual account record with your account and answer the Privacy Policy request accurately.

We may disclose limited information when needed for payment reconciliation, account security, support operations, or a lawful request. The details depend on the service involved and the applicable rule. We do not ask a payment provider to share your wallet password, and you can ask support what disclosure relates to your record.