Reference

Legal terms for India accounts

o77 sets out the rules that shape how you open, use, and close your account, how we handle data, and how we respond to change requests.

Local lawData useVerificationContact path

Explore lobby Read FAQ

Policy terms that apply here

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

Access to o77 depends on local law and is available where local law permits. When you create an account, we may ask for details that help us keep the record accurate, match wallet activity to the right profile, and reduce mistakes. The exact checks can change

1
by region, device, and payment route. If you ask us to change a name, number, or login detail, we may request proof before we update the record. The same legal frame applies whether you use UPI, Paytm, PhonePe, or Google Pay, and we keep the final
2
position tied to the payment rail and the local rules that apply to you.

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

REQUEST CHANNELS

Where to send legal requests

If you need a clause explained, a record corrected, or a legal request logged, our support path keeps it in one thread. We separate access questions from change requests so you do not repeat the same details. If local law limits a request, we say so clearly and point you to the next step. Messages stay attached to your account for follow-up.

Team online

Email request

Send a message with your account ID, the clause you want checked, and the change you are asking for. We keep the thread tied to your record so the reply matches the exact legal point you raised.

In-app form

Use the in-app form when you want to correct contact details, ask for a copy of stored data, or flag a consent question. The form helps us sort the request before a human reply.

Proof check

If a request needs extra proof, we say which document or confirmation step is required and why. You can track the reply in the same thread instead of starting over by email.

RECORD CARE

How we handle records safely

We keep legal requests tied to the account record, use cookies to remember session state and language choice, and store activity logs only as long as needed for dispute checks or legal…

Data map

Account details, device signals, login timestamps, and payment references are kept together only for the purpose they were collected. That helps us answer legal requests without pulling unrelated records into the thread.

Cookies

We use cookies to remember session state, language choice, and consent settings. If you clear them, the site will ask again on your next visit, including any legal prompts tied to your account.

Login checks

When a sign-in looks unusual, we may ask for a fresh password entry, OTP, or device confirmation before anything sensitive opens. That keeps account changes tied to the person asking.

Record retention

Some records stay longer when law, dispute handling, or audit needs require it. After that window, we delete or anonymise what we can, keeping only what the rule still asks us to hold.

Change requests

If your name, phone number, or email changes, send the update request through support with matching proof. We review the request against the current record before making any legal change.

Contact trail

Each legal query keeps a single thread, a timestamp, and the reply history so you can see what was asked and what was approved. That trail also helps us avoid mixed instructions.

Questions on access and records

These questions cover access, records, cookies, corrections, retention, and contact steps. We keep the answers short so you can check the legal position before you continue. If your situation depends on local law, the answer always points back to what is permitted in your region and what proof we may need.

Access depends on local law and is available only where that law permits it. If your region is not supported, the entry path stops before account creation, so you do not need to guess.

We keep account details, login logs, device signals, payment references, and support messages that are needed for operation, dispute handling, or legal duties. We do not keep more than the task calls for.

Yes, if the request matches the current account and you complete the verification we ask for. Some fields can change right away; others stay fixed until we confirm the record is correct.

Cookies remember your session, language choice, and consent state, so the same prompts do not appear on every page load. You can clear them, but the legal settings will need to be set again.

We keep records only as long as needed for disputes, compliance duties, and account safety. After that, we remove or anonymise what the rule allows, while keeping any part we must retain.

Use support, include your account ID, the clause or record you want checked, and the change you need. We answer in the same thread so you can follow the decision from start to finish.

Legal terms for India accounts

Where to send legal requests

Email request

In-app form

Proof check

How we handle records safely

Data map

Cookies

Login checks

Record retention

Change requests

Contact trail

Questions on access and records

01 Who can access the site?

02 What records do you keep?

03 Can I change my details later?

04 How do cookies affect legal pages?

05 How long do you keep my records?

06 How do I send a legal request?

Related Pages