Reference

Open g102 Privacy Policy for Indian Accounts

We set out how g102 collects, uses and stores the details tied to your account, device and payment trail, so you know what happens before you open an…

Account dataCookie choicesLocal lawSupport path
Browse Lobby Read FAQ
g102 Open g102 Privacy Policy for Indian Accounts
CONTACT ROUTES

Switch to support for privacy requests

For a privacy request, start from the contact path linked to your account so we can match the message to the right record. You can use the support email, in-account form or chat path, then tell us whether you want access, correction, deletion or a copy of stored settings. We answer from the same contact details you registered, and we only process a change once the request is verified and allowed under local law.

Team online

Registered email

Write from the email tied to your account and say what you want changed. We use it to match the request, confirm identity and send the next step without exposing your record to the wrong inbox.

In-account form

Use the form inside your account when you want to ask for access, correction or deletion. It keeps the request linked to your profile, which helps us verify it faster and keep a clean audit trail.

Support chat

If you need a quick reply, start a chat from your signed-in account and share the subject line. We can direct you to the right privacy path, then follow up in writing after verification.

DATA HANDLING

Browse how we handle account data

We keep account data limited to what is needed for sign-in, payment checks, security review and service messages.

Data handling

We collect only the details needed to create and service your account, confirm deposits or withdrawals and answer your messages.

Cookie use

Cookies remember sign-in state, language choice and session safety flags.

Account security

We check for unusual log-ins, repeated failed attempts and device changes.

Record retention

We keep records only as long as needed for active service, legal duties, fraud checks or dispute handling.

Change requests

You can ask for access, correction or deletion by using the contact path linked to your account.

Local-law limits

If a request conflicts with a legal duty, security need or active dispute, we may keep the relevant record for…

Open privacy answers for your account

These answers cover the parts of the policy you are most likely to ask about before you send details or open an account. We keep the language direct so you can see what we collect, how long we keep it and how you can ask for a change. If you need a request handled through a registered contact path, the same steps apply.

It covers the account details, device signals, sign-in logs, support messages and payment references linked to your use of g102. It also explains cookies, record retention and the steps for correction or deletion requests.

We may keep the reference ID, method name and transfer status for UPI, Paytm, PhonePe or Google Pay so we can match the payment and fix errors. We do not need extra bank details for that job.

Yes. Send the request from your registered contact path and tell us whether you want access, correction or deletion. We verify the request first, then reply with the action we can take under local law.

Cookies help us remember your sign-in state, language choice and device signals. They reduce repeat checks, help spot unusual access and keep the page working the way you left it.

Only staff or service partners who need the record for account work, security or support can see the relevant part. They are limited to that purpose and cannot use it for unrelated tasks.

We keep records for as long as the account is active, a legal duty applies, or a dispute or fraud check is still open. After that period, we remove or de-identify them through normal process.

Use the support email, in-account form or chat path tied to your account. Name the exact change you want, and we will confirm what can be done once we match the request.

Related Pages

Balloon About Us g102 Login g102 App