Reference

Privacy Policy for Indian Accounts

This page explains what we collect when you open an account, browse the site, or send a request.

Account dataCookie signalsLocal lawRequest access

How This Policy Applies In India

kalyanday Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

When you use kalyanday from India, this policy applies to the account data, device details, login events, cookie signals, and payment records that pass through your profile. We may use the details you enter during sign-up, the time and browser used to sign in, and the

1
record of UPI, Paytm, PhonePe, or Google Pay actions that move through your wallet area. We use that data to verify access, process requests, keep fraud checks moving, and respond when you ask for changes. Some records may also be shared with hosting, security, and payment
2
partners only when they need them to carry out those tasks, and only under controls that match this policy. We may also keep audit logs that show when a request was opened, handled, or closed, so we can trace changes if you ask later. If local
3
law limits a feature, we follow that rule and make the service available only where local law permits.

Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

CONTACT PATHS

Reach Us About Your Data

If you want to correct details, ask how your data is used, or raise a privacy concern, use the contact routes set inside your account.

Account form Use the form inside your account when you want a correction, a copy of stored details, or a privacy question sent to the right desk. We track each request by ticket, link it to your profile, and reply through the same route.

Email desk Send a clear message with your registered contact details and the change you want. That helps us confirm identity, reduce back-and-forth, and move the request to the privacy team without slowing the reply.

Chat route If you need quick help during local working hours, open chat and ask for the privacy team. We will point you to the right form, note the request, and keep the thread for records.

HANDLING STEPS

How We Handle Data Safely

We keep privacy work tied to a few clear rules: collect only what the account flow needs, use cookie data for session control and language settings, protect logins with standard checks, and…

Data use

We use contact details, device markers, login times, and wallet records to run the account, settle requests, and spot unusual access. We do not use that data for any purpose outside the scope stated in this policy.

Cookie signals

Cookies help us remember your language choice, session state, and whether you signed in on a shared device. You can clear them in the browser, though that may change how the page remembers you.

Account security

We compare sign-in attempts against recent device patterns and may ask for extra confirmation when a request looks unusual. That step protects your account and keeps private records from being changed by mistake.

Retention

We keep records for the period needed to handle access, payment, dispute, fraud, and legal duties. After that, we remove or archive them according to our internal deletion and storage rules.

Change requests

If your details change, send the new record through the account form and include enough context for verification. We only update data after we can match the request to your account.

Contact route

For access, correction, or deletion questions, write to the privacy team listed in your account area. Tell us what you want, and we will reply through the same channel where possible.

Privacy Questions You May Ask

This section answers common questions about the policy, the data we keep, and the choices you can make. The same rules apply whether you open the site on mobile or desktop, and we use the same contact routes for access, correction, and deletion requests. If local law changes what we may store or share, we adjust the policy and the account process together.

It covers the account details, device data, cookie signals, and payment records we handle when you use the site. It also covers how we respond to access, correction, and deletion requests where local law allows them.

Yes. Use the contact route in your account and ask for access. We will confirm your identity, gather the records tied to your profile, and send the reply through the same channel when possible.

Cookies help keep your session live, remember language settings, and reduce repeated logins on the same device. If you clear them, some settings may reset, but the policy still applies to data already collected.

We keep payment-linked records only as long as needed for processing, dispute handling, fraud checks, and legal duties. Those records are handled under the same privacy rules as the rest of your account data.

Only the people and service partners who need it for hosting, security, payment handling, or request processing can see it. Access is limited by role, and we keep a record of sensitive actions.

Send the change through the form or email in your account, add the updated details, and include enough context for us to match the request. We will update it after verification.

If local law changes what we may collect or keep, we update this page and adjust the account process. The updated text applies from the time it is posted.

Privacy Policy for Indian Accounts

Reach Us About Your Data

How We Handle Data Safely

Data use

Cookie signals

Account security

Retention

Change requests

Contact route

Privacy Questions You May Ask

01 What does this privacy policy cover?

02 Can I ask what you store about me?

03 Do cookies affect my sign-in?

04 Do you keep UPI, Paytm, and PhonePe records?

05 Who can see my data inside the company?

06 How can I ask for a correction?

07 What if local law changes?

Related Pages