Reference

Legal access for h5n1 accounts

Clear account terms, data rules, cookie choices and UPI record handling sit here before you open your account.

Local-law accessData rightsCookie choicesUPI record checks
h5n1 Legal access for h5n1 accounts
CONTACT PATHS

Contact routes for legal requests

Legal requests need enough detail for us to locate the account without sharing sensitive records in the wrong channel.

Email Desk Write to [email protected] with the phone number or email tied to your account, the date of the issue, and any UPI or wallet reference. We use that trail to route legal requests without exposing data in chat.
In-Lobby Chat Use chat for quick legal routing, such as asking where to send a correction request or account closure request. Our team will not ask for full payment credentials and may move detailed matters to email.
Record Request For copies of account records, cookie consent history or transaction references, send a written request from your registered contact. We verify control of the account before sharing any record or making changes.
DATA CARE

Data, cookies and account security

Our legal handling is built around proof, privacy and clear account control. We collect only the details needed to run the account, process payments, answer disputes and meet legal duties.

Data collection

We collect account contact details, sign-in records, device signals, payment references and support messages. Each record has a purpose: account access, fraud prevention, legal compliance, dispute handling or service communication requested by you.

Cookie choices

Cookies keep your session active, remember consent choices and help detect unusual access patterns. You can change browser cookie settings, but some account checks may need fresh sign-in or extra verification after changes.

Account security

We protect account changes with contact verification, session checks and payment-reference matching. If a password reset, withdrawal query or data request looks unusual, we may pause the action until you confirm control.

Record retention

We keep records for as long as needed for account operation, legal duties, payment disputes and fraud prevention. When a record is no longer required, we remove it or reduce it so it no longer identifies you.

Correction requests

If your name, contact detail or payment reference is wrong, send the correction request from your registered email or phone. We may ask for proof before editing records that affect wallet or identity checks.

Legal contact

Send legal questions, privacy requests or account closure requests to [email protected]. Include your registered contact and a clear request, but never send card numbers, full UPI PINs or account passwords.

Legal questions before you join

These answers explain how our legal terms affect your account, your data and your ability to use the service in India. They are written to help you decide what to do next without guessing. If your case involves a court order, state restriction or payment dispute, contact us with exact account and transaction details.

Access depends on local law and is available where local law permits. If your location or payment route falls under a restriction, we may block account activity or ask for extra verification.

We collect contact details, sign-in records, device signals, payment references, cookie choices and support messages. These records help operate your account, answer disputes, meet legal duties and detect unusual access.

Yes. Send the correction request from your registered email or phone with the exact field that needs change. We may ask for proof before editing details tied to identity or wallet checks.

We store payment references, timestamps and method names to match deposits, withdrawals and disputes. We do not need your UPI PIN, wallet password or full banking credentials for any legal request.

You can request closure through email or chat routing. We verify control first, then check for unresolved balances, open disputes or legal retention duties before closing or limiting further account activity.

Cookies record session status and consent choices, and they help identify unusual access. You may adjust browser settings, but some changes can trigger sign-in checks or require renewed consent on your next visit.

Email [email protected] from your registered contact and state whether you want access, correction, deletion or closure. Include payment references only when relevant, and avoid sending passwords or secret wallet credentials.