Our kepo66 Privacy Policy for Account Data and Payments

Our kepo66 privacy introduction

This page describes what we collect when you use kepo66 and how we keep that data protected in a mobile-first account environment. We note that Bank Indonesia has reported broad QRIS adoption across bank and e-wallet applications, and we use that context to explain why our privacy practice gives close attention to payment identifiers, phone login records, and scan-and-pay top-up references.

We operate kepo66 for account holders who access football coverage, live-dealer tables, slot games, esports markets, and payment history from a phone. We support Android installation flow, iOS browser access, account login on mobile networks, and e-wallet top-ups where available through supported payment apps. Our services are available only where applicable law permits, and our users are responsible for verifying that access and use comply with their own jurisdiction's law.

We collect data only for account operation, payment review, fraud prevention, service communication, and compliance checks. Our payment records may include mobile banking, local payment, online payment, e-wallet, mobile banking, local payment, online payment, e-wallet, mobile banking, and local payment references, depending on what method our account holder selects. We do not present those records as public activity, and we separate account support notes from game catalogue browsing where our systems allow that separation.

Our kepo66 data details

We collect your registration details when you create or update an account, including phone number, email address, username, password credentials in secured form, and contact preferences. We may collect identity information during KYC review when a withdrawal, account recovery request, unusual login pattern, or payment mismatch requires document handling. Our KYC documents are used to verify account ownership and payment consistency, not to create a public profile.

We collect payment data when you use DANAe-wallet, mobile banking, local payment, online payment, e-walletor virtual-account transfer through mobile banking, local payment, online payment, or e-wallet. We may record transaction reference codes, masked account names, deposit status, withdrawal destination, review notes, and time-stamped system events. Our withdrawal flow may require us to compare the requested destination with previous verified payment details before we release a transaction for processing.

We collect technical data from your device so our platform can handle account login, session security, language display, payment routing, and basic compatibility on mobile networks. We may receive browser type, operating system, approximate location from network signals, device identifier, IP address, failed login records, and cookie identifiers. Our mobile flow uses those signals to detect account takeover attempts, repeated password errors, and abnormal access from cities such as JakartaSurabaya, Bandung, Medan, Semarang, or Yogyakarta.

Our kepo66 payment and verification records

We use deposit data to credit the correct account, trace stalled top-ups, verify mobile banking scan results, and check whether e-wallet or bank transfer details match the account profile. We use withdrawal data to confirm that a payment request follows our verification practice, especially when a user changes phone number, bank account, e-wallet name, or document record. Our support team may ask for screenshots or reference numbers when a transaction needs manual review.

We use account data to provide access to football markets such as Liga 1 coverage, live-dealer tables such as blackjack, roulette, baccarat, and Dragon Tiger, slot titles such as Aviator and Sweet Bonanza, and esports markets including Mobile Legends, Free Fire, and PUBG Mobile. We keep this game-related data for account settlement, security review, dispute handling, product maintenance, and legal compliance where applicable.

• We collect registration and login details to keep account access traceable.
• We collect payment references to match deposits and withdrawals with verified account records.
• We collect KYC documents when ownership, recovery, or payment review requires a clearer record.
• We collect support messages so we can respond through the correct contact channel.

Our kepo66 processors and storage practice

We work with third-party processors that may support payment routing, identity review, security monitoring, hosting, analytics, messaging, and customer help tools. We require those processors to handle data for service purposes rather than their own independent promotion. Our servers may sit outside your jurisdiction, and we use contractual, technical, and administrative controls to reduce unnecessary access to personal data.

We retain account records for as long as we reasonably need them for payment reconciliation, legal obligations, fraud prevention, dispute review, and account recovery. We may keep withdrawal and KYC records longer than ordinary browsing logs when those records support transaction review or compliance duties. Our retention practice aims to avoid keeping data that no longer has an operational or legal reason.

Our kepo66 privacy policy commitments

We use cookies and similar technologies to keep you signed in, remember language choices, secure sessions, measure basic service performance, and detect repeated errors during payment or login flow. We may use essential cookies for account access and security, and we may use limited analytics cookies to understand page performance. Our cookie use does not change the rule that our services are available only where local law permits.

We provide account rights through support channels, including requests to access, correct, update, or review personal data connected to your account. We may ask you to verify ownership before we change phone numbers, email addresses, e-wallet details, or withdrawal destinations. Our account recovery practice may require KYC documents, past payment references, or other proof that helps us avoid releasing data to the wrong person.

We keep contact options available for privacy questions, payment review, account recovery, and document handling. We may respond through multilingual help channels when staff availability and case type allow it, and we may prioritise security-sensitive requests such as lost access, changed payment details, or suspected unauthorised login. Our response windows can vary when a case depends on payment processors, bank confirmation, or document review.

1. We ask you to contact support from the registered email or phone when possible.
2. We ask you to provide transaction references for stalled DANA, e-wallet, or bank-transfer cases.
3. We ask you to submit clear KYC images only through our approved account channel.
4. We ask you to avoid sharing passwords, one-time codes, or wallet access with another person.

We may update this kepo66 policy when our payment flow, verification practice, support tools, or legal duties change. We will publish the revised wording on this page and apply it from the stated update point where our template provides one. Our users should review this policy when they change payment method, recover an account, or submit new documents.

We treat privacy as part of account service quality, not as a separate notice hidden from payment and withdrawal practice. We connect data handling with mobile banking, local payment, online payment, e-wallet, mobile banking, local payment, online payment, e-wallet, mobile banking, local payment, mobile login, KYC review, and support contact because those are the places where personal information most often enters our system. Our policy is written to explain that flow in plain terms for kepo66 account holders.