Reference

Privacy Policy for India account data

Your Privacy Policy explains how g67 handles account details, wallet records, KYC files, device signals and cookie data when you open an account or use the lobby.

Account data useUPI privacy contextKYC handlingCookie choices
g67 Privacy Policy for India account data
PRIVACY HELP

Reach us about privacy requests

If you want to ask about your data, update account details or raise a privacy concern, contact us through the channel that fits the request.

Email privacy desk Write to [email protected] for access, correction, deletion or retention questions.
Live chat privacy handoff Use live chat for a quick privacy request number or to confirm which document…
KYC document query For ID file questions, tell us whether the concern relates to upload status, correction…
ACCOUNT CARE

How we handle your privacy choices

Our privacy work is tied to everyday account activity: login checks, wallet movements, KYC verification, cookies, support chats and withdrawal checks.

Data we collect

We collect data you provide, such as name, mobile number, email, KYC files and payment references, plus technical data like device type, IP address, session time, cookie choices and security events.

Why we use it

We use your data to run the account, verify payments, protect wallet access, respond to support requests, apply fraud controls, meet legal duties and keep records needed for disputes or transaction checks.

Cookies and device signals

Cookies help us remember sessions, manage language choices, measure site faults and spot unusual login patterns. You can change browser cookie settings, though some account and security features may need them.

Sharing with service partners

We share limited data with payment processors, hosting teams, identity checks, fraud tools and support systems. Each partner receives only what is needed for the account task or legal request involved.

Retention and deletion

We keep data for as long as needed for account service, payment records, legal duties, dispute handling and security checks. When the reason ends, we delete, anonymise or archive it under controlled access.

Access and correction

You can ask to access, correct or delete personal data linked to your account. We first confirm ownership, then explain what we can change and what must remain for legal or payment reasons.

Privacy questions for India account holders

These answers focus on how this Privacy Policy applies when you create an account, verify identity, use local payment methods or contact support. They are written to help you understand the data steps behind the account flow. If your question involves a live account, send it from your registered email so we can check ownership before sharing any private data.

We collect account details you provide, KYC files when verification is required, payment references, login records, device data, cookie choices and support messages. The exact data depends on how you use the account.

Payment references help us match wallet activity to your account, confirm transaction status and resolve disputes. We do not need your banking password, UPI PIN or private login credentials for any privacy request.

Yes. Email [email protected] from your registered email and state that you want access to your personal data. We may verify ownership before sending account-linked data through a secure response path.

Send the corrected detail and your registered mobile or email to the privacy desk. For sensitive fields, such as identity data, we may ask for fresh proof before making the change.

You can request deletion, and we will remove data where no legal, payment, dispute or security reason requires retention. If we must keep certain records, we will explain the category and reason.

Cookies can remember sessions, help security checks and measure site errors. You can manage them in your browser, but blocking some cookies may affect sign-in, wallet security or account verification steps.

Only teams who need the messages for your request, account safety or a legal duty can access them. We limit access, keep logs and avoid sharing more data than the case requires.