Reference

Privacy Policy for Your 3pl Account

Live Blackjack, Rummy, Football Strike, Aviator, Bingo and Fishing God sit behind account, wallet and support flows where this Privacy Policy explains what data we collect, why we…

Account dataCookie choicesUPI contextPaytm recordsPhonePe receipts
Explore Lobby Read FAQ
3pl Privacy Policy for Your 3pl Account
CONTACT ROUTES

Three Ways to Reach Privacy Support

Privacy requests need a clear path because account records, payment receipts, and identity checks cannot be handled through public comments or social replies.

Email privacy desk Write with the email linked to your account, add the request type in the subject, and we will match it to your profile before sharing any data or changing stored details.
Chat privacy help Use chat after you log in if the question is tied to a live session, device alert, cookie setting, or payment receipt. We may ask for a short account check before discussing records.
Account request form The account menu lets you send correction, access, deletion, or consent queries without exposing private details in open channels. Keep screenshots limited to the part we need to check.
ACCOUNT CARE

Six Privacy Controls Around Your Account

Our privacy work follows the way the account actually runs: login checks before wallet actions, payment matching before withdrawals, cookie choices before device recognition, and support checks before sharing account data.

Data collection

We collect the details needed to open your account, keep sessions linked to you, verify payment activity, and answer support requests. Extra fields are not requested unless a law, security alert, or withdrawal check requires them.

Cookie use

Cookies help remember language, session status, device signals, and fraud-control markers. You can clear cookies in your browser, but fresh checks may be needed when you return or switch devices.

Login security

We monitor failed logins, new device patterns, password resets, and unusual account movement. These checks protect access without exposing your private records to staff who do not need them.

Payment privacy

UPI, Paytm, PhonePe and Google Pay records are used to match deposits, review withdrawals, resolve wallet queries, and meet legal duties. We store only the payment data needed for those purposes.

Retention windows

Some records must be kept after account closure for tax, payment, dispute, audit, or fraud-control reasons. When retention is no longer needed, we delete, mask, or anonymise the data.

Change requests

You can ask us to correct account details, access stored data, withdraw cookie consent, or delete eligible records. We first verify the account so another person cannot alter your privacy choices.

Privacy Questions Before You Join

These answers focus on how the Privacy Policy applies when you open an account, browse the lobby, use local payment methods, speak with support, or request a change to stored data. They do not replace the full policy text, but they point you to the practical parts most likely to matter before you get started. For anything account-specific, contact us through a private channel after logging in where possible.

We collect account details, contact data, login records, device signals, payment references, cookie choices, and support messages. The exact data depends on how you use the account and what checks are required.

Payment records help us match deposits, check withdrawals, resolve wallet questions, and meet legal or tax duties. We use those records for account and compliance purposes, not for selling your profile data.

Yes. Send the request from your account email or through the account menu. We may ask for verification before changing names, contact details, payment records, or other data tied to access and withdrawals.

Cookies keep your session recognised, remember basic preferences, and support device and fraud-control checks. If you clear them, you may need to log in again or complete fresh security steps.

Access is limited to staff who need the data for account service, payments, security checks, support, legal duties, or technical maintenance. Internal access is not open to every team by default.

Retention depends on the record type. Payment, tax, dispute, security, and audit records may stay longer than routine session data. When a valid reason ends, we delete, mask, or anonymise records.

Yes. Access and eligibility depend on local law and are available where local law permits. Privacy checks may also vary when a region requires extra identity, payment, or account safety steps.

Related Pages

About Us Register Aztec Warrior 3pl App