Reference

Privacy Policy for Indian Accounts

This betvibe privacy policy explains what we collect when you open an account, use wallet features, or contact support, and how we use it to run your request…

Account dataCookie useLocal lawSupport records
betvibe Privacy Policy for Indian Accounts
CONTACT PATHS

How to Reach Our Privacy Team

If you need help with access, correction, or deletion requests, use the contact paths below and send the message from the email on file.

Email us Send privacy requests from the email on your account, and we will match it against our records before replying. Use this path for access, correction, or deletion requests that need a written trail.
In-account chat Use chat for quick questions about what we collect, how cookies work, or which record we need next. If the issue needs identity checks, we will move it to a written channel.
Privacy form If you prefer a structured request, send the form with your account email, the change you want, and any reference details. We use it to route the case and avoid extra delays.
RECORD HANDLING

Account Records and Retention

We keep this policy focused on the smallest set of records that lets us operate your account cleanly.

What we collect

We collect contact details, device logs, cookie choices, and messages you send us. We keep the set narrow so the record stays useful for support, verification, and account access without storing extra material.

Why we use it

We use the record set to confirm identity, keep sessions stable, answer questions, and handle disputes. Where law requires it, we also keep the necessary history for accounting or compliance checks.

Cookies and devices

Browser cookies remember language, session state, and page settings. Device markers help us notice repeated sign-ins from the same source and protect the account from misuse or accidental lockouts.

Payment references

UPI, Paytm, PhonePe, and Google Pay references are stored for reconciliation and support follow-up. We do not keep more payment detail than needed, and we separate the reference from the message content where possible.

Retention windows

We keep each record only for the period needed for the purpose it served, unless a legal hold says otherwise. After that, we remove, mask, or archive the item so it no longer sits in active use.

Access and correction

If something is wrong, send the change request from the email on file. We verify the requester, make the update when allowed, and tell you when a record must stay unchanged for legal reasons.

Questions on Your Privacy Rights

These questions cover the parts people ask about most: what we hold, why we hold it, how long it stays, and how you can ask for a change. We keep the answers direct so you can decide what to do next without chasing around the site. If a request needs identity checks or a legal hold applies, we say that plainly before anything moves forward.

It covers account details, device logs, cookie choices, payment references, and support messages that we use to run your account, answer requests, and keep records accurate where local law permits.

Yes. Send a request through the support path using the email on your account, and we will confirm what can be shared, what needs verification, and whether any legal hold applies.

We use cookies to keep sessions active, remember language choice, and store page settings. You can change browser settings, though some parts of the site may not keep their state after that.

Yes, for reconciliation, dispute handling, and record keeping. UPI, Paytm, PhonePe, and Google Pay references stay only as long as needed for those purposes, then they are archived or masked.

Yes. Ask support to update the detail that is wrong, and we will verify the request before making a change so the record stays accurate and matches the current account holder.

Retention depends on the record type and any legal need. Some logs stay briefly for session checks, while transaction records may stay longer for accounting, dispute handling, or audit needs.

Use the privacy contact path in the support section and send the request from the registered email. We will respond after verifying identity and checking what can be actioned.