Reference

Privacy Policy at k72

This page explains how we collect, use, store and protect the details tied to your account, including login data, device signals, messages and payment records.

DATA USECOOKIE CONTROLACCESS RIGHTS

Browse our lobby Read FAQ

How We Handle Your Data

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

This policy applies when you create an account, sign in, use cookies, contact support, or send or receive payment records tied to your account. We collect only the details needed for those actions: contact data, login logs, device signals, transaction references, and the messages you send

1
us. We use that data to run the account, process requests, detect misuse, protect access, answer privacy queries, and meet legal duties where local law requires it. We keep records for different periods depending on why they were collected. Short-lived logs help with security checks, while
2
account and transaction records can stay longer if we need them for disputes, audits, or legal retention. If your region allows a correction, access, or deletion request, we will review it after verification. For India payment context, records linked to UPI, Paytm, PhonePe, and Google Pay
3
are handled as account data, not as marketing material.

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

CONTACT PATHS

Where To Reach Our Privacy Team

If you want a copy of the data we hold, a correction, or a privacy question tied to your account, use the contact paths below.

Email the privacy team Send a message with your account email, the record you want to access or change, and a short reason. We use that to locate the file, confirm the request and reply after verification.

Use the contact form If you prefer a form, include your contact details, the subject line privacy, and the action you want. We route it as a data request so it does not sit in a general queue.

Reply through your thread When you already have an open conversation, reply from that same thread. It gives us the context we need to confirm identity, match the request to your record, and keep the process moving.

CARE AT WORK

Data Use, Cookies, Security, Retention

We keep the policy practical: collect only what the account needs, use cookies for session memory and security, and separate payment records from contact lists.

What we collect

We collect contact details, login records, device data, transaction references, and messages you send us only when they are needed to run the account or meet legal duties. We avoid collecting extras without a purpose.

Cookie control

Cookies help keep you signed in, remember language choice, and spot unusual access. You can clear them in your browser, though some functions may then ask for fresh verification before they work again.

Account safety

We use login checks, session controls, and internal access rules to keep personal data away from people who do not need it. If something looks unusual, we may pause the action until you confirm it.

Payment records

UPI, Paytm, PhonePe, and Google Pay records stay with your account history so we can confirm transfers, settle disputes, and meet audit duties. Those records are not used for unrelated messaging or profiling.

Retention rules

Different record types stay for different periods. Short-lived logs help with security checks, while account and transaction files can stay longer when the law or an unresolved issue requires it.

Change requests

If you want access, correction, or deletion where local law allows it, send the request with enough detail to locate your record. We may ask for extra verification before changing sensitive data.

Privacy Questions, Answered Clearly

These questions cover the parts of the policy you are most likely to ask about: what we collect, why cookies are used, how payment records are stored, how long files stay, and how to ask for a change. If local law gives you a right to request access, correction, or deletion, we handle it after we confirm the account.

We keep the details needed to run your account: contact data, login records, device signals, transaction references, and messages you send us. If a field is not needed for that purpose, we do not collect it.

Cookies help remember your session, language choice, and security state. They also help us spot repeated failed logins or unusual access. You can clear them in your browser, though some functions may ask you to verify again.

Payment records tied to UPI, Paytm, PhonePe, or Google Pay are kept with your account history so we can confirm transfers and settle disputes. They stay separate from contact lists and are used for account handling only.

When local law allows, you can ask for a copy of the data we hold, a correction, or deletion of certain records. We may need to confirm identity first so we do not change the wrong account.

Retention depends on record type and purpose. Short-lived logs may disappear sooner, while account and transaction records can stay longer for safety, dispute handling, or legal duties. We do not keep records longer than needed without reason.

Send privacy requests through the contact paths on this page and include enough detail to locate your account. If the request affects sensitive data, we may ask for extra verification before we act on it.

Privacy Policy at k72

Where To Reach Our Privacy Team

Data Use, Cookies, Security, Retention

What we collect

Cookie control

Account safety

Payment records

Retention rules

Change requests

Privacy Questions, Answered Clearly

01 What data do you keep from my account?

02 Why do you use cookies?

03 How are payment records handled?

04 Can I ask for a copy or correction?

05 How long do you keep my data?

06 How do I contact you about privacy?

Related Pages