Reference

Privacy Policy for Your Account Data

This Privacy Policy gives you a clear account-data map: sign-in records, device checks, cookie choices, and payment data linked to UPI, Paytm, PhonePe or Google Pay.

Account dataCookie choicesUPI recordsSupport contact

Browse Lobby Read FAQ

India Data Practices at kr730

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

Your privacy on our India-facing site is handled through defined collection points, not hidden guesses. We collect the data needed to open your account, keep your wallet activity traceable, process support requests, apply security checks, and meet legal duties that may apply in your region. Payment

1
references from UPI, Paytm, PhonePe and Google Pay are used to match transactions with your wallet, confirm status, and resolve failed or delayed entries. We do not sell your account data. Where we rely on partners for hosting, analytics, fraud screening or payment routing, we share
2
only the fields needed for that task under contract terms. If access or eligibility is discussed, it depends on local law and is available where local law permits. You can contact us to request access, correction, deletion or a copy of your data, subject to records
3
we must keep.

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

CONTACT ROUTES

3 Ways to Reach Privacy Support

Privacy requests need a clear route, so we keep contact choices inside the account area and on kr730.com.

Privacy email Send policy requests from the email linked to your account. Include your username, the data action you want, and any payment reference only when it helps us locate the record.

Live chat Use chat when your question is about cookie settings, login alerts or a recent change to your personal details. We can explain the policy path, then move sensitive requests to email.

Account form The account form helps us verify ownership before we act on correction or deletion requests. Upload only what we ask for, because extra files can slow the privacy check.

ACCOUNT SAFETY

6 Privacy Checks Behind Your Account

We treat the Privacy Policy as an operating rulebook for every account action, from sign-in checks to wallet records.

Collection scope

We collect account identifiers, contact details, device signals, wallet references and support messages. We do not ask for unrelated documents, and we trim requests to the fields needed for account, security or legal tasks.

Cookie choices

Cookies help the site remember your session, language and security state. You can change browser settings, and we explain which cookies are needed for login compared with analytics or preference tools.

Payment records

UPI, Paytm, PhonePe and Google Pay references are stored with time, status and wallet link. This lets us trace pending entries without exposing your full payment app details to support staff.

Account security

When a password reset, new device or unusual login appears, we may use extra checks before sharing data. These steps protect your privacy request from anyone who cannot prove account ownership.

Retention periods

Some records are kept for tax, fraud prevention, dispute handling or legal duties. When that need ends, we delete, anonymise or archive data according to the retention schedule behind this policy.

Change requests

You can ask us to correct details, change contact choices, delete eligible records or send a data copy. We confirm identity first, then reply with the action taken or the reason for refusal.

Privacy Policy Questions Before You Join

Before you open an account, read this Privacy Policy so you know how data moves through sign-in, wallet, support and cookie systems. The answers below cover your rights, storage, UPI references, Paytm and PhonePe records, account checks and contact steps. If your question is more specific, send it through the privacy route inside your account or from the email you used with us.

It covers data you give us, data created by account activity, device signals, cookie records, payment references, support messages and security checks. It also explains why each category is used and how long we keep it.

Payment records help us match a transaction to your wallet, trace delayed entries and respond to disputes. We store references, status and timing, not full app credentials or private balances from your payment service.

Yes. Send a request from your account email and tell us whether you want access, correction, deletion or a copy. We verify ownership first, then respond subject to legal records we must retain.

Cookies keep you signed in, remember preferences and help detect risky sessions. Some are needed for account security; others support analytics. You can manage browser settings, though certain changes may affect login.

We may share limited fields with hosting, payment, analytics, fraud screening and customer service partners. Each partner receives only what is needed for its role, and we use contract terms to restrict further use.

We keep records for as long as the account purpose, dispute handling, fraud prevention, tax or legal duty requires. When retention is no longer needed, we delete, anonymise or archive the record.

Privacy rights and account access can vary by local law. When access or eligibility is discussed, it depends on local law and is available where local law permits, and we apply the relevant request process.

Privacy Policy for Your Account Data

3 Ways to Reach Privacy Support

6 Privacy Checks Behind Your Account

Collection scope

Cookie choices

Payment records

Account security

Retention periods

Change requests

Privacy Policy Questions Before You Join

01 What data does the Privacy Policy cover?

02 How are UPI, Paytm and PhonePe records used?

03 Can I ask for my account data?

04 How do cookies affect my privacy?

05 Who receives my data outside kr730?

06 How long do you keep my records?

07 Does privacy change by location in India?

Related Pages