Reference

Privacy Policy for your ie777 account

At ie777, your privacy file connects your account identity, device signals, UPI, Paytm, PhonePe, Google Pay records, cookie choices and support chats to one clear policy.

UPI data careCookie choicesAccount request pathIndia privacy support
ie777 Privacy Policy for your ie777 account
CONTACT ROUTES

Privacy help through account support

Privacy requests should reach the same support team that can verify your account safely.

Privacy mailbox Write to the privacy mailbox with your account ID, registered mobile number and the change you want. We check the request against your account record before sharing or changing any private data.
Live chat request Use live chat when you need a quick privacy handoff, such as a cookie query or login alert. Chat agents can collect the request and pass it to the privacy desk after verification.
Account profile path Your profile area helps us confirm email, phone and payment references before we act. If a field cannot be changed directly, support can raise a privacy request for manual checking.
DATA CARE

Account privacy across payments and cookies

We keep privacy work tied to practical account checks, not vague promises. Payment references are matched to deposits and withdrawals, cookies are used to remember session choices and security tools watch for…

Account data we collect

We collect the details needed to open and maintain your account, including contact data, login history, device signals and wallet activity. We do not ask for more than we need for verification and support.

UPI and wallet records

UPI, Paytm, PhonePe and Google Pay references help us match deposits, withdrawal checks and dispute queries. We store payment identifiers with account records so support can trace a transaction without exposing full banking data.

Cookie choices

Cookies help keep your session active, remember language choices and support fraud checks. You can manage browser cookies, but blocking some cookies may affect login flow, device recognition or support diagnostics.

Security checks

We monitor login attempts, device changes, password resets and payment patterns to protect your account. When an alert looks unusual, we may pause a sensitive action until your identity is checked.

Retention periods

Some records must stay for account, tax, dispute or payment checks. When a record is no longer needed, we delete, mask or separate it from your active account where our systems allow.

Correction requests

If your name, phone number, email address or payment reference is wrong, contact support from your registered channel. We may ask for proof before correcting a record that affects withdrawals or account access.

Privacy questions before you join

These answers explain how privacy requests work before and after you open an account. They cover the records we hold, how we use payment references, what happens when you ask for correction or deletion, and how account access depends on local law. If your case involves a disputed transaction or security alert, support may need extra verification before acting.

We collect contact details, account credentials, device signals, login history and wallet activity. If payment or withdrawal checks are needed, we also keep transaction references linked to UPI, Paytm, PhonePe or Google Pay.

Payment references help us match deposits, verify withdrawals and trace disputes. We use them to confirm the account connection, not to publish or sell your banking details to unrelated third parties.

Yes. Send a request from your registered email or phone and include your account ID. We verify your identity first, then explain what data we can share and any lawful reason for withholding part of it.

Contact support with the field that needs correction and the current account ID. For sensitive changes, such as phone number or payment reference, we may request proof before updating the account record.

You can ask for deletion, and we will remove or mask data where allowed. Some records may stay for payment, dispute, tax or security duties until the required retention period ends.

Cookies support login sessions, language settings, device recognition and security checks. You can manage them in your browser, but blocking key cookies may make sign-in, wallet checks or support diagnostics less reliable.

Use the privacy mailbox, live chat or your account profile route. Send the request from a registered channel where possible, so we can confirm ownership before discussing or changing private account data.