Reference

India Account Terms and Access

We keep the legal side simple: who can open an account, how we use your records, and when we may ask for extra checks.

India lawData useCookiesVerification

What This Policy Covers

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

This page explains the terms that apply to account creation, data use, verification and access. We may ask for your name, phone number, device signals and payment references when we need to confirm a request or match records. If you use UPI, Paytm, PhonePe or Google

1
Pay, the name on the payment trail may need to line up with the account name before a change is accepted. Access and availability depend on local law, and we only offer the account where local law permits. We also keep logs for security, fraud checks
2
and dispute handling, then remove or anonymise them after the retention period ends unless a legal hold applies. If a rule changes, we update this page and use the latest version for your account from the effective date.

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

REQUEST ROUTES

Where to Send Requests

If you need help with a policy question, use the channel that matches the request. Email works for record access and corrections, the account form works for identity or contact changes, and…

Email request Send a message from the email tied to your account if you want to see stored data, correct a detail or ask what a clause means for your case. We verify the address before we reply.

Account form Use the form inside your account when the request touches your phone number, payment trail or consent setting. That path keeps the request linked to the right profile and reduces delays from mismatched details.

Postal letter For paper requests, send a signed letter with your account name, registered phone and the change you want. We log the request on arrival and respond through the same route where possible.

RECORD KEEPING

How We Handle Your Records

Our handling is built around a small set of checks: we collect only what we need, we keep logs for a limited period, and we use cookies for sign-in state and basic…

Data handling

We keep profile details, login traces and payment references only for account servicing, verification and dispute handling. Those records are not used for a different purpose without a clear policy change and a fresh legal basis where required.

Cookie use

Cookies help us keep you signed in, remember language choice and spot unusual sign-in attempts. If you clear them, your session may end and a few preferences may reset the next time you open the page.

Security checks

When a phone number, device or payment reference changes, we may ask for a fresh check before we accept the update. That step helps us keep the account linked to the right person.

Retention periods

Support chats, verification logs and transaction traces stay only as long as we need them for service, security or legal retention. After that, the record is removed or anonymised where our systems allow.

Change requests

If you want a correction, restriction or deletion where allowed, send a written request from the registered contact path. We may ask for proof before any change reaches the live record.

Access questions

For questions about how a record is used, contact the support path on this page with your account email and phone number. We will tell you the next step that applies to your request.

Common Questions About Your Account

We keep this section short so you can check the points that matter before you open an account. The questions below cover what we store, how cookies behave, who can ask for changes and when access may pause under local law. If your request is personal, use the contact paths listed here and include the account details that let us match the right record.

We keep the details needed to run the account, confirm identity and handle support, such as profile data, login history and payment references. If a record is no longer needed, we remove or anonymise it under the applicable retention rule.

Yes. Send the request from the registered email or phone number, and we will confirm identity before sharing what can be disclosed under local law and our retention limits.

Cookies remember session state, language choice and some security flags. Clearing them can end the session, reset a few settings and make us ask you to sign in again.

Tell us through the account form or the registered email, then complete the check we send. We update the record only after the new detail matches the account and the security step passes.

No. Payment references can help us confirm a request, but the policy stays the same. Whether you use UPI, Paytm, PhonePe or Google Pay, the same account checks apply.

Access can be limited when local law requires it, when identity cannot be confirmed, or when security checks flag unusual activity. If that happens, we will show the next step that is available.

India Account Terms and Access

Where to Send Requests

How We Handle Your Records

Data handling

Cookie use

Security checks

Retention periods

Change requests

Access questions

Common Questions About Your Account

01 What records do you keep for my account?

02 Can I ask for a copy of my records?

03 How do cookies affect my account?

04 What happens if my contact details change?

05 Do UPI, Paytm, PhonePe or Google Pay change these rules?

06 When can access be limited?

Related Pages