Reference

Privacy Policy for your account

Before you open your account, this Privacy Policy explains what data we collect, why we use it, and how you can ask us to correct or remove it.

Account data useCookie choicesUPI record handlingPaytm and PhonePe context
u3425we Privacy Policy for your account
CONTACT ROUTES

Three ways to ask privacy questions

Privacy requests work faster when you contact us through the same account email or phone number you use with the site.

Email privacy desk Write to our privacy mailbox with your account ID, registered mobile number, and the privacy request you want us to handle. We reply with the next step, any identity check needed, and the expected response window.
Live chat handoff If you start in chat, ask for a privacy handoff rather than sharing sensitive documents in the message window. Our team will move the request to a safer channel tied to your account.
Account message trail Use your account message history when the request relates to wallet records, login alerts, or cookie choices. Keeping the request inside your account helps us match the record without asking for extra personal data.
HANDLING RULES

Six privacy controls we follow

We treat the Privacy Policy as an operating rule, not a page added after the account flow.

Data we collect

We collect account identifiers, contact details, device signals, login records, payment references, cookie choices, and support messages. We use these records to run the account, secure access, process requests, and answer privacy questions.

Cookie handling

Cookies help us remember your session, protect against repeated failed logins, and understand basic site use. You can manage cookies in your browser, though some account security checks may need essential cookies to work.

Account security

Access records help us spot unusual login patterns, password reset attempts, and device changes. When a privacy request concerns security data, we verify the account holder before sharing or changing anything linked to the account.

Payment records

UPI, Paytm, PhonePe and Google Pay references may be stored as transaction records, not wallet passwords. We use them to match deposits, check withdrawal requests, and resolve payment queries raised from your account.

Retention periods

Some records are removed when no longer needed, while others may be kept for legal, security, payment or dispute reasons. When retention applies, access is limited and the record is not used for unrelated contact.

Change requests

You can ask us to correct wrong contact details, update consent choices, or check whether a record can be deleted. If a legal duty prevents deletion, we explain the reason and limit further use where possible.

Common questions about your privacy

These answers explain how our Privacy Policy works when you create an account, use cookies, contact support, or connect a payment method. They are written for everyday account questions, not legal jargon. If your request involves sensitive data or a disputed record, contact us from your registered email or signed-in account so we can verify you before acting.

It covers account details, contact data, login records, device signals, cookie choices, payment references, and support messages. We use these records to operate your account, protect access, process requests, and respond to privacy queries.

We keep limited payment records to match UPI, Paytm, PhonePe or Google Pay activity with your account. These records help us confirm requests, handle disputes, and meet recordkeeping duties that may apply in India.

Yes. Send the correction request from your registered email or signed-in account and include the field that is wrong. We may verify your identity before changing contact details, payment references, or security-related records.

Cookies support session access, login protection, language preferences, and basic site measurement. You can adjust browser cookie settings, but essential cookies may still be needed for account security and signed-in functions.

Only the teams needed to handle the request, verify the account, or resolve the linked record can view it. We limit access by role and avoid sharing your request with staff who do not need it.

Retention depends on the record type and the reason it was collected. Some data may be removed after account use ends, while payment, legal, security or dispute records may need to stay longer.

Use the privacy email, account message route, or chat handoff described on this page. Include your account ID and request type, but do not send wallet passwords, full card data, or unrelated documents.