okewla Casino & Sportsbook Data Care

We at okewla collect and process personal data when you create an account, fund your balance, and place transactions on our platform—and we undertake to protect that data with industry-standard encryption and restricted access across all okewla servers and mobile apps.

This privacy policy sets out exactly what we collect, how we use it, who has access to it, and what rights you have. We operate across multiple jurisdictions and comply with local data-protection regulations where okewla services are available—including Indonesia, where our primary user base resides.

Whether you access okewla via Android APK, iOS browser, or desktop, your data handling remains consistent: minimal collection, clear purpose, and transparent third-party sharing when required.

What We Collect and Why

We at okewla collect only the data necessary to operate our platform, process your payments, and comply with regulatory requirements. When you sign up, we ask for your email, phone number, and full name. When you place your first withdrawal request, we require identity verification: a photo of your ID (KTP, passport, or driving licence) and a recent utility bill (electricity, water, or internet bill).

We collect transaction data—every deposit, every bet, every withdrawal—to settle your account, track your balance, and detect fraud. We also log your device type (Android or iOS), IP address, and browser user-agent to improve okewla's mobile experience and prevent unauthorized access.

Payment data on okewla

When you fund okewla via DANA, e-wallet, mobile banking, local payment, online payment, e-wallet, or direct bank transfer (mobile banking, local payment, online payment, e-wallet), we do not store your banking credentials. Instead, we partner with third-party payment processors who handle the transaction directly. We receive only a confirmation code and settlement status—not your PIN, password, or account details.

Identity and verification data

We at okewla store identity documents (ID photos, utility bills) in encrypted form on secure servers. This data is used only for account verification and compliance with anti-money-laundering (AML) regulations. We retain this data for seven years—the standard retention period for financial-sector KYC (know your customer) rules—and delete it afterward unless local law requires longer retention.

Location and device data

We collect your location on each login to ensure okewla services remain available only where permitted by law. If you travel to a jurisdiction where okewla does not operate, your account temporarily locks. We also track device identifiers to prevent fraudulent account takeover and to understand which devices (Android, iOS, desktop) okewla users prefer, so we allocate engineering resources effectively.

Our okewla Data Protection Commitments

We at okewla encrypt all personal data in transit (using TLS 1.3) and at rest (AES-256 encryption). Our servers are hosted in secure data centres with restricted physical access and continuous monitoring. Only okewla staff with a documented need—support agents verifying account ownership, fraud-investigation teams, and compliance officers—can access your data.

Third-party processors we use

okewla partners with external services in limited, necessary ways. Payment processors (DANA, e-wallet, mobile banking, local payment, online payment, and our acquiring banks) handle transaction routing. Email-delivery services send you deposit confirmations and password-reset links. We do not sell your data to marketing firms or data brokers. Any third party who accesses okewla data on our behalf is bound by written data-protection agreements.

Your rights under okewla's policy

We at okewla recognize your right to access, correct, and delete your personal data. To exercise these rights, contact okewla support through the Help section in-app or via email. We will respond within fourteen days. You also have the right to data portability: we can export your transaction history and account details in a machine-readable format (CSV or JSON) upon request.

Cookies and tracking on okewla

Our okewla web platform uses session cookies to keep you logged in across pages. We also use analytics cookies (Google Analytics, without personally identifiable information) to understand how users navigate okewla, which games are popular in Jakarta, Surabaya, Bandung, and Medan, and which payment methods drive the most volume. You can disable non-essential cookies in your browser settings without breaking okewla's core functionality.

Data processing outside your jurisdiction

okewla's servers may sit outside Indonesia, even if you use okewla from Jakarta or Surabaya. By using okewla, you consent to your data being processed in multiple jurisdictions where we operate backup systems and maintain compliance with local regulations. We do not transfer data to jurisdictions with weaker data-protection standards than Indonesia's own framework.

Contact okewla for privacy questions

If you have questions about our privacy practices or suspect a data breach, contact okewla support immediately through the Help section in-app. We maintain a data-protection officer who reviews all privacy concerns and responds within fourteen days. okewla also publishes a breach-notification policy: if your data is compromised, we notify affected users within seventy-two hours.

Mobile app data practices

okewla's Android APK and iOS browser app apply the same privacy controls as our desktop platform. We do not request access to your contact list, camera, or microphone unless explicitly needed for a feature (e.g., face recognition during identity verification). You can revoke app permissions at any time in your device settings. okewla respects those revocations immediately.

Policy updates

We at okewla may update this privacy policy as regulations change or our practices evolve. We notify users of material changes by in-app alert or email at least thirty days before the change takes effect. Your continued use of okewla after the new policy date constitutes acceptance of the updated terms. This policy was last updated on 30 May 2026.