Reference

How we protect your account data

Our Privacy Policy explains how rajabet handles your account details, device signals, wallet records and privacy choices when you browse the lobby or manage payments through UPI, Paytm…

Account data useCookie choicesUPI record handlingPrivacy request path

explore the lobby Read FAQ

What this policy covers for India

rajabet Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

This Privacy Policy sets out the data we collect, why we collect it, how long we keep it and how you can ask us to check, update or delete it where the law allows. We collect account details you give us, technical signals from your device,

1
payment references connected with UPI, Paytm, PhonePe or Google Pay, and records needed to keep your wallet and login activity accurate. We use this data for account access, identity checks, fraud prevention, support handling, payment matching, service messages and legal duties. We do not sell your
2
personal data. We may share limited records with payment processors, security vendors, analytics services, customer care tools and authorities when a lawful request applies. Access and eligibility depend on local law and are available where local law permits.

Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

CONTACT PATHS

Three ways to raise privacy requests

If you want to ask about personal data, use the channel that matches your request. Privacy queries are handled separately from general lobby questions so the right team can check account ownership…

Email privacy desk Write to our privacy mailbox with your registered email, request type and any related UPI, Paytm or PhonePe reference. We check ownership before sharing account records or making data changes.

Live chat handover Start a chat from your account and ask for privacy help. The agent can collect the request, verify basic access, then move it to the team that handles data rights.

Security escalation If you think your login, device or wallet data has been exposed, tell us quickly through chat or email. We can restrict access while the security team checks recent account activity.

ACCOUNT CARE

Six privacy controls we apply

Privacy work is part of how we run accounts, not a side document. Our teams look at collection, storage, access and deletion as separate steps, because each one carries a different risk.

Data collection

We collect only the account, device, wallet and support details needed to create access, match payments, protect sessions and answer requests. Optional fields are treated separately from records needed by law.

Cookie handling

Cookies help keep you signed in, remember language choices and measure page issues. Some cookies are needed for account security, while analytics cookies can be adjusted where our tools allow.

Payment records

UPI, Paytm, PhonePe and Google Pay references are used to match deposits and withdrawals with your wallet. We store transaction IDs, timing and status, not your complete banking credentials.

Account security

Login checks may use device type, IP range, session timing and failed access patterns. These signals help us spot unusual activity without giving routine support staff unnecessary access to sensitive records.

Retention periods

We keep records for as long as needed for account service, payment disputes, security checks and legal duties. When data is no longer needed, we delete it or reduce it to non-identifying records.

Change requests

You can ask us to correct account details, check stored data or remove records where the law allows. We verify identity first so another person cannot change your account on your behalf.

Questions about your data rights

These answers explain how our Privacy Policy works in day-to-day account situations. They cover the data we collect, how local payment references are handled, how cookies affect your session, and what you can ask us to change. If your request depends on law, account status or payment checks, we will explain the next step after verification.

We collect details you provide during account setup, login and support contact, plus device signals, cookie data and wallet records. Payment references from UPI, Paytm, PhonePe and Google Pay are kept for matching and checks.

Payment references help us connect a wallet action with the correct account, confirm status and resolve disputes. We do not need your full bank credentials, card secrets or private UPI PIN to do this.

Yes. Send a request through email or account chat, and we will verify that the request comes from you. We then share the data we can provide under applicable law and account safety checks.

Cookies keep your session active, remember basic choices and help us detect page errors or unusual access. Some are necessary for security, while other measurement cookies may be adjustable through browser settings.

Access is limited to teams and service partners who need the data for payment matching, security checks, support or legal duties. Internal access is role-based, logged and reviewed when sensitive records are involved.

Contact us from your registered email or logged-in chat and describe what needs correction. We may request proof or payment references before updating names, contact details or wallet-related records.

You may ask for deletion where the law allows. Some records must be kept for payment disputes, security checks or legal duties, and we will explain any reason that prevents immediate removal.

How we protect your account data

Three ways to raise privacy requests

Six privacy controls we apply

Data collection

Cookie handling

Payment records

Account security

Retention periods

Change requests

Questions about your data rights

01 What personal data does rajabet collect?

02 Why do you need my payment references?

03 Can I ask to see my stored data?

04 How do cookies affect my account privacy?

05 Who can access my account records?

06 How can I correct account details?

07 When can my data be deleted?

Related Pages