Reference

Your 10crics Data, Clearly Explained

Your account data, KYC records, cookies and payment details for UPI, Paytm, PhonePe and Google Pay are covered by this Privacy Policy before you open your account on…

KYC data explainedCookie choicesUPI privacy contextIndia law framing
10crics Your 10crics Data, Clearly Explained
CONTACT CHANNELS

Privacy Help When You Need It

If you need to ask about personal data, cookie settings, KYC records or a correction request, contact us through the account paths we make available inside 10crics.

Privacy email requests Email us from the address linked to your account and include your username, the data request you want handled, and any order or transaction reference that helps us trace the record without extra back-and-forth.
Live chat privacy help Use chat after signing in when your question involves cookie settings, login alerts, KYC upload history or wallet privacy. We may ask account checks before discussing personal data, so keep your phone and email available.
Document change channel If your name, address or ID record has changed, contact support before uploading replacements. We will tell you what proof is needed, where to send it, and when outdated copies are removed.
ACCOUNT CARE

How We Handle Privacy Requests

Our privacy handling is built into account checks, wallet reconciliation, cookie controls and security logs rather than kept as a separate promise.

Data collection

We ask for account details, contact data, device signals and service usage data only where they support login, verification, wallet records, fraud checks, customer care or legal duties tied to your region.

KYC handling

Identity documents are viewed by trained staff or verification partners, not open teams across the company. We store audit trails showing when checks happened, who handled them, and why a fresh copy may be requested.

Payment records

UPI, Paytm, PhonePe and Google Pay references help match deposits or withdrawals to your wallet. We record transaction IDs, status messages and timestamps, but support will never ask for bank passwords or one-time codes.

Cookie controls

Cookies help keep you signed in, remember privacy choices, detect suspicious sessions and measure page performance. You can adjust browser settings, though some security or account features may not work correctly if cookies are blocked.

Account security

Login alerts, session checks and device signals are used to spot unusual account access. If you contact us about a privacy concern, we verify identity before changing email, phone, KYC or withdrawal records.

Retention and removal

We keep data for as long as account operation, dispute handling, payment reconciliation and legal duties require. When retention no longer applies, records are deleted, anonymised or restricted from routine access.

Privacy Questions Before You Join

These answers explain how the Privacy Policy works when you create an account, verify identity, use India payment methods or contact us about your records. They are written for everyday use, not legal jargon. If your request depends on local law, we will explain what we can do and what we must retain.

Send a request from the email linked to your account or use signed-in support. Tell us what data you want to access, correct or remove, and we will verify identity before sharing records.

It covers account details, contact data, login activity, KYC documents, wallet records, cookie choices, device signals and support messages. It also covers limited data shared with verification, payment and security service partners.

We use UPI, Paytm, PhonePe and Google Pay references to match wallet activity and resolve payment queries. We do not need your bank password or one-time code, and support will not ask for them.

Yes, you can manage cookies through your browser and, where available, account privacy settings. Blocking some cookies may affect login, fraud checks or saved choices, but we explain the purpose clearly.

KYC records are kept while needed for account checks, payment disputes, fraud prevention and legal duties. When the need ends, we delete, anonymise or restrict records according to our retention process.

Only staff and service partners with a work need can handle it, such as payment processors, verification providers, security vendors or customer care. Access is logged, and broader use needs a lawful reason.

Access and eligibility depend on local law and are available where local law permits. If a law affects your account or privacy request, we will explain the practical step we can take.