Reference

Legal access, data and records

0tg keeps the legal side of access in one place so you can see how eligibility, data use, cookies and account records work before you open anything.

India only where law permitsState rules applyData and cookiesAccount recordsSupport on request

Explore Our Lobby Read FAQ

How the notice applies in India

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

This notice explains how we handle access, records, data and account checks for Indian accounts, and it applies only where local law allows the service to operate. If your state or territory sets a tighter rule, that local rule takes priority. We keep the legal wording

1
tied to your account, the way you contact us, and the records linked to actions inside the lobby, so you know what applies before you proceed. When we store data, it is used for account security, fraud checks, support handling and record keeping tied to lawful
2
access. If you ask for a copy, correction or closure step, we use the same support route and respond after confirming your identity. Payment labels such as UPI, Paytm, PhonePe and Google Pay may appear in account records, but the notice itself still follows the same
3
legal standard.

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

HELP ROUTES

Where to send legal queries

If you need clarity on the notice, use the contact route inside your account or the form on the site. We read requests about access, data correction, record copies and state-specific availability as legal queries, not general chat. When we need to verify you, we ask for the least details needed to match the request to your account and then keep the reply on the same channel.

Team online

Support inbox

Use the support inbox when you want the current notice, a copy of your request history or help matching a legal query to your account. We reply on the same thread after checking who is asking.

In-app form

Open the form from your account if you want to ask for data correction, closure steps or a state-specific access check. That route keeps the request tied to your profile and reduces back-and-forth.

Escalation desk

If your issue needs a second look, send it to the escalation desk with your account email and the relevant date. We use that path for disputes, record checks and any reply that needs a careful read.

RECORD CARE

How we handle data and access

We keep the legal side of your account tied to clear records, limited use and access checks.

Data use

We use account data to open sessions, verify requests, keep service logs and answer support queries. Access is limited to staff who need it for those tasks, and we do not treat the data as public.

Cookies

Cookies help with session handling, language choice and basic security checks. You can clear them in your browser, but some form fields may not hold their state after that.

Account security

We look for unusual sign-ins, repeated failed attempts and device changes. When that happens, we may ask for a fresh check so the account stays linked to the right person.

Retention

We keep records only for the period needed to meet legal duties, resolve disputes and answer support requests. After that, the data is removed or archived under our internal schedule.

Change requests

If your details change or you want a correction, send the exact field and the updated value through support. We confirm the request before making any edit that affects the account record.

Contact path

The same support route handles access questions, correction requests and any copy you need for your records. Add your account email, the date and a short reason so we can route it quickly.

Questions about legal access

These are the questions we hear most often about access, records and the way this page works. If your state has a different rule, that rule takes priority, and we do not switch that by device or browser. For anything that needs a personal check, use the support route and include the account email you used when you joined so we can match the request to the right record.

Access depends on local law. If the service is not allowed in your state or territory, we do not present it there. Where access is allowed, the same legal notice applies to your account and records.

We use the details you give us to verify access, handle requests, keep session logs and answer support queries. We do not use them for anything outside the legal purpose tied to your account.

Yes. Send the request through support with your account email and the date range you need. After we confirm the request, we share the record in the same channel or explain any legal limit.

No. Cookies help with sign-in, form memory and simple security checks. They do not change the notice, the legal wording or the rules that apply to your state.

We keep records only for the period needed to meet legal duties, settle disputes and handle support work. After that period, the record is removed or archived under our retention schedule.

Use support, name the field that needs fixing and share the updated detail. We check the request against your account before we make any change that affects the record.

Legal access, data and records

Where to send legal queries

Support inbox

In-app form

Escalation desk

How we handle data and access

Data use

Cookies

Account security

Retention

Change requests

Contact path

Questions about legal access

01 Who can access this service?

02 How do you use my data?

03 Can I ask for a copy of my record?

04 Do cookies change the legal terms?

05 How long do you keep records?

06 How do I request a correction?

Related Pages