Reference

Privacy Policy for Your 8cm Account

At 8cm, this page explains what we collect, why we use it, how long we keep it, and how you can ask for access or changes.

Data useCookiesRequestsIndia
8cm Privacy Policy for Your 8cm Account
CONTACT ROUTES

Where To Reach Us

Use the contact paths below if you want access, correction, deletion, or a clarification about how we use a record.

Email Write to us from the address linked to your account, and we will reply with the next step, the checks we need, and the records we may need before changing private details on your file.
Chat Use chat if you want a quick path for access, correction, or deletion questions. Keep your account details ready so we can match the request to the right record without delay or confusion.
Support form Add the request type, your account email, and a short explanation of what you want changed. We route it to the correct team and keep only the thread needed to finish the case.
PRIVACY CONTROLS

How We Handle Requests

We treat privacy work as part of account care, not a side task. That means we limit collection to what we need, keep payment references separate from public-facing text, and use cookies…

Data minimisation

We collect only what we need to open your account, process transfers, and answer support. That can include contact details, device data, cookies, and activity logs linked to your sessions, but nothing extra just to fill a file.

Cookies

Cookies help keep you signed in, remember your settings, and measure page performance. You can clear them in your browser anytime, though some preferences may need to be set again after that to reflect your current choice.

Payment records

UPI, Paytm, PhonePe, and Google Pay references are stored with time stamps and transaction IDs so we can match deposits or withdrawals to the right account and settle questions accurately when you ask about a specific transfer.

Security checks

When you ask for a sensitive change, we may ask for a fresh verification step. That protects the account from unauthorised edits and helps us confirm the request came from you instead of someone else.

Retention

We keep personal data only as long as needed for account history, dispute handling, tax checks, and system safety. After that, records are removed or masked unless law requires longer storage for a valid reason.

Change requests

If you want a correction, deletion, or a limit on how a record is used, contact support with a clear request. We will explain what can change now and what must stay on file, then confirm the result.

Common Questions About Privacy

These questions cover the parts you usually check first: what we collect, why we keep it, how cookies work, and how to ask for a correction for your account. We keep the answers short so you can decide what to do next without scanning dense legal text. If local law sets a different rule, that rule applies where it is valid.

It covers the data we collect when you open an account, use your wallet, contact support, or move between pages, and explains why we keep each record in line with local law where it applies.

We may collect your name, contact details, device data, cookies, support messages, and transaction references from UPI, Paytm, PhonePe, or Google Pay when you use the account for support.

We use it to run your account, process payment records, keep the site secure, answer requests, and meet retention or record-keeping duties where local law permits for you.

Yes. Contact support from the address tied to your account, tell us what you want changed, and we will verify the request before making any update allowed by law.

Yes. Cookies help with sign-in, preferences, and page performance. You can clear them in your browser, but some settings may need to be set again after you clear them.

Send an email, use chat, or submit the support form with your account details and the request type. We reply in plain English and keep the thread needed to finish the case.

If local law changes what we may hold or share, the local rule applies where it is valid. We will still explain what stays on record, what can change, and which request path to use.