Reference

Your data, handled in India

We explain how 6jj collects, uses, stores, and shares account details so you can see what happens to your records before you open an account.

Account checksCookie controlsData requests

Explore lobby Read FAQ

What this policy covers

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

This page explains the privacy policy that applies to the way we handle your records on 6jj. We collect contact details, login signals, device data, cookie data, and transaction references when you open an account, sign in, or send a request. We use that data to

1
verify access, keep sessions secure, answer support messages, detect misuse, and keep the account history we need for audits or disputes. If we work with service providers, they receive only the fields they need for the task and must use them within our instructions. When access
2
or eligibility is discussed, it depends on local law and is available where local law permits. The chip row below uses UPI, Paytm, PhonePe, and Google Pay as local context for India account flow, not as a separate promise. If you ask for correction or deletion,
3
we may first confirm that the request came from the account holder.

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

CONTACT PATHS

Ways to reach us

If you want a copy of the data we hold, a correction, or a deletion request, start with the contact path that matches your account.

Email Send requests to [email protected] with your registered email or phone and the change you want. We use the thread to verify identity before we share, correct, or delete any record.

In-account chat Use in-account chat when you need a faster route. Keep the message short, mention the page, and we can direct it to the privacy team without exposing your records to the wrong inbox.

Secure form If you prefer a written trail, submit the secure form in the account area. It helps us log your request, check the account holder, and track the response until the matter is closed.

SECURITY AND STORAGE

How we protect records

We keep this policy practical by collecting only the details needed to run your account, answer requests, and secure access.

Collection

We collect only the details needed to open, maintain, and secure your account, including contact fields, device signals, and transaction references. The data stays tied to account handling rather than unrelated use.

Cookies

Cookies help us remember sign-in state, session security, and language choice. If you clear them, the site may ask you to sign in again or reset saved settings on your next visit.

Access control

Only staff with a business need can reach sensitive records, and their access is limited by role. We log important actions so we can trace changes and investigate a mismatch.

Retention

We keep records only as long as needed for account handling, audit work, dispute handling, and legal duties. When the retention period ends, we delete or anonymise the file where the system allows it.

Requests

You can ask for a copy, correction, or deletion of details we hold about you. We may need a quick identity check before acting, so we do not send records to the wrong person.

Changes

If this policy changes, we replace the page text and keep the latest version active. For a clear answer about a request, contact the privacy channel that matches your account.

Questions about this policy

These answers explain how the policy works for your account, device, and contact records. If local law changes, we adjust how we collect or store details, and the current version on this page stays the one that applies. When you need a copy, correction, or deletion request, start with the support path that matches your account so we can verify you first.

It covers details we collect when you open an account, sign in, send a message, or move through the site. It also explains why we store device and cookie records and when we may share them with service providers.

We may store transaction references, status logs, and the minimum fields needed to confirm a deposit or withdrawal. Full card data is not our focus here; local payment rails such as UPI, Paytm, and PhonePe are handled through secure processors.

Yes. Send the request from your account contact path, tell us what to change, and add enough detail for identity checks. We will act where local law allows and where the record is eligible for the request.

Only staff and service partners with a defined business need can see restricted records. They are bound by internal controls, and we limit access to the smallest set needed to run security, support, and record handling.

We keep records for the period needed to run the account, handle disputes, meet legal duties, and prevent misuse. After that period, we delete or anonymise them when the system and law permit.

We may still keep certain records for audit, dispute, or legal reasons after an account is closed. If you want a copy before closure, send the request first so we can check the account and respond within the right process.

Your data, handled in India

Ways to reach us

How we protect records

Collection

Cookies

Access control

Retention

Requests

Changes

Questions about this policy

01 What does this policy cover?

02 Do you keep my payment details?

03 Can I ask for correction or deletion?

04 Who can see my details?

05 How long do you keep records?

06 What if I stop using the account?

Related Pages