Reference

Privacy Policy for Indian Account Data

This page sets out how kalyanfinal handles the details you share when you open an account, sign in, or send a privacy request.

Account dataCookie useLocal lawRequest changes
kalyanfinal Privacy Policy for Indian Account Data
REQUEST PATHS

How to Reach Our Privacy Desk

If you want a copy of the data we hold, need a correction, or want to ask about cookies or retention, we keep the request paths simple.

Email Send your privacy request to the address listed on the page if you want access, correction, or deletion where law permits. Include your registered mobile number so we can match the record quickly.
Account Form Use the form in your account area when you need to question a cookie record, a login trace, or a stored payment reference. We route it to the team that handles privacy changes.
Postal Mail If your request needs extra proof, we may ask for a signed letter and one matching account detail before moving ahead. That keeps the change tied to the right record and prevents misuse.
STORAGE PRACTICE

How We Handle Your Data

We treat privacy as part of account operation, not as a separate box to tick.

Data Use

We collect only the details needed for account creation, device security, support handling, and payment matching.

Cookie Use

Cookies help remember session state, language choice, and page flow.

Account Checks

When you request a change, we may compare your registered mobile number, recent login signals, or a payment reference.

Retention

We keep records only for the period needed for service, dispute handling, tax, or other legal duties.

Change Requests

If you want correction, access, or deletion where law permits, send a clear request with the account details we need…

Contact Route

For privacy matters, use the contact route listed here and include enough detail for us to identify the record.

Questions About This Policy

The questions below cover the privacy points people ask us about most often: what we collect, why we keep it, how long it stays, and how you can request a correction or deletion where local law allows. If your situation is tied to a payment record or a login trace, the answer explains how we handle that too.

It covers the details we collect when you create or use an account, send a request, or load pages that rely on cookies. It also explains how we store, limit, and remove records where local law permits.

Yes. Cookies help remember your session, language choice, and page state, and they support basic safety checks. You can clear them through your browser, though some actions may ask you to sign in again.

Yes. Send the account email or mobile number, name the field that needs correction, and we will verify the request before changing it. If a legal retention rule applies, we explain what can be updated.

We keep records only for the period needed for account handling, support work, dispute checks, tax duties, or other legal reasons. After that period ends, we delete or anonymise the data we no longer need.

Payment traces linked to UPI, Paytm, PhonePe, or Google Pay are used to match the transaction to the right account, handle errors, and keep audit trails. We store only the details needed for those tasks.

Only staff who need the record for support, security, or legal handling can access it. We keep access narrow, and we ask for extra proof before sharing or changing anything sensitive.

Use the privacy contact path listed on this page and include the account detail that helps us locate the record. We will reply with the next step once we check the request.