Reference

Privacy Policy for Your w0w Account

Baccarat, War, Football Strike and Spribe Aviator sit beside UPI, Paytm and PhonePe wallet flows, so this Privacy Policy explains the account data we collect when you browse…

Account data useUPI privacy contextCookie choicesRequest contact path

Explore Games Read FAQ

How This Policy Applies in India

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

This Privacy Policy sets out how w0w collects, uses, stores and protects personal data linked to your account, device, wallet actions and support chats. For India, payment references may include UPI, Paytm, PhonePe and Google Pay, but we use those labels only to explain how wallet

1
events are recorded and checked. We do not ask you to share more data than is needed for account access, security checks, payments, legal duties and service replies. Where local law gives you rights to access, correct or delete data, we explain how to send the
2
request and what we may need to verify it. Access and eligibility depend on local law and are available where local law permits, so policy handling may differ by location.

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

PRIVACY HELP

Reach Us About Privacy Requests

Privacy questions need a direct route, not a maze. Use the contact path that matches your request, include the email or mobile number linked to your account, and tell us whether you…

Email privacy desk Send account-data requests to our privacy contact with your registered email or mobile number. Keep payment screenshots out of the first message unless we ask, so only necessary data enters the case record.

Live chat routing If you start in chat, ask for a privacy request handoff. The agent can record the request type, confirm your account marker and move the case to the team that handles data rights.

Wallet query path For UPI, Paytm or PhonePe privacy questions, mention the payment method and date range only. We check wallet logs against account records, then reply with the least data needed to resolve it.

ACCOUNT CARE

What We Do With Your Data

Our privacy work covers the whole account journey: profile creation, login checks, game-session records, wallet actions, cookies and support replies.

Data we collect

We collect account details, contact markers, device signals, login events, game-session records and wallet references. The policy links each data type to a reason, such as account access, fraud checks or legal duties.

Cookie choices

Cookies help keep you signed in, remember language choices and detect risky access patterns. Where optional cookies are used, the policy explains their purpose and how your browser settings can reduce them.

Account safety

Login records, device checks and session history help us spot account misuse. We use these signals for protection and investigation, not for public display, and access is limited inside our operations.

Payment records

UPI, Paytm and PhonePe references may be kept with timestamps, status codes and account markers. We use them to reconcile wallet events, handle disputes and meet legal record duties.

Retention periods

We keep data only while it has a valid purpose, such as account service, legal records, dispute handling or security checks. When that purpose ends, we delete, anonymise or archive it under controls.

Change requests

You can ask us to correct inaccurate account data or explain what we hold about you. We verify the request first, then reply with the action taken or the reason a record must remain.

Privacy Policy Questions Before You Join

These answers explain the privacy points you may want clear before opening an account or sending a request. They focus on data categories, payment references, cookies, retention, access rights and local-law limits. If your case is specific, contact us with your account marker and request type so we can respond without collecting extra personal data.

It covers account details, contact markers, device data, login events, game-session records, wallet references and support chats. The policy explains why each category is used and how it connects to your account.

They appear as payment references tied to wallet actions, timestamps, status checks and dispute handling. We do not publish those records, and we limit internal access to teams that need them for a defined task.

Yes, you can ask us to correct data that is inaccurate or outdated. We may verify your identity first, especially if the change affects login access, wallet records or legal record duties.

Cookies are described by purpose, such as keeping your session active, remembering settings and detecting risky access. Your browser can block some cookies, though certain account and security features may need them.

Retention depends on the data type and reason for holding it. Account service, legal records, wallet disputes and security checks may require different periods before data is deleted, anonymised or archived.

Only staff and service partners with a defined need can access relevant data. Examples include support replies, payment reconciliation, security checks and legal handling, with access limited to the task involved.

Yes. Account access, eligibility and some privacy rights depend on local law and are available where local law permits. If a local rule affects your request, we explain the impact in our reply.

Privacy Policy for Your w0w Account

Reach Us About Privacy Requests

What We Do With Your Data

Data we collect

Cookie choices

Account safety

Payment records

Retention periods

Change requests

Privacy Policy Questions Before You Join

01 What personal data does this Privacy Policy cover?

02 How do UPI, Paytm and PhonePe appear in the policy?

03 Can I ask to correct my account data?

04 How are cookies described in the Privacy Policy?

05 How long do you keep my data?

06 Who sees my data at w0w?

07 Does access depend on local law?

Related Pages