Reference

Open y93 Legal Terms

Open this page to see the rules that shape your account, your data, and your access when local law permits.

Local lawAccount checksData useRecord changes
y93 Open y93 Legal Terms
REQUEST ROUTES

Explore request paths for legal help

When a legal request needs a human reply, we keep the path simple.

Email Use the address linked to your account and add the exact page or record…
Chat If you are already signed in, send the request through chat with the same…
Form For formal legal requests, use the contact form and include any proof we ask…
DATA HANDLING

Switch on data and access controls

We treat legal handling as part of account care, not a side task. Cookies help the page remember sign-in state and policy choices, while account checks help us verify corrections and withdrawal…

Data handling

We collect account details, device signals, and transaction references only when we need them to run the account, verify a request, or settle a dispute. Less data means less handling, so we keep the scope narrow and the file tidy.

Cookies

Cookies help us remember your sign-in state, language choice, and whether you already saw a policy notice. You can clear them in your browser, but some page settings may not stay saved, which means you may need to set them again.

Account security

Keep your password private and make sure your email and phone remain current. If you spot unfamiliar access, send the details right away so we can check the trail, lock the session, and stop further changes until we hear back.

Retention

We keep legal and account records only for as long as our operating, tax, audit, or dispute duties require. After that, we remove them or archive them under the current record rule and local law, with access kept narrow.

Change requests

To correct a name, contact detail, or account note, send the request from the registered email and include the proof we ask for. After verification, we update the record, keep a change log, and close the case on file.

Contact route

For legal questions, use the contact route on this page and name the policy area you want checked. That helps us route the case to the right team without delay, and it keeps the thread easy to follow.

Browse answers on legal access

These answers cover access, record use, corrections, and how we handle requests from India. If local law changes, we update the page and apply the latest wording to new cases. For requests that need identity checks, we ask for the minimum detail needed to confirm the account and move the matter forward. If you want a record copy, send the request through the same route you used for the account.

Yes. Use the registered email tied to your account and ask for the record you want. We confirm identity first, then share the relevant details or update them if your request is a correction, deletion, or status check.

Send the correction from your registered email with the right proof. We check the request against the account, update the file after verification, and keep a change log for future checks if the same detail comes up again.

Access depends on local law and is available where local law permits. If your location is not allowed, we block the account flow there. If the rule changes later, we follow the newest lawful position.

Yes. Cookies help remember sign-in state, language choice, and policy consent. You can clear them in your browser, but some settings may reset and you may need to confirm them again before the page feels familiar.

We keep records only as long as our operating, tax, audit, or dispute duties need them. After that, we remove or archive them under the current record rule and local law, and we do not keep extras.

They can. When a withdrawal needs verification, we may compare the request details with the account record and the payment trail. That helps us keep the legal and account file accurate and reduces later correction work.

Use the contact route listed here and say which policy section you want checked. If we need proof, we ask for the minimum detail and reply on the same route you used, so the thread stays simple.