Reference

Privacy Policy for India accounts

UPI, Paytm, PhonePe and Google Pay records, account data, cookies and support chats are covered in this Privacy Policy for India-facing access on g84.

UPI data contextPaytm wallet recordsPhonePe checksCookie choicesSupport privacy
g84 Privacy Policy for India accounts
CONTACT ROUTES

Privacy contact paths for India

You can reach us about this Privacy Policy through the account help area, email or a wallet query raised from your payment history.

Email privacy desk Send your privacy request from the email linked to your account. Include your account name, mobile number if added, and the data question you want us to check.
In-account chat Use the help area after logging in when your question relates to cookies, recent device access or a payment reference. The agent can view account status without asking for card-like secrets.
Wallet query path For UPI, Paytm, PhonePe or Google Pay privacy concerns, raise a wallet query from the transaction row. That keeps the payment ID tied to your request.
DATA CARE

India privacy controls inside g84

We handle privacy as part of the account lifecycle, not as a separate form hidden away from your wallet.

Account data

We collect details you provide during account creation, profile changes and verification. This can include your name, contact details, login records and status markers needed for access where local law permits.

Payment records

UPI, Paytm, PhonePe and Google Pay references are linked to wallet activity so deposits and withdrawals can be matched. We store transaction IDs, timing and status, not your full payment app secrets.

Cookie choices

Cookies help keep you signed in, remember basic preferences and support security checks. You can adjust browser settings, though some account and wallet functions may need session cookies to work.

Security logs

We record device type, IP range, login timing and activity signals to detect unusual access. These records help us protect your account and investigate support requests tied to your balance.

Retention handling

We keep data while your account is active and for periods required by payment, security or legal duties. When a record is no longer needed, we delete or reduce it.

Correction requests

If your name, mobile number or email is wrong, ask us to correct it. We may request a fresh verification step before changing account data that affects access.

India privacy questions before account access

These answers explain how this Privacy Policy applies when you open, use or close an account from India. They focus on practical privacy topics: what we collect, how payment data is handled, when records are kept, how cookies work and how you can contact us. Access and eligibility depend on local law and are available where local law permits.

We collect account details you provide, login activity, device signals, support chat records, cookie choices and wallet references. Payment records can include UPI, Paytm, PhonePe or Google Pay transaction IDs and status.

Payment data helps us match deposits, process withdrawals, trace failed transactions and respond to wallet queries. We use transaction references and timing data rather than asking for sensitive payment app credentials.

We may share only the data needed with banks, payment processors or verification partners to complete payments, handle disputes, check fraud risk or meet legal duties. We do not sell your account data.

Retention depends on account status, payment requirements, security needs and legal duties. When a record is no longer needed for those purposes, we delete it, reduce it or keep only limited proof.

Yes. Contact us from your linked email or logged-in account and explain what needs correction. We may verify your identity before changing data tied to login, wallet access or withdrawals.

Cookies support login sessions, preferences and security checks. You can manage them through your browser, but some account or wallet actions may not work correctly without session cookies.

Use the account help area, email privacy desk or wallet query path. Share enough detail to identify the account, but do not send passwords, payment app PINs or unnecessary documents.