Reference

Your Legal Position at m80

This page sets out how your account, data, and stored records are handled on m80.

India accessLocal lawRecord checksContact paths

Browse Lobby Read FAQ

How Local Law Shapes Access

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

Our legal position is simple: we only let an account move ahead where local law permits, and we do not route around regional restrictions. If a feature is not allowed for your location, it stays closed. The same applies to age, identity, and payment checks tied

1
to your account. For Indian access, we keep the language clear around UPI, Paytm, and PhonePe so you can see how wallet actions connect to your verified details. We also separate policy text from marketing copy. That means the page explains what we collect, how long
2
we keep it, who can see it, and how you can ask for a correction. If we update these terms, the current version is the one that applies from the time it is posted, unless local law says otherwise. We keep audit logs for account movement,
3
support chats, and consent changes so we can trace what happened if a dispute appears.

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

CONTACT PATHS

Where to Send Legal Questions

If you want to raise a legal or account-record query, we keep three paths open so the request lands in the right place.

Account message Use the message thread inside your account for legal questions, correction requests, or a record of what we replied. It keeps the request tied to the same profile, so we can check identity before making changes.

Email Send a written query to the address shown in your contact panel if you need a copy of records, a policy change request, or a follow-up after a support thread. We keep the chain for tracing.

Postal request If a signed letter is required for your case, use the postal address listed on the site. That route is useful for formal notices, document updates, and requests that must be kept on paper.

DATA HANDLING

How We Handle Data and Requests

We treat this page as a working record, not filler. The text connects your account to the data we keep, the cookies we set, the security checks we run, and the retention…

Data scope

We collect only the details needed to open, run, and verify the account, plus the logs required for dispute handling and fraud checks. Access inside the team is limited, and we do not reuse those records for unrelated purposes.

Cookie use

Cookies keep your session active, remember language choice, and help us spot unusual sign-in patterns. If you clear them, the page may forget your session and ask you to sign in again.

Account safety

We expect a strong password and a private device. If you use a shared phone or laptop, sign out after each session and avoid saving credentials in the browser, especially on public devices.

Retention

Records stay with us for the period needed for audit, tax, dispute, and operational checks. After that period, we remove or anonymise them where local law allows, so old files do not sit around without purpose.

Change requests

If your name, phone number, or other stored detail is wrong, send a correction from the registered contact path. We verify the request against the account before we update anything, so the record stays tied to you.

Who can read it

Only staff who need the record to do their job can open sensitive files. We log internal access, and if a query needs a closer check, we can point you to the exact contact route that handled it.

Questions About Rights and Access

These questions cover access, records, and how to reach us when something in your file needs attention. The answers stay tied to local law, your verified account, and the contact routes listed on this page. If a request is not allowed in your region, we will say so directly rather than leaving you to guess. That way you know what is possible before you send a request.

Access depends on local law and is available where local law permits. If a region is blocked, the page will not move forward there, and you should not try to bypass that restriction.

You can ask what we hold, why we hold it, and how long we keep it. You can also ask for a correction if a stored detail is wrong and you can prove the change.

Yes. Cookies keep you signed in, remember a few site settings, and help us spot odd access patterns. Clearing them may end the session or make the site forget your saved choice.

Use the registered contact path from your account or the email listed on the site. We check the request against the profile before we change any record, so the update stays attached to the right person.

Only staff handling your case can read the thread, and we keep internal access logged. If the matter needs a deeper check, we may ask for one more confirmation before sharing or amending a record.

We keep them for as long as needed for audit, tax, dispute handling, and account checks. After that, we remove or anonymise the records where local law allows, so storage does not continue without purpose.

Check this page again before using the account, because we update the text when local law or internal process changes. If an action is no longer allowed, we stop it and explain the next step.

Your Legal Position at m80

Where to Send Legal Questions

How We Handle Data and Requests

Data scope

Cookie use

Account safety

Retention

Change requests

Who can read it

Questions About Rights and Access

01 Can I access m80 from any part of India?

02 What can I ask about my account records?

03 Do cookies change how my session works?

04 How do I send a correction request?

05 Who sees my support messages?

06 How long do you keep legal records?

07 What should I do if the law changes?

Related Pages