Reference

How 4nec2 Handles Your Data

We explain how account details, wallet records, device signals and support chats are handled, so you know what stays on file before you open an account.

India accessData useCookiesSupport path

Browse The Lobby Read FAQ

Scope, Use and Local Law

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

This policy explains how we collect, use, store and share records linked to your 4nec2 account. That includes profile details, device and browser signals, payment activity from UPI, Paytm, PhonePe and Google Pay, plus messages you send to support. We use those records to run sign-in

1
checks, process deposits and withdrawals, settle disputes, prevent misuse and meet record-keeping duties. We may also share only the minimum needed with service providers, payment partners, fraud checks or authorities when the law requires it. Where local law gives you a right to ask for access,
2
correction or deletion, we will check the request from the registered account path and confirm it after verifying your identity. Access and eligibility depend on local law and are available where local law permits. If our handling changes, the version on this page is the one
3
that applies when you visit.

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

CONTACT ROUTES

Ways To Reach Us

If you want to check, correct or delete records covered by this policy, use the contact path that matches your account.

Email request Send your privacy request from the registered email with your account ID, the detail you want checked and any proof we ask for. That helps us verify the case and reply through the same mailbox.

In-account chat Use chat from the account area when you need a quick answer on access, correction or deletion. If the request affects sensitive records, we may move it to a verified email trail.

Written request If you prefer paper, send a signed request to the postal address in the footer with your contact details and account reference. We match it to the file, confirm identity and continue from there.

DATA CARE

How We Handle Records

We keep privacy handling practical: collect the details needed to run the account, use cookies for sign-in and preferences, lock down sensitive changes and keep only the records required for service, disputes…

Collected records

We keep the details needed to run your account: name, contact fields, device signals, login history, wallet entries and support messages. Anything outside that purpose is not asked for unless law or fraud checks require it.

Cookie use

Cookies remember your session, language and basic security settings. They also help us spot repeated failed logins or device changes. If you clear them, some settings will reset and we may ask you to sign in again.

Sign-in checks

Sensitive actions such as password changes, payout requests or contact edits can trigger a code check or another proof step. That extra layer helps us keep the account tied to you, not to an unknown device.

Retention

We retain records only for the period needed to serve your account, settle disputes, meet tax or legal duties and complete fraud checks. After that period ends, we delete or anonymise data where the law allows.

Correction requests

If you want to correct an email address, phone number or other stored detail, send the request from the registered account path. We verify the request first, then update the file and confirm the change.

Privacy contact

For any privacy issue, use the support route on the site or the mailbox in the footer. We log each request, note the action taken and keep the response with the case record.

Questions About This Policy

These answers cover the records we hold, the reason we use cookies, the steps behind verification and how long data stays in the file. They also explain what happens when you ask for a correction or deletion request. If your case depends on local law, we handle it under the rule that applies where local law permits, and we answer through the same contact path you used so the thread stays clear.

It covers the account details, device signals, cookies, wallet records and support chats we handle for your 4nec2 account. It also explains why we keep each record and how long it stays in the file.

We collect only what we need to open, verify and service the account: name, phone or email, login signals, transaction records, device data and the messages you send to support. We avoid extra fields unless law requires them.

Cookies help us remember your sign-in state, language choice and a few security checks. They also help us spot unusual access patterns. If you clear them, some settings reset and you may need to sign in again.

We keep records for the time needed to run the account, settle disputes, meet tax or legal duties and complete fraud checks. After that, we delete or anonymise them where the law allows.

Yes. Send the request from your registered account path, tell us which field needs correction and include any proof we ask for. Once verified, we update the file and confirm the change.

Use the support route on the site or the email address in the footer. We log the request, note the action taken and keep the reply with the case record for traceability.

How 4nec2 Handles Your Data

Ways To Reach Us

How We Handle Records

Collected records

Cookie use

Sign-in checks

Retention

Correction requests

Privacy contact

Questions About This Policy

01 What does this policy cover?

02 Which records do you collect?

03 Why do you use cookies?

04 How long do you keep my records?

05 Can I ask for changes to my account data?

06 How do I contact you about privacy?

Related Pages