Reference

Legal terms before you join bdgwin

This Legal page explains the terms that shape your account, your data choices and how we handle records linked to payments such as UPI, Paytm and PhonePe.

Terms of usePrivacy choicesCookie settingsLocal law appliesContact routes

Explore Lobby Read FAQ

How our legal notice applies

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

bdgwin is offered with legal terms that govern account creation, wallet activity, identity checks, data handling, cookie use and contact requests. Access or eligibility depends on local law and is available where local law permits. We may ask for identity or payment proof when the law,

1
fraud checks or account security process requires it. Payment names such as UPI, Paytm, PhonePe and Google Pay appear here only as local context for wallet records, not as separate legal promises from those providers. If a rule changes, your continued account use may be subject
2
to the latest terms shown on our site. You should read this page with the privacy and account terms together, because they explain how we process data, answer requests and keep records needed for legal, tax, security or dispute purposes.

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

CONTACT ROUTES

Three routes for legal questions

Legal questions often need a clear record, so we separate them from general lobby chat.

Email for formal requests Send privacy, terms, data correction or account record requests by email so we can keep a dated trail. Include only the documents needed for the request, and mask unrelated payment or identity details.

Chat for routing help Use live chat when you need to know where a legal request should go. The chat team can route your case, but private data changes or records copies may need email verification.

Account status checks If your access is paused for verification, contact us with the reference shown in your account area. We explain the legal or security step involved before asking for any further documents.

ACCOUNT RECORDS

Six ways we manage legal rights

Our legal handling is built around records you can trace: account events, payment references, cookie choices, support tickets and security checks.

Data collection

We collect account details, contact data, device signals, wallet references and support messages needed to run your account, meet legal duties and handle disputes. We avoid asking for documents unrelated to your request.

Cookie choices

Cookies help us keep sessions active, remember language choices and detect suspicious access. Where optional cookies are used, we explain the purpose and give you a practical way to adjust consent.

Account security

Before sharing records or changing personal details, we verify control of your account through email, phone or document checks. This protects your wallet history and support files from unauthorised access.

Retention periods

Some records stay only while your account is active, while payment, tax, fraud-prevention and dispute files may remain longer when law or operational need requires it. We remove data when no reason remains.

Change requests

You can ask us to correct outdated contact details, update identity records or explain a data entry. We may refuse a change if it would hide payment history, fraud checks or legal records.

Escalation path

If an answer does not address your legal concern, reply to the same ticket and ask for escalation. Keeping one thread helps us read the full history and respond with context.

Seven legal answers before you join

These answers explain how we treat account rights, data access, cookie choices, local law and contact requests. They are written for you as an India customer checking the legal position before opening or using an account. For a formal decision, contact us through the routes above with your account details.

Access or eligibility depends on local law and is available where local law permits. If your location, identity check or account activity conflicts with legal requirements, we may decline or pause access.

We collect details needed for account creation, sign-in security, wallet records, support replies and dispute handling. This may include contact data, device signals, payment references and documents you provide for verification.

Email us from the address linked to your account and state what needs correction. We verify ownership first, then update data where the change is lawful and does not affect required records.

Cookies can keep your session active, remember consent choices and help detect unusual account access. We separate necessary cookies from optional ones where possible and explain how to adjust choices.

Payment records are limited to internal teams and service partners who need access for verification, wallet support, dispute handling, fraud checks or legal duties. We do not publish your private wallet history.

Retention depends on record type. Support chats may be shorter, while payment, tax, identity and dispute files may stay longer when law, security or operational duties require continued storage.

We place the updated terms on our site and apply them from the stated effective date. If the change affects your account rights, you should read it before continuing to use the account.

Legal terms before you join bdgwin

Three routes for legal questions

Six ways we manage legal rights

Data collection

Cookie choices

Account security

Retention periods

Change requests

Escalation path

Seven legal answers before you join

01 Can I open an account from any Indian state?

02 What personal data do you collect for legal records?

03 How do I ask to change my account data?

04 Why do you use cookies on legal pages?

05 Who can see my payment records?

06 How long do you keep account records?

07 What happens if the terms change?

Related Pages