Reference

Terms & Conditions for India accounts

These Terms & Conditions set the rules for your z400 account, including how you access it, accept updates we publish from time to time, and use the login…

IndiaLocal lawAccount useUPI
z400 Terms & Conditions for India accounts
CONTACT PATHS

Where to send clause questions

If a clause feels unclear, send us the part you want checked and the account email linked to it.

In-account chat Use in-account chat for a clause query, an access concern, or a request to restate a condition in simpler language. We can trace the note to your account and reply with the current text.
Email desk Email works well when you want a copy of the current wording, a record of your question, or a follow-up after a change notice. Include your account email and the clause you want checked.
Request form The support form helps when you need a correction, a retention query, or a note attached to your file. It gives us enough context to route the request without extra back-and-forth.
CARE PRACTICES

How we handle your terms data

We keep the records needed to run account terms properly: your acceptance logs, change history, identity checks, and support messages tied to a request.

Acceptance log

We store the time, device sign-in, and version number tied to each acceptance so we can show which text was current when you agreed. That record helps resolve later questions about timing or scope.

Cookies

Session cookies keep you signed in, remember language choices, and help us spot repeated failed logins. They do not rewrite the agreement, but they do support a cleaner account flow on your next visit.

Account security

We may ask for extra checks if a login looks unusual, if a device changes suddenly, or if a request touches sensitive account data. That protects the terms relationship without asking for extra steps on every visit.

Retention

We retain terms records only as long as the legal time frame, dispute window, or account history requires. Once that period ends, we remove or anonymise data that no longer has a clear account purpose.

Change requests

If you want a correction, send the exact clause, the date you saw it, and the account email tied to the record. We can then check whether the request affects stored terms history or just your contact details.

Contact trail

Every request leaves a support trail so we can show what was asked, when we answered, and which version we sent back. That trail matters if you later want the same clause checked again.

Questions about our terms

These questions cover the parts people ask about most: what you accept, how updates work, which law controls access, and how to contact us if a clause needs another look. We keep the answers short so you can find the rule fast, and each one points back to the current page version we publish for your account today without repeating the same rule in every answer.

You agree to the current page, any linked rules that apply to your account, and the checks we need to confirm identity, access, and lawful use. If a clause changes later, the posted version governs future use.

Yes. Access depends on local law and is available where local law permits, so a state or regional rule can limit what you can do, when you can do it, or whether a feature is available at all.

We post the new wording on this page and the updated text becomes part of the agreement from the posted date. If the change affects your account flow, we may also show a notice inside the account.

Send the exact detail that needs fixing and the account email linked to it. We check the record, confirm what can be changed, and keep the earlier version only when the law or dispute handling requires it.

No. UPI, Paytm, and PhonePe are shown as local context chips for supported rails. They do not override the agreement, and any payment step still follows the current posted terms.

Use in-account chat, email, or the support form with the clause number or copied sentence. That lets us answer against the exact wording you saw and keeps the request tied to your account.