Reference

Privacy Policy for your India account

Your account data, UPI references, Paytm receipts and PhonePe records are handled under this Privacy Policy before you open an account or return to the lobby.

Account data useCookie choicesUPI privacyPaytm privacyPhonePe privacy
indigo777 Privacy Policy for your India account
CONTACT PATHS

Three ways to ask about privacy

Privacy requests should reach the team that can trace your account safely, not a public comment thread.

Email privacy team Write to [email protected] from your registered email. Tell us whether you want a data copy, correction, deletion check, cookie help or account access query, and include only the details needed to identify your account.
Chat privacy handoff Use chat after login if your question is tied to a live account. Our support team can raise a privacy ticket, mask wallet references in the thread, and confirm what extra proof is required.
Account recovery ticket If you cannot log in, send a ticket through the help form on indigo777.co. We will ask for a registered contact, device clue or payment reference before discussing stored account data.
ACCOUNT SAFETY

Six controls behind our privacy work

Our privacy work sits inside daily account operations: sign-in checks, payment reconciliation, cookie settings, chat logs and payout verification.

Data collection

We collect only data needed to create and run your account, such as contact details, login signals, device clues, wallet references and support messages. Extra identity checks are requested when law, fraud checks or account recovery require them.

Cookie choices

Cookies help us keep you signed in, remember language choices and measure page errors. You can clear cookies in your browser, though some account checks may run again when you return.

Payment records

UPI, Paytm and PhonePe references are stored with account records so wallet queries can be matched. We do not store full banking passwords, and support only asks for transaction IDs or screenshots when needed.

Account security

Sign-in alerts, session logs and device checks help us detect account access that does not match your usual pattern. If we see risk, we may pause sensitive changes until identity checks are complete.

Retention timing

Some records must be retained for tax, dispute, security or legal reasons after you cease using the account. When those reasons end, we delete, anonymise or narrow the data held in our systems.

Correction requests

Ask us to correct contact details, spelling errors or outdated documents through the privacy channel. We verify ownership first, then update active records and mark older copies where records must remain for legal reasons.

Privacy questions from India account holders

The FAQ below explains how this Privacy Policy works in practical account situations for India. It covers data collection, wallet references, cookies, access rights and request timing without asking you to share private details in public. If your case involves local eligibility, our answer will consider whether access depends on local law and is available where local law permits. Use it before you send a ticket so your request reaches the right team.

We collect contact details, login records, device signals, wallet references and support messages needed to create, secure and manage your account. Extra documents may be requested only when account checks or legal duties require them.

Wallet references help us match your account with payment status, failed transactions, refunds and dispute checks. We keep the reference, time and account link, not your banking password or private app login details.

Yes. Email [email protected] from your registered contact and describe the data you want. We verify ownership before sending a copy, because account records may include wallet and security details.

Cookies store session, language and device signals so your account can load correctly and suspicious access can be detected. You can clear browser cookies, but some sign-in or verification steps may repeat later.

We use session checks, device signals, staff access controls and audit trails for sensitive changes. If a request affects stored data, we may ask for identity proof before changing or releasing account records.

You can ask us to correct, update or delete eligible data through the privacy channel. Some records may remain for tax, dispute, security or legal reasons until the required retention period ends.

Yes. Access and eligibility depend on local law and are available where local law permits. If your region requires extra verification, we may request matching account and wallet details before allowing changes.