Reference

Privacy Policy for your z1100 account

Speed Baccarat, Prosperity Lion, Football Strike and wallet actions create account data, and this Privacy Policy explains how we collect, use, secure and keep it.

Account data useUPI privacy contextCookie choicesSecurity checks
z1100 Privacy Policy for your z1100 account
CONTACT ROUTES

Three policy contact routes

If a privacy question comes up while you are using the lobby or wallet, contact us through the channel linked to your account.

Account privacy desk Use the in-account support form for privacy requests tied to login, KYC checks, device activity, or wallet records. Keeping the request inside your account helps us match the query without asking for extra documents.
Email privacy mailbox Write to the privacy contact listed in your account area if you cannot sign in. Include your registered mobile number, email address and request reason, but never include UPI PINs, wallet passwords or card secrets.
Payment query link For Paytm, PhonePe, Google Pay or UPI transaction privacy questions, share the transaction ID and time. We use those details to trace the record and explain what data was stored for that payment.
PRIVACY CONTROLS

Six privacy controls we keep active

Our Privacy Policy is written around the account actions you can see: login, wallet use, table access, game history, support contact and security checks.

Data collection

We collect account details, login signals, device data, wallet status, game session references and support messages only for defined purposes. This helps us run your account, resolve disputes and check activity that looks unusual.

Cookie handling

Cookies help keep you signed in, remember display choices and detect repeated failed logins. You can control browser cookies, but some account security checks may not work correctly if essential cookies are blocked.

Account security

We use password checks, session controls, device signals and manual checks when risk flags appear. If we need to confirm a privacy request, we ask for account-linked clues rather than wallet passwords or UPI PINs.

Record retention

Some records are kept while your account is active, and some are kept longer for payment disputes, fraud checks or legal duties. When the reason ends, we reduce, archive or delete data based on our retention process.

Third party processors

Payment partners, hosting providers, analytics tools and support systems may process limited data for us. We share only what they need for the task, and we expect them to handle it under contract terms.

Change requests

You can ask us to correct account details, explain a record, restrict certain processing, or delete data where the law allows. We confirm identity first so another person cannot change your account record.

Seven privacy questions before you join

These answers explain how the Privacy Policy works in normal account situations, including wallet use, cookies, identity checks and support contact. They are written for India and should be read with the full policy terms shown on this page and inside your account area.

We collect details such as your name, contact details, login credentials, device signals and account activity. If verification is required, we may also process documents or reference checks needed to confirm the account holder.

No. For UPI, Paytm, PhonePe and Google Pay, we may store transaction references, status messages and timestamps, but we do not ask for or store your UPI PIN, wallet password or banking password.

Cookies help keep your session active, remember basic settings, measure site stability and spot risky login patterns. You can manage cookies through your browser, though some account features may need essential cookies.

Yes. Contact us from your account or the privacy mailbox with the detail you want corrected. We may verify your identity first, then update the record where the request is lawful and technically possible.

We keep records only for account operation, payment dispute handling, security checks and legal duties. Retention periods can differ by record type, and data is reduced or removed when there is no continuing need.

Only teams that need to handle the request can access it, such as account support, payment operations or compliance staff. Access is role-based, and sensitive payment secrets are not requested in privacy conversations.

This Privacy Policy explains data handling; it does not change legal eligibility. Access to account services depends on local law and is available where local law permits, including any region-specific checks we must apply.