Reference

Privacy Policy for your account

Our Privacy Policy explains how matkaguru collects, uses and protects the data linked to your account, wallet checks, UPI, Paytm, PhonePe and Google Pay activity, device sessions and…

Account dataUPI recordsCookie choicesPrivacy contact
matkaguru Privacy Policy for your account
CONTACT ROUTES

Reach us about privacy requests

Privacy questions need a clear route, not a generic inbox. When you contact us, include your registered mobile number or email, the payment name involved if relevant, and the request you want…

Account email Use the privacy contact email shown inside your account area for correction, deletion or copy requests. We check the account link before acting, because payment records and login data must stay protected from unrelated requests.
Live chat handover If you start in chat, ask the team to mark the conversation as a privacy request. We may move the matter to email when identity checks, payment references or written confirmation are needed.
Payment query tag For UPI, Paytm, PhonePe or Google Pay privacy questions, share the transaction reference without sending full bank data. We use that reference to locate records while reducing extra personal data in chat.
DATA CARE

How we handle your data

The Privacy Policy is written around the account flow you actually use: login, wallet action, device session, support contact and withdrawal verification.

Data we collect

We collect account identifiers, contact details, login signals, device data, wallet references and support messages. This helps us run your account, answer privacy requests, check payment status and protect access against suspicious activity.

Cookie use

Cookies help keep you signed in, remember basic preferences and measure page function. You can manage cookies in your browser, but blocking some cookies may affect login, wallet checks or privacy request forms.

Account security

We use verification steps before releasing or changing personal data. If a request concerns UPI, Paytm, PhonePe or Google Pay records, we match account details before any privacy action is confirmed.

Retention periods

We keep data only for account operation, payment records, security, dispute handling and legal duties. Some records may remain after closure when law, payment reconciliation or fraud prevention requires a longer period.

Sharing controls

We share limited data with processors that help with hosting, payments, verification, support and security checks. Each share is tied to a defined purpose, and we avoid sending data that is not needed.

Change requests

You can ask us to correct account data, request a copy or raise deletion questions. We verify the account first, explain what can be changed and tell you if a legal record must remain.

Questions about this Privacy Policy

Use these answers when you want a quick privacy response before contacting us. They explain what we collect, why we keep it, how payment records are treated and how you can ask for a privacy action on your account. For complex cases, we will reply through a verified contact path.

It covers your account identifiers, contact details, login records, device signals, wallet references, payment status, support messages and verification data. We use these records for account operation, security checks, payments and privacy request handling.

We store transaction references, timing, status and account matching data needed to confirm payment activity. We do not ask you to send full bank data in chat, and we limit access to payment records.

Yes, you can send a verified request through the privacy contact path. We may ask you to confirm your registered email or mobile number before sharing account data linked to your profile.

You can ask us to correct details that are inaccurate or outdated. Some fields may need verification, especially when the change affects payment records, withdrawal checks, account ownership or security review.

You can raise a deletion request, and we will review what can be removed. Certain records may need to remain for legal duties, payment reconciliation, dispute handling, fraud prevention or account security.

Cookies support login, page function and basic measurement. You can control them through your browser, but some settings may affect account access, wallet checks or forms used for privacy requests.

Use the privacy contact email inside your account area or ask chat to route the case to privacy support. Include your registered contact detail and avoid sharing full bank data in messages.