Our kevtoto privacy introduction

Our kevtoto Platform Privacy Notice for Account Data

This page describes what we collect when you use kevtoto and how we keep that data protected across account verification, payment options, withdrawal flow, and customer support records.

We collect account data so we can run live-dealer tables, sportsbook markets, slot categories, esports markets, payment records, and support files under one account record. We focus on blackjack, roulette, baccarat, Dragon Tiger, Sic Bo, and multi-camera studio activity because those tables create time stamps, table choices, dealer session records, language settings, and rule-panel interactions.

We use a simple case study in this privacy notice. We may review a user who verifies identity, enables two-factor authentication, watches a live roulette table, checks DANA as a payment route, and later submits a withdrawal request. We use that record to explain what data we collect, why we use it, and when we share it with processors.

Our kevtoto data collection details

We collect identity data such as name, date of birth where required, contact details, account username, password reset records, KYC document references, and verification status. We collect technical data such as device type, browser data, login time, IP signal, cookie identifiers, and session status. We collect payment data linked to DANA, e-wallet, mobile banking, local payment, online payment, e-wallet, mobile banking, local payment, online payment, and e-wallet when those routes are available in the account.

We collect live-dealer data when our users enter blackjack, roulette, baccarat, Dragon Tiger, Sic Bo, or another studio table. Our records may include table name, round reference, seat or view setting, table-limit context, video-quality setting, language preference, and support notes linked to the session. We collect sportsbook data for event browsing and settlement checks, including Liga 1Piala AFF, Champions League, Premier League, MotoGP, and badminton categories.

Our kevtoto privacy review follows account risk signals

We may ask for added verification when a password reset, device change, payment route change, or withdrawal request does not match our account record.

We use personal data to open and maintain accounts, run KYC checks, manage two-factor authentication, process deposits and withdrawals, answer support requests, and review disputes. We use table and game records to confirm live-dealer activity, round status, rule application, and provider settlement notes. We use payment records to match account ownership, transaction references, provider status, and withdrawal review steps.

We work with third-party processors when we need payment routing, game provision, fraud screening, identity verification, hosting, analytics, or support tools. Our processors may handle selected data under our instructions. Our servers and processors may sit outside your jurisdiction, so we apply access controls, retention limits, and contractual safeguards where data is transferred.

We use cookies and similar tools to keep login sessions active, remember language settings, support security checks, and measure basic site performance. We may use cookies to separate live-studio pages from account pages, so a baccarat table screen does not mix with a withdrawal review screen. We do not use cookies to remove the user’s duty to check local law.

Our kevtoto privacy policy and your rights

We give our users the right to ask for access, correction, deletion, restriction, or a copy of personal data where applicable law allows. We may need to keep some records after a request when payment review, KYC proof, dispute resolution, fraud prevention, or legal compliance requires retention. We may also ask for identity confirmation before we answer a privacy request.

We handle privacy requests through our support process. We ask the user to provide the account identifier, contact detail, and a clear request. We may compare that request with login history, KYC status, payment records, and recent account changes. We use the same cautious method when a user from JakartaSurabaya, Bandung, Medan, or Semarang asks us to correct account details after a payment-route update.

We protect account data with standard security practices, including access controls, review logs, encryption where appropriate, and internal handling rules. We encourage two-factor authentication because it helps reduce account takeover risk after password sharing, device loss, or email compromise. We do not treat any security control as a guarantee, and we may suspend selected actions while our review continues.

We contact users through account messages, email, or support channels when we need privacy clarification, KYC follow-up, payment review, or dispute information. We do not ask users to send password details through support. We may send service messages about account status, verification, cookie changes, or policy updates.

We make our services available only where local law permits. We do not offer our services in jurisdictions where online wagering is prohibited. We require our users to verify that access and use comply with their own jurisdiction's law before using live-dealer tables, sportsbook markets, slot games, esports markets, or payment routes.

Privacy policy Guide

Info