Reference

Open with zk899 Privacy Policy clarity

zk899 Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the mobile lobby and live tables.

Account dataWallet recordsCookie choicesSecurity steps
zk899 Open with zk899 Privacy Policy clarity
CONTACT ROUTES

Contact us about Privacy Policy access

A clear contact path helps you ask what we hold, why we use it or how to correct an account detail. Start from the support route connected to your account and include the email or phone detail linked to your profile, without sending a wallet password. We will use the available account checks to reduce mistaken requests and keep a record of the conversation.

Team online

Policy questions

Ask about the zk899 Privacy Policy through the account support route. Include the subject of your request and the email or phone detail tied to your account so we can locate the correct record.

Wallet records

For a DANA, OVO, GoPay or QRIS question, attach the payment reference rather than your wallet password. This lets us trace status details while limiting the sensitive data included in your support request.

Access changes

If your phone verification or login path blocks a privacy request, tell us which device you used and where the step stopped. We can direct the request toward the account and cashier support path.

DATA CONTROLS

Check your data controls and security

Privacy choices work best when each account step has a clear reason. We separate account details, payment references, device signals and support messages so requests can be handled with the right context.

Account details

We collect details needed to create and maintain your account, including contact data used for phone verification. We use those details to confirm account access, respond to policy requests and connect the right person with the right account record.

Payment references

A DANA, OVO, GoPay or QRIS transaction can create a reference, amount, timestamp and status record. Bank transfer and virtual account details may be matched with cashier activity so deposits and withdrawals can be checked.

Device signals

When you move from mobile login to the lobby, we may receive device and browser signals used for session security. These signals help us identify unusual access without treating your phone model as a public profile.

Cookies

Cookies can keep a session active, remember selected settings and help us understand whether a page loads correctly. You can manage cookie controls in your browser, although removing some cookies may interrupt account access or policy preferences.

Retention

We retain account, payment and support records only for the period needed for service operation, dispute handling, security checks or legal duties. A deletion request may not remove records that must remain for those specific purposes.

Your request

You can ask us to access, correct or clarify personal data through the account support route. Include your account contact detail and request type; we may complete a phone verification step before discussing private records.

Find zk899 Privacy Policy answers

These Privacy Policy answers address the account and payment questions we expect you to ask before opening access. Each response stays close to an actual step, from phone verification and mobile sessions to DANA records and requests for data changes. If your situation is not covered, use the support route attached to your account.

The zk899 Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages, payment references and retention. It also explains how to ask for access or correction, with access depending on local law and any records we must keep.

We record payment references, timestamps and status so a DANA, OVO, GoPay or QRIS transaction can be matched to the correct account. We may also use bank transfer or virtual account records to reconcile deposits and verify withdrawal requests.

Yes. The Privacy Policy covers device and browser signals connected with a mobile or desktop session. We use them for session security and troubleshooting, such as checking where a phone verification step stopped, rather than displaying your device details publicly.

Use the support route shown inside your account and ask for a data access request. Include the email or phone detail linked to the account, then complete any identity check we request. We handle the request where local law permits.

You can request a correction when an account detail is inaccurate or out of date. Send the requested change through account support and identify the affected field. We may ask for phone verification before changing contact or payment-linked records.

We keep records for the time needed to operate the account, match payment status, investigate disputes, protect sessions or meet legal duties. A deletion request may therefore exclude transaction or support records that still serve one of those purposes.

Ask through the account support route if you need help with cookie choices or a session affected by browser settings. Cookies may remember login preferences and page settings; removing them can interrupt access, while access remains where local law permits.