Reference

Privacy Policy for your India account

Your account connects Blackjack, Rummy, Football Strike, Spribe Aviator, Bingo, wallet activity and support messages, so this Privacy Policy explains what data we collect and why.

Account dataCookie choicesUPI recordsPaytm contextPrivacy requests
kabook99 Privacy Policy for your India account
CONTACT ROUTES

Three privacy contact paths

Privacy requests work faster when you reach the right team with enough detail for us to locate your account.

Privacy email Email [email protected] from the address on your account.
In-account help After you join, use the help panel inside your account for privacy questions linked…
Payment data query For UPI, Paytm or PhonePe privacy questions, share the transaction reference, date and amount…
CARE CONTROLS

Six controls around your account data

We handle privacy through practical controls rather than broad promises. Account data is separated by purpose, payment references are limited to wallet and compliance tasks, and support access is kept to cases…

Account verification

When you create or update an account, we may check your name, mobile number, email and access signals. These checks help prevent account takeover and keep privacy replies linked to the right person.

Payment records

UPI, Paytm and PhonePe entries may include reference IDs, timestamps, amounts and wallet status. We do not ask for full card data, and we keep payment details only for account and legal needs.

Cookie choices

Cookies help remember your session, language choice and security state. Some are needed for login, while optional cookies may measure page use; you can adjust choices through your browser or account settings.

Game activity data

If you open Blackjack, Rummy, Fishing War or Spribe Aviator, we record activity needed to settle rounds, handle disputes and protect wallet accuracy. This record is not used to expose private play history publicly.

Retention checks

We keep personal data only while it serves account operation, legal duties, security checks or open requests. When that reason ends, we remove, mask or anonymise records under our retention process.

Change requests

You can ask us to correct outdated details, send a copy of account data or delete records where the law allows. We verify identity first so changes do not harm your account security.

Privacy questions before you join

These answers explain how we apply the Privacy Policy in common account situations. They cover data collected during registration, payment records, cookies, support contact, correction requests and deletion requests. If your case involves local law, payment partner rules or account security, our reply may include the reason for any delay or retained record.

We collect details needed to create and protect your account, such as name, mobile number, email, login signals and device data. Payment references are added only when you use UPI, Paytm or PhonePe.

We keep payment references to confirm deposits, process withdrawals, trace wallet queries and meet legal record needs. The record normally includes reference ID, time, amount and status, not full payment credentials.

Yes. Email [email protected] or use in-account help after you join. We will verify that the request comes from you before sharing a copy or explaining any data we cannot release.

Some cookies keep you logged in and protect account security, while optional cookies help us measure page use and fix errors. You can adjust browser settings, and some choices may affect account functions.

Send the correct detail through the privacy email or in-account help panel. We may ask for extra proof before changing mobile numbers, payment links or identity details that affect access to your wallet.

You can request deletion, and we will remove data where the law allows. Some records may remain for payment disputes, security checks or legal duties, and we will explain the reason in our reply.

Yes. Access and eligibility depend on local law and are available where local law permits. Privacy requests still apply to your stored account data, even if access changes in your location.