Our betsaya privacy introduction

Our betsaya Platform Privacy Notice for Account Records

This page describes what we collect when you use betsaya and how we keep that data protected when account opening starts with email verification, KYC documents, and a deposit method. We use this policy to explain mobile login, Android installation flow, iOS browser access, QRIS scan-and-pay top-ups, and support review for sportsbook, live-dealer, slot, and esports categories.

We process account data only for service operation, payment checks, security review, dispute handling, and contact support. Our services are available only where local law permits, and we do not offer our services in jurisdictions where online wagering is prohibited.

We write this privacy notice for our users who access football coverage such as Liga 1Piala AFF, Champions League, Premier League, MotoGP, and badminton, plus live-dealer tables, slots, and esports markets. Our privacy practice also covers wallet and bank routes used in Indonesia-region payments.

Our betsaya data details and payment privacy

Our betsaya account data we collect

We collect registration details such as name, email, phone number, login credential records, device signals, and communication history. We may collect KYC documents when we need to confirm identity, recover an account, review a withdrawal, or match a payment route with an account profile.

We collect technical data from Android app access, iOS browser sessions, network status, device type, approximate location signals, and security logs. We use these records to maintain login continuity, detect unusual access, and help our support team answer account questions with enough context.

Our betsaya payment data we process

We process payment details from e-wallet and bank-transfer routes, including DANAe-wallet, mobile banking, local payment, online payment, e-walletmobile banking, local payment, online payment, and e-wallet. We may store reference numbers, provider status, wallet name, virtual-account route, transaction notes, and support screenshots when our users submit them for verification.

We use payment data to confirm deposits, review withdrawals, detect mismatch cases, and answer disputes. Our review may compare account name, payment route, KYC status, deposit history, withdrawal destination, and provider confirmation. We do not treat an image alone as final proof when provider data or account records do not match.

We may process extra context during local payment periods, including public-holiday traffic around Idul Fitri, Idul Adha, Imlek, or Nyepi. Our support records may also show city-level contact context such as Jakarta, Surabaya, Bandung, Medan, Semarang, or Yogyakarta when a user provides it during account help.

Our note: We do not ask our users to send KYC files through random channels. We ask for documents only through approved account or support routes.

Our betsaya use of processors and service tools

We use third-party processors for hosting, payment routing, fraud screening, analytics, communication tools, and document handling. Our processors may receive limited data needed to perform a defined task, such as checking a mobile banking reference, sending a support reply, storing KYC files, or maintaining account security logs.

We may store or process data outside a user’s jurisdiction when our infrastructure or service providers operate in another location. Our contracts and internal access controls require processors to handle data for our service purpose only, subject to standard security practices and verification needs.

Our betsaya cookie and device policy

We use cookies and similar tools to keep a login session, remember language choice, support mobile display, and review technical errors. We may also use cookies to understand page performance for account pages, payment guides, sportsbook sections, live-dealer pages, slot categories, and esports screens.

We allow browser controls to block or clear cookies, but some account functions may not work correctly without session cookies. Our iOS browser access and Android flow may require refreshed login when cookies are cleared, network quality changes, or a device switches between mobile data and Wi-Fi.

Our betsaya privacy policy and user rights

Our betsaya access and correction process

We allow our users to ask for access, correction, or review of account data through our approved contact channels. We may require identity checks before sharing account information, changing contact details, updating KYC records, or confirming payment-route ownership.

We may keep some records after an account request when we need them for legal compliance, fraud review, payment disputes, system security, or audit history. Our retention period depends on record type, account activity, dispute status, and applicable law.

Our betsaya contact and support handling

We provide multilingual help availability for account, payment, KYC, and recovery questions, subject to response windows and case queue. We ask our users to include account email, payment route, reference detail, device type, and a short issue summary when contacting us.

We use support messages to answer the request, check related account records, and improve our help process. We do not sell support conversations, KYC documents, or payment references as marketing lists.

Our betsaya jurisdiction and security limits

We restrict access where local law does not permit online wagering. We may refuse service, close an account, or limit data processing when we believe access conflicts with applicable law, payment rules, account integrity, or our internal security process.

We maintain standard security practices for account records, payment references, KYC files, and support history. We cannot promise absolute protection, so we ask our users to keep login details private, avoid shared devices, check network reliability, and contact us quickly when an account appears compromised.

Privacy policy Guide

Info

↑