Reference

Legal terms for your account in India

Open your account and we will show you the legal text that applies to your use of limeprobet in India.

India accessData useAccount recordsLocal law

How access and records work

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

Access to limeprobet depends on local law and is available only where local law permits. We do not invite you to continue from a restricted place, and we do not soften that limit in the wording here. When you create or use an account, we may

1
record sign-in details, device markers, wallet actions, and support messages so we can confirm identity, prevent misuse, and answer disputes. Payment names such as UPI, Paytm, PhonePe, and Google Pay appear in the wallet flow only as methods for transfers and checks; they are not used
2
for unrelated messaging. If the law changes, we update the legal text, the account steps, and the contact path together so what you read matches what we can actually do.

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

CONTACT PATHS

Where to send legal questions

If you want a correction, a copy of stored account data, or a question about access, use one of the channels below and send the details that match your account.

In-account form Use the form inside your account for correction, access, or retention questions. Add your registered phone number and the exact change you want so we can locate the record before we answer.

Email Write to [email protected] when you need a written trail. We use the subject line and your account details to route legal requests to the right team without mixing them with routine support.

Message thread If a request starts in chat, keep replying in the same thread. That keeps your identity check, prior messages, and any follow-up attached to one record, which helps us close the request cleanly.

DATA HANDLING

How we handle data and access

We keep legal handling tied to the account itself. Device and browser data help us detect duplicate sign-ins, cookie settings help us remember your consent choices, and transaction records help us verify…

Data handling

We store only the record needed for account use, verification, dispute handling, and legal retention. When a field is no longer needed, we stop using it for active checks and keep only what the law or the request history requires.

Cookie choices

Cookie settings help us remember session state, language, and access flags. You can clear browser cookies yourself, but that may change how the account loads and may require you to confirm identity again.

Account security

We protect the account with sign-in checks, device signals, and change verification before sensitive updates. If a password or number changes, we may ask for extra proof so the wrong person cannot alter your record.

Retention

We keep logs for the period needed to run the account, settle disputes, meet lawful record duties, and stop misuse. When the retention window ends, we remove or anonymise data according to the record type.

Request changes

To update a name, number, consent choice, or stored detail, send a clear request from the registered account path. We compare it with existing records before we make any change that could affect access.

Contact path

If you need a legal copy, a correction, or a question answered in writing, use the same support channel shown in your account. We keep the thread attached to your file so the reply is easy to trace.

Common legal questions, answered clearly

These answers cover the legal points people ask about most: access, stored data, changes, and contact. If your case needs a closer look, use the account path that matches your registered details and send the exact request in writing. We answer from the same record set we keep for support, verification, and lawful retention, which keeps the process tied to the right account and avoids delays caused by mismatched details.

Access depends on local law and whether your location is allowed. If a region is restricted, the account flow stops there and we do not ask you to push ahead from that place.

We keep the details needed to set up the account, check sign-ins, process wallet actions, and answer support requests. That may include device markers, contact details, and transaction records tied to your profile.

Yes. Send the request from the registered account path, say what you want changed or copied, and include the exact account details. We compare it with stored records before we reply.

Cookies help us remember session state, language, and consent choices. If you clear them, the page may ask you to confirm parts of the record again before we continue with a change or access request.

We keep records only as long as needed for active use, dispute handling, lawful retention, and misuse checks. When that period ends, the data is removed or anonymised in line with the record type.

Use the in-account form, the email address shown in support, or the same message thread you used earlier. Keeping one path attached to your file helps us verify the request faster.

Yes, wallet records may show UPI, Paytm, PhonePe, or Google Pay when they are part of a transfer or verification step. We use those entries only to match the transaction and keep the account trail clear.

Legal terms for your account in India

Where to send legal questions

How we handle data and access

Data handling

Cookie choices

Account security

Retention

Request changes

Contact path

Common legal questions, answered clearly

01 What decides whether I can access the account from India?

02 What data do you keep when I open an account?

03 Can I ask for a copy or correction of my data?

04 How do cookies affect legal handling?

05 How long do you keep records?

06 Which contact path should I use for legal questions?

07 Do payment names appear in the legal record?

Related Pages