Reference

Open Privacy Policy for Indian accounts

jackpotin sets out what data we collect, why we use it, and how long we keep it so you know what happens after you open an account.

Data useCookiesAccess requestsLocal law

Browse Lobby Read FAQ

Explore data use and consent

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

This policy explains how jackpotin handles the data tied to your account, device, support chats, and payment activity. We collect only what we need to create access, match deposits and withdrawals, complete verification, and keep records for dispute handling. When you use UPI, Paytm, PhonePe, or

1
Google Pay, the payment reference and status are stored with your account so we can reconcile the transaction and answer if something does not match. Cookies and similar tools help us remember session state, language choice, and security checks. Where local law limits access or requires
2
extra steps, we follow those rules and make the relevant feature available only where local law permits. If you ask for a copy, correction, or deletion of data, we use the contact paths below and verify the request before changing records.

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

CONTACT ROUTES

Switch to contact paths for requests

At jackpotin, we keep three contact paths open for privacy requests so you can choose the one that suits your record trail.

HANDLING STANDARDS

Browse retention, access, and cookies

We handle your account data on a need-to-know basis: sign-up details, device signals, support messages, and payment references stay tied to your profile only as long as we need them.

Data capture

We keep only the details needed to open and maintain your account, such as contact data, device signals, and payment references. That lets us match requests, reduce duplicate checks, and answer data questions with a clear record.

Cookie use

Cookies remember session state, language choice, and whether a login step was already completed on the device. They help us avoid asking for the same action twice, but they do not replace the account checks that protect your record.

Account protection

Before we change sensitive records, we verify the request against the account email, support history, or another matching detail. This reduces the chance of an unauthorised edit and keeps your privacy request tied to the right file.

Retention windows

We retain data only for the period needed for account support, dispute handling, and legal recordkeeping. Once that period ends, we remove or de-identify the data unless a law asks us to keep it longer.

Change requests

To ask for a correction, removal, or copy, contact us through the channels listed here and tell us exactly what should change. Clear requests help us locate the record faster and close the case without extra back-and-forth.

Record access

When you ask to see what we hold, we return the data we can share and explain any parts that must stay restricted under law. If more detail is needed, we point you to the same request path.

Open common privacy questions

The questions below cover the points you are most likely to ask before opening or updating an account. We keep the answers tied to our policy language so you can see what we collect, why we keep it, and how to contact us for access or corrections. If local law changes the way a request must be handled, we follow the applicable rule and update the process.

We store the details you submit when you open an account, along with device and session data needed for access, support, and security checks. Payment references stay linked to the relevant record so we can match them later.

Cookies help keep you signed in, remember session state and language choice, and reduce repeated checks on the same device. You can clear them in your browser, but some access steps may then appear again.

We keep the reference, status, and amount needed to reconcile a payment, answer support questions, and handle reversals or disputes. The record stays attached to your account only for as long as the law and our records require.

Yes. Send a request through the contact paths below with your account email and the exact change or copy you need. We verify the request before we share records or edit stored details.

We keep data only for account support, dispute handling, fraud checks, and legal recordkeeping. When that period ends, we remove it or de-identify it unless a rule requires us to keep it longer.

Access is limited to staff and service partners who need the data to run the account, process support, or maintain systems. We do not share records outside that scope unless law or your request allows it.

We update the page, show the effective date, and keep the current version available. If a change affects how we handle your data, we apply the new text from that point and keep the request path open.

Open Privacy Policy for Indian accounts

Switch to contact paths for requests

Browse retention, access, and cookies

Data capture

Cookie use

Account protection

Retention windows

Change requests

Record access

Open common privacy questions

01 What data do you collect from me?

02 Why do you use cookies on my device?

03 How do you use payment records?

04 Can I ask for a copy or correction?

05 How long do you keep my data?

06 Who can access my data?

07 What if the policy changes later?

Related Pages