Reference

Privacy Policy for your India account

1xbetmovie keeps account, cookie and payment privacy controls in one place, so you can open your account with clarity on what data we collect, why we need it…

Account data scopeCookie choicesUPI privacy contextContact route
1xbetmovie Privacy Policy for your India account
CONTACT PATHS

Privacy contact routes in India

Privacy questions should reach people who can check account records without asking you to share full payment details in open chat.

Email privacy desk Send privacy requests through the email channel shown in your account area. Include your registered phone or email, the request type and any relevant UPI, Paytm or PhonePe transaction reference in masked form.
Live chat privacy queue When you are signed in, live chat can route privacy matters to the right desk. The team may confirm device, login time or masked payment detail before discussing account data.
Account form requests Use the account form for correction, access or deletion requests when you want a written trail. We record the request date, verification step and final response for privacy audit purposes.
ACCOUNT SAFEGUARDS

Account data controls at 1xbetmovie

Privacy work sits alongside account security, not after it. We separate payment references from public-facing account views, limit internal access by role and keep logs for changes that affect your profile.

Data we collect

We collect account identifiers, contact details, device signals, login timestamps and transaction references. Each category supports account access, wallet reconciliation, security checks or privacy request handling, not unrelated sharing.

Cookie handling

Cookie records help keep your session active, remember language choices and flag suspicious access attempts. You can adjust browser settings, though some account and security functions may not work correctly without core cookies.

Security checks

Session security uses password checks, device signals and activity logs to reduce unauthorised access. If a privacy request affects sensitive records, we verify identity before making changes or sharing account data.

Payment records

For UPI, Paytm, PhonePe and Google Pay, we store transaction references, timing and status responses needed for reconciliation. We do not ask you to send full bank credentials through chat.

Retention periods

We keep personal data only while it is needed for account operation, legal record duties, dispute handling and security logs. When retention is no longer required, records are removed or anonymised.

Request changes

You can ask to access, correct or delete eligible account data through the privacy contact route. Some records may need to remain where law, fraud checks or payment reconciliation require retention.

Privacy questions before you join

These answers explain how the Privacy Policy applies when you create an account, use cookies, make payment requests or contact support from India. They are written for direct use, so you can decide what to share, what we keep and how to reach us before you head into the lobby.

We collect the details needed to create and protect your account, such as contact data, login records, device signals and verification details. Payment references are added only when you use a supported India payment route.

UPI, Paytm, PhonePe and Google Pay records are used for wallet reconciliation, payment status checks and dispute handling. We keep references, timestamps and response codes, not full bank credentials or private app passwords.

Yes, you can request access to eligible account data through the privacy contact route. We may verify your identity first, then provide the data we can share under applicable law and account security rules.

Cookies help maintain your session, remember account preferences and detect unusual login activity. You can manage cookies in your browser, but blocking essential cookies may affect sign-in, wallet checks and privacy request verification.

You can ask us to delete eligible personal data, and we will assess the request against account, payment, security and legal record needs. Some transaction or safety records may need to remain for a defined period.

Only teams that need to process or verify the request can access relevant records. Access is role-based, logged where appropriate and limited to the data needed to answer, correct or remove eligible account details.

Yes. Account access and eligibility depend on local law and are available where local law permits. Privacy rights may also vary by location, so our response will reflect the rules that apply to your request.