Our zk6 privacy introduction
Our zk6 Casino & Sportsbook Data Care for Mobile Payments
This page describes what we collect when you use zk6 and how we keep that data protected across Android install paths, iOS browser access, phone login, QRIS scan-and-pay top-ups, and account support requests. We write this policy for our casino, sportsbook, live-dealer tables, slot games, esports markets, and number-game areas. Our services are available only where local law permits.
We collect data only for account operation, payment verification, KYC review, security checks, customer support, and legal compliance. We handle details linked to e-wallet, mobile banking, local payment, online payment, e-wallet, mobile banking, local payment, online payment, e-wallet, and mobile banking so our cashier can show deposit records, match payment ownership, and review withdrawal requests.
We keep our mobile flow practical. We show Android users an install path from our site, we support iOS users through browser access, and we ask our users to keep a stable network before opening cashier pages. Our zk6 account login, payment history, help channel, and recovery checks are designed for phone use first.
Our zk6 data details for accounts and payments
We collect account details such as email address, username, phone number where provided, login records, device signals, and language preference. We use this data to open and maintain an account, support account recovery, reduce duplicate account issues, and answer help requests in available support languages.
We collect KYC details when our review process requires identity confirmation. Our review may include document images, name, date details shown on the document, address information where requested, and payment ownership proof. We use these records to match deposits, withdrawals, and account recovery cases. We do not ask our users to send wallet PINs, banking passwords, or one-time security codes.
We process payment data for e-wallet and virtual-account routes. Our cashier may record selected method, transaction reference, amount, status, provider response, and time stamp. We use those records when our users ask about DANAe-wallet, mobile banking, local payment, online payment, e-walletmobile bankinglocal payment, online payment, and e-wallet activity.
Our zk6 payment verification practice
We check payment ownership before withdrawal where our rules or processors require it. We may ask for a clearer receipt, a matching account name, or a corrected document when the first upload cannot be read. Our review does not promise a fixed completion time because bank, wallet, and internal verification windows can differ.
We use payment data to show balance changes, support deposit tracing, handle failed mobile banking scan results, and review withdrawal requests. We also keep records for dispute handling when a user in Jakarta, Surabaya, Bandung, or another supported location contacts us through the proper help channel.
- We use email data for login notices, recovery checks, and service messages.
- We use KYC data for account ownership and withdrawal review.
- We use payment data to connect wallet, bank, and cashier records.
- We use device and session data to support mobile access and security checks.
Our zk6 game and service data
We record activity needed to run sportsbook markets, live-dealer tables, slots, esports, and number-game categories. We may process entries linked to Liga 1, Piala Indonesia, baccarat, roulette, blackjack, Dragon Tiger, Aviator, Sweet Bonanza, Gates of Olympus, Mobile Legends, Free Fire, and PUBG Mobile. We use this data for account history, dispute review, internal risk checks, and service improvement.
We use cookies and similar storage to keep login sessions, remember language choices, support cashier navigation, and understand technical errors. Our cookies help the zk6 mobile interface keep users on the correct page after phone network changes. We do not use cookie wording to claim guaranteed access, fixed results, or unrestricted service availability.
We work with payment processors, hosting providers, analytics tools, security vendors, KYC review services, and customer-support systems. Our processors may receive only the data needed for their function. Our servers may sit outside your jurisdiction, and we use standard security practices when data moves between our systems and approved service providers.
Our zk6 policy on rights, retention, and contact
We keep personal data for as long as needed for account operation, payment records, legal obligations, dispute handling, fraud prevention, and audit review. We may keep some records after account closure when law, processor rules, or unresolved claims require retention. We delete or limit data when we no longer need it for those purposes.
We give our users a way to ask for access, correction, update, or review of personal data held in an account. We may need to verify identity before acting on a request. We may decline or limit a request where law, payment records, security review, or another user’s rights prevent full action.
We protect account access through login checks, device review, support verification, and controlled access to internal tools. Our staff access is limited by role. Our support team may handle multilingual help requests, payment questions, KYC upload issues, and account recovery through the channels listed on our Live Chat and FAQ pages.
- We ask our users to keep account email and phone details current.
- We ask our users to contact us when a wallet, bank, or QRIS record does not match the cashier history.
- We ask our users to verify that access and use comply with their own jurisdiction’s law.
We may update this zk6 Privacy Policy when our cashier flow, payment routes, KYC handling, support tools, or legal duties change. We place the current policy on this page so our users can review how we treat account, payment, and game-service data before using our services.
We do not offer our services in jurisdictions where online wagering is prohibited. Our users are responsible for checking local law before creating an account, logging in, making deposits, using sportsbook or live-dealer services, or requesting withdrawal review. We direct legal-scope questions to our Legal notice and service-rule questions to our Terms