Reference

Open 6n137 Privacy Policy Details

This page explains how 6n137 handles the details tied to your account, your device, and the messages you send us.

Account recordsCookiesPayment referencesIndia law
6n137 Open 6n137 Privacy Policy Details
REQUEST ROUTES

Switch to contact paths for requests

Use the contact path that is already inside your account when you want to ask about access, correction, or removal.

In-account help Send your request from the help panel after you sign in. We match it with your account record, then reply with the next step for access, correction, or removal where local law permits.
Support inbox Use the message inbox when you need a written trail for a privacy request. We keep the thread with your case file so you can track the reply and any follow-up checks.
Chat panel When chat is visible, you can ask about cookies, account records, or payment references. If the request needs identity checks, we will ask for proof before we share or change anything.
DATA CARE PRACTICES

Explore security, cookies and retention

Our policy is built around limited access and clear records. Only staff who need a task can view account, payment, or support data, and we log those actions.

Account data

We collect only the details needed to create your account, confirm sign-in activity, and answer your requests. That usually includes contact fields, login events, and case references from support.

Payment records

When you use UPI, Paytm, PhonePe, or Google Pay, we may store the reference number, time stamp, and status result so wallet checks and account matching stay accurate.

Cookies

Cookies help us keep you signed in, remember language choice, and see whether pages load correctly on your device. You can clear them in your browser if you want a fresh session.

Security checks

We protect account access with login controls, session logs, and change checks. If a request looks unusual, we may ask for extra proof before we update personal data or payment records.

Retention

Records stay only for the period needed for account handling, legal duties, dispute checks, and support history. After that, we delete or anonymise them where local law allows.

Your requests

You can ask to see, correct, or remove account details by sending a logged-in request. We verify identity first, then handle the request in line with local law and our records.

Open answers about your privacy choices

These answers cover the most common privacy questions on 6n137. If your request is unusual, send it through support and we will check the account record, the relevant logs, and the law that applies before we reply. We may ask for proof of identity before any change that affects your account.

We collect the details needed to open and keep your account running: contact fields, sign-in events, device data, and support messages. If you use UPI, Paytm, PhonePe, or Google Pay, we may also keep payment references and status records.

Cookies help us keep you signed in, remember your choices, and check whether pages load properly on your device. They also reduce repeated checks when you move between account pages.

We keep records only for account handling, dispute checks, legal duties, and support follow-up. When those reasons end, we delete or anonymise the data where local law permits.

Yes. Send a logged-in request through support and tell us what needs correction or removal. We confirm it against your account first, then act according to local law and the records we hold.

Only staff who need the data for account checks, support replies, payment matching, or security work can view it. We limit access and log those actions so the record stays tied to a task.

Yes. Access, retention, sharing, and removal requests depend on local law and are available where local law permits. If a rule conflicts with a request, we follow the applicable legal requirement.

Use the in-account help panel, the support inbox, or chat when it is shown on your screen. We will respond after matching the request to your account and checking any proof we need.