Reference

Privacy Policy for India Accounts

Baccarat, Mayan Gold, Football Strike and our wallet sit behind one account, and this Privacy Policy explains how f12 handles the data connected to that account.

Account data explainedUPI records coveredCookie choices describedSupport request routes
f12 Privacy Policy for India Accounts
CONTACT PATHS

Reach Us About Privacy Choices

Privacy questions should go through channels that let us match your request to the correct account without asking you to repeat sensitive details in open places.

Privacy email Send data access, correction, deletion, or cookie questions by email with your account email, mobile number, and a short request summary. We use those details to locate the account before sharing any record.
Live chat handoff If you start in chat, our team may move a privacy request to email when identity checks or written consent are needed. This keeps sensitive account data away from a quick chat thread.
Account correction request For spelling errors, mobile number updates, or payment name mismatches, raise a correction request from the account area. We may ask for proof that matches the wallet or bank record before making a change.
ACCOUNT CARE

How We Handle Your Privacy

Our Privacy Policy is written around the data we actually handle: sign-in details, wallet records, game session logs, device signals, cookies, and support messages.

Account data map

We record your name, mobile number, email, sign-in activity, device type, and region signals so the account can open, stay secure, and show access only where local law permits.

Payment records

UPI, Paytm, PhonePe and Google Pay activity is stored as transaction references, status updates, amount fields, and timing records. We use these records to match wallet activity and respond to payment disputes.

Cookie choices

Cookies help remember sessions, measure page errors, protect sign-ins, and show account messages. You can manage browser cookie settings, though some account checks may not work without required security cookies.

Security checks

We use login alerts, device checks, session controls, and limited staff access to reduce account misuse. If unusual activity appears, we may pause sensitive changes until your identity is confirmed.

Retention approach

We keep account and transaction records for the period needed for service operation, legal duties, fraud checks, dispute handling, and audit needs. When no longer needed, records are deleted or anonymised.

Request handling

When you ask to view, change, export, or delete data, we verify the account first. Some records may remain if law, fraud checks, payment disputes, or security duties require retention.

India Privacy Questions, Clear Answers

These answers explain how the Privacy Policy works when you use the account, wallet, games, cookies, and support channels. If your request depends on a legal duty, payment dispute, or identity check, our team will explain the next step through the contact path linked to your account.

We collect account details such as name, mobile number, email, sign-in records, device signals, region checks, and support messages. Payment activity may add transaction references from UPI, Paytm, PhonePe or Google Pay.

Game and wallet records help us confirm account activity, resolve disputes, check unusual access, and meet record duties. They may include session times, table or game names, wallet status, and transaction references.

Yes. Contact us with your registered email or mobile number and state what you want to view or change. We verify the account first so your data is not shared with another person.

We store payment references, amounts, timing, status updates, and account matching details needed to trace wallet activity. We do not ask you to send full screenshots unless a support check specifically requires proof.

Cookies help keep you signed in, detect errors, remember language or region signals, and protect account access. You can change browser settings, but required security cookies may be needed for account functions.

We keep data for service operation, dispute handling, fraud checks, security needs, and legal duties. When those reasons no longer apply, records are deleted, anonymised, or reduced to non-identifying logs.

Access depends on local law and is available where local law permits. Some privacy requests may also be limited by payment disputes, security checks, or legal retention duties that apply to the account.