Reference

g42 legal terms for India account access

g42 keeps account access tied to local law, and any use stays available only where local law permits.

India accessLocal lawIdentity checksRecord requests

How local law shapes access

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

When you join from India, we first check the legal position in your location before we allow access. If the rules permit it, we may ask for identity proof, contact details or payment ownership proof so the account can be matched cleanly to the person using

1
it. UPI, Paytm and PhonePe references are used only to confirm a record, reduce repeat entries and support dispute handling; they are not treated as public data. We keep the shortest record that still lets us answer a request, meet a legal duty and protect the
2
account against misuse. Cookies and device markers help us recognise a return visit, keep the session stable and spot strange access patterns. If we change this policy, the updated version applies from the date it is posted, and access after that date means you accept the
3
newer wording where local law permits. If you need a copy, correction or closure request, use the contact route in your account so we can verify it against the right record.

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

REQUEST ROUTES

Send legal requests our way

If you want a copy of a record, a correction, a closure request or a question about access, use the channel that matches the account and send it from the email on…

Email desk Send written legal requests to the email tied to your account. We use that address to confirm identity, log the request date and reply with the next step without sharing your records with the wrong person.

Secure form Use the form inside your account when you want a correction, copy or closure request. It matches your message to the right profile and keeps a clean trail for audit and dispute handling.

Postal request If post works better for you, send the request to the address listed in your account area. Add your name, account email and the change you want, so we can verify it against our records first.

DATA HANDLING

Records, cookies, and account safety

Our policy work starts with narrow collection, then matching, then retention control. We use session records, login history and relevant payment traces only when they are needed to verify an account or…

Data use

We collect the details needed to run the account, confirm identity and answer legal requests: contact data, device logs, session records and payment traces where relevant. We keep access narrow and limit staff visibility to what the task needs.

Cookie use

Cookies help us remember session state, spot repeated logins and keep the request flow steady as you move through the site. You can clear them in your browser, but that may mean we ask for a fresh check next time.

Login safety

Your password, device and login history matter. We expect you to keep credentials private, and we may step up verification if a sign-in looks unusual or comes from a new device, browser or location.

Record retention

We retain records only as long as needed for the stated purpose, legal duty, chargeback handling or dispute handling. Once the period ends, we delete or anonymise the record according to our internal schedule.

Change requests

If you want a correction, restriction or deletion where the law allows it, send the request from the email on the account and say exactly what should change. We answer after matching the request to the record.

Contact path

For any policy request, use the contact route linked in your account settings. We keep that path current so you can reach the right team without sending private details through unrelated channels.

Questions on access and records

These answers cover access, record checks, cookie use and change requests. If your location changes or the law changes, the applicable rule can change with it, so we may ask for a fresh verification before we act. Use the questions here to see which contact path fits each request and what proof we need before we make a change.

Access depends on local law and is available where local law permits. If your location or the rules tied to it change, we may pause, limit or reopen access after a fresh check on the account record.

We keep the details needed to verify identity, handle requests, settle disputes and maintain audit logs. That usually means contact data, login records, device markers and payment traces connected to the account history.

Yes. Send the request from the contact on file, say what needs to be corrected and attach anything that helps us confirm the change. We act after we match the request to the account record.

Cookies help maintain session state, remember your preferences and flag unusual activity. They do not replace account verification, and clearing them may make us ask for a fresh sign-in or an extra check.

We keep records only for the period needed for the stated purpose, legal duty or dispute handling. After that, we delete or anonymise them in line with our retention schedule and any local requirement.

Use the email or form linked to your account, since it lets us match your request to the right record quickly. If the request needs extra proof, we will ask for it through that channel.

If a request touches identity, record corrections or deletion, we may ask for a supporting document from the same contact on file. We only ask for what the request needs, then close the loop once the record matches.

g42 legal terms for India account access

Send legal requests our way

Records, cookies, and account safety

Data use

Cookie use

Login safety

Record retention

Change requests

Contact path

Questions on access and records

01 How does local law affect access?

02 What records do you keep?

03 Can I correct my details?

04 How do cookies affect my account?

05 How long do you keep records?

06 Who should I contact for a legal request?

07 What if you need extra proof?

Related Pages