Reference

Open your matkaboss Privacy Policy

Your account data, UPI, Paytm and PhonePe payment records, cookies and support messages are handled under this Privacy Policy before you open your account.

India account privacyUPI data handlingCookie choicesRequest changes
matkaboss Open your matkaboss Privacy Policy
CONTACT PATHS

Check privacy contact paths

Privacy questions should reach the team that can trace your account record, not a general inbox.

Email privacy desk Write to the privacy address shown in your account area with the subject line clearly naming your request. We use email for data access, correction, removal checks and copies of privacy responses.
Live chat handoff Start with chat if you need to confirm which record is affected. The agent can verify basic account details, then route the privacy request to the correct queue for written handling.
Account security path Use the security option when you suspect unauthorised access, changed contact details or unknown payment activity. We can freeze sensitive changes while checking login records, device signals and wallet events.
POLICY CARE

Manage your data choices

We keep this policy practical by tying each privacy step to a real account record. Cookies help remember sign-in state and measure page errors; payment logs help reconcile UPI, Paytm and PhonePe…

Data we collect

We collect account details you provide, verification documents where required, wallet records, device data, cookies, support messages and transaction timestamps. Each category is linked to account access, security, payments or legal recordkeeping.

Cookies and devices

Cookies help keep you signed in, remember basic preferences and detect unusual sessions. Device signals, browser type and IP address also help us spot repeated failed logins or account access from unexpected locations.

Payment privacy

UPI, Paytm, PhonePe and Google Pay records may include masked identifiers, bank response codes, references and timing data. We use these records to match wallet entries, answer disputes and reduce duplicate processing.

Security checks

We use login history, password reset records and verification status to protect your account from unauthorised changes. Access to sensitive records is restricted to trained staff who need it for a defined task.

Retention rules

Some records are kept longer because payment, tax, anti-fraud or dispute duties require them. When a record no longer serves a lawful purpose, we delete, mask or aggregate it where our systems allow.

Change requests

You can ask for access, correction, account data removal review or cookie help. We verify your identity first, then respond with what we can change and what must remain for lawful records.

Ask about privacy rights

These answers explain how your privacy requests work after you create an account or contact us. They cover data access, payment records, cookies, retention, security checks and lawful sharing. If your request concerns a specific wallet entry, withdrawal check or support chat, send the date, reference number and registered contact detail so we can find the record quickly.

We collect the data needed to create and protect your account, process wallet activity, answer support chats and meet legal duties. This can include contact details, device signals, payment references, verification files and cookie data.

Payment records help us match wallet entries with bank or app responses, trace failed or pending requests and answer disputes. We normally store references, status codes, timestamps and masked identifiers, not your full banking details.

Yes. Send a request through the privacy contact path with your registered email or mobile number. We may verify your identity before sharing account data, because the response can include sensitive wallet and security records.

You can ask us to correct eligible details such as contact data or profile fields. Some records, including completed payment logs or verification outcomes, may need to stay unchanged to preserve legal and accounting accuracy.

Cookies support sign-in, page performance checks, security detection and preference storage. You can control browser cookies, but blocking some cookies may affect login, account protection prompts or the way wallet pages load.

We share data only when needed for payment processing, identity checks, hosting, analytics, security reviews, support tools or lawful requests. Each partner receives only the data needed for its assigned purpose.

Access depends on local law and is available where local law permits, but privacy handling still applies to records connected with your account or enquiry. We may retain certain records even if access changes later.