Reference

Privacy Policy for Your zve1 Account

Our Privacy Policy sets out how we collect, use and protect the data you share while opening your account, managing your wallet, and using UPI, Paytm, PhonePe or…

Account data handlingUPI and wallet recordsCookie choicesPrivacy request paths
zve1 Privacy Policy for Your zve1 Account
CONTACT ROUTES

Three Routes for Privacy Requests

Privacy requests work better when they come from the same email, mobile number, or signed-in account that you use with us.

Email privacy desk Send your request from the email linked to your account and include your registered mobile number. We use those details to match the request before sharing or changing account records.
Signed-in chat Open chat after you sign in if you need help finding data choices or cookie settings. Our team can point you to the right privacy path without asking for wallet passwords.
Security escalation If your request involves suspected account access by another person, tell us quickly. We can start a security check, protect the account, and explain which privacy records may be affected.
ACCOUNT SAFETY

Six Controls Behind This Policy

We treat privacy as part of daily account operations, not as a separate form hidden away from you.

Account data

We collect the details needed to create and maintain your account, such as name, mobile number, email address and login history. Extra documents may be requested only when verification or law requires them.

Payment records

UPI, Paytm, PhonePe and Google Pay references are used to match wallet activity, verify requests and resolve disputes. We do not need your app passwords, UPI PIN or saved banking credentials.

Cookie choices

Cookies help us keep you signed in, remember device settings and detect unusual access. You can adjust browser controls, though some account functions may work differently if required cookies are blocked.

Login protection

We monitor device signals, failed sign-ins and session changes so we can detect account misuse. If a privacy request looks unusual, we may ask extra questions before acting on it.

Retention schedule

Different records are kept for different periods. Support messages may close sooner, while payment references, security logs and dispute records may remain longer when legal or safety reasons require it.

Change requests

You can ask us to correct account details that are wrong, incomplete or outdated. Before making changes, we verify ownership so another person cannot alter your privacy record.

Privacy Policy Questions Before You Join

Before you open an account, you should know what data we ask for, why we keep it, and how you can contact us about it later. These answers explain the privacy choices linked to account creation, payment references, cookies, data changes, retention and support checks in plain language for India.

We may collect your name, mobile number, email address, sign-in records, device signals and account activity. If payment verification is needed, we may also store UPI, Paytm, PhonePe or Google Pay references.

Yes, you can ask for a copy of eligible account data by contacting us through a verified route. We confirm account ownership first, then explain what can be shared and what must stay restricted.

We use payment references to match wallet activity, support queries and security checks. We do not ask for your UPI PIN, Paytm password, PhonePe password or Google Pay passcode under this policy.

Cookies help keep your session active, remember basic settings and detect unusual sign-in patterns. You can manage browser cookie controls, but some account features may not work normally if required cookies are blocked.

Retention depends on the type of record and the reason it was collected. Some support records close quickly, while payment references, security logs or dispute material may stay longer for legal reasons.

Yes, you can request corrections when account details are wrong or outdated. We verify the request through your registered contact details before changing records, so your account cannot be altered by another person.

Only the teams that need to handle your request, security check or legal duty can access it. We limit access, record internal handling, and avoid asking for wallet passwords or payment app passcodes.