Reference

Open paribet privacy choices

Live Roulette, Jade Butterfly, Football Strike and Crash X sit behind one account, so this Privacy Policy explains what data we use when you browse, log in, pay…

Account data explainedCookie choicesUPI record contextIndia privacy contact
paribet Open paribet privacy choices
CONTACT ROUTES

Check privacy contact paths

Privacy requests work better when they reach the right queue with enough detail to identify your account. Tell us whether your query is about access, correction, deletion, cookies, payment records or security alerts. Please avoid sending full UPI PINs, card secrets or one-time codes in any message. We may ask for a short verification step before changing account data, because privacy requests should come from you and not from another person.

Team online

Account privacy email

Send privacy requests from the email linked to your account. Include your username, the request type, and the data period you mean, so our team can locate the right records without asking twice.

Live chat privacy handoff

Use chat for quick routing when you are logged in. The agent can mark the issue as privacy related, confirm the account, and move sensitive requests to the correct team.

Payment record query

For UPI, Paytm, PhonePe or Google Pay privacy questions, share only the transaction ID, date and amount range. Do not share private banking passwords or one-time codes.

DATA CARE

Explore account data controls

We handle privacy as part of the account journey, not as a separate formality.

Data we collect

We collect account details you provide, login timestamps, device type, IP signals, cookie choices, game-session records and support messages.

Why we use it

Your data helps us open and maintain the account, process deposits and withdrawals, detect unusual access, personalise cookie settings, answer…

Cookie handling

Cookies help keep your session active, remember language choices and measure page performance.

Security practice

We use access controls, monitoring, encryption in transit and staff permission checks to reduce exposure of personal data.

Retention approach

We keep account, payment and security records only for as long as needed for service, legal, tax, dispute, fraud-prevention or…

Your requests

You may ask to access, correct or delete eligible data, withdraw certain consents, or object to some processing.

See answers on privacy requests

These answers explain how the Privacy Policy applies when you open an account, use cookies, make payments, browse games or contact support. They are written for India and refer to UPI, Paytm, PhonePe and Google Pay records where relevant. For a request about your own account, contact us from your registered email or through logged-in chat so we can verify you before taking action.

We collect details you provide during account setup, login records, device signals, cookie choices, game-session records, payment references and support messages. These records help us run the account and respond to your requests.

We use transaction IDs, timestamps, amount ranges and status updates to match deposits or withdrawals to your account. We do not ask for UPI PINs, wallet passwords or one-time codes.

Yes, you can request a copy of eligible account data by contacting us from your registered email or logged-in chat. We may verify your identity before preparing the available records.

You can ask us to correct eligible details if something is wrong or outdated. Some changes, such as payment names or identity fields, may need verification before we update the account.

We keep records for the period needed for account service, payments, legal duties, dispute handling and security checks. When retention is no longer needed, records may be deleted, anonymised or restricted.

Cookies may remember session status, language, device settings and page performance. Game-session records are handled under this Privacy Policy and used for account history, support checks and security monitoring.

Use the privacy email linked on our site or start logged-in chat and ask for a privacy handoff. Include your username, request type and date range, but never share secret codes.