Reference

Privacy Policy for your i30 account

i30 links your account data, cookie choices and payment records for UPI, Paytm, PhonePe and Google Pay under one Privacy Policy, so you can see what we collect…

UPI data contextPaytm record checksPhonePe privacy flowGoogle Pay receipt data
i30 Privacy Policy for your i30 account
CONTACT ROUTES

Three ways to ask privacy questions

Privacy requests need a clear path because they can involve account access, payment records or identity checks. Use the route that matches your situation, and include only the details needed for us to find your account. We will not ask for your password, full card image or private UPI PIN. If your request concerns a payment record, include the payment method and approximate time.

Team online

Privacy email

Send your request to [email protected] with your account email and the data question you want us to check. Do not include card images or passwords; we will reply with the next step after identity checks.

Account message

Use the logged-in help message if your question relates to UPI, Paytm, PhonePe or Google Pay records. We can match the request with your wallet history without asking you to repeat sensitive payment details.

Live chat ticket

If you cannot access your account, contact live chat and ask for a privacy ticket. We will first confirm control of the registered phone or email, then help you raise the privacy request safely.

CARE PRACTICES

Six privacy controls around your account

Our Privacy Policy is written around the data flows we actually handle: account creation, cookie storage, payment verification, support conversations and security checks.

Cookie choices

Cookies help us remember language, session status and device safety choices. The Privacy Policy explains which cookies are needed for login, which support analytics, and how you can adjust them from your browser.

Account security data

We use account passwords, one-time codes and device checks to reduce unauthorised access. The policy links these security steps with the data we collect, including login time, IP range and failed access attempts.

Payment record handling

Payment records for UPI, Paytm, PhonePe and Google Pay may include reference IDs, receipt status and timing. We keep only what is needed to verify wallet movement, resolve queries and meet legal duties.

Limited sharing

When service providers help with hosting, fraud screening or payment checks, they receive only the data needed for that task. We do not sell your account data to outside ad lists.

Retention periods

Retention periods differ by data type: account records last longer than short session cookies because law, audit checks or disputes can require them. We delete or anonymise data when retention no longer applies.

Correction requests

You can ask us to correct profile details, close dormant records where law allows, or share a copy of key account data. We may ask for proof before acting to protect your account.

Privacy Policy questions you may ask

The answers below explain common privacy requests in practical terms. They focus on account data, cookies, payment records and contact steps rather than general lobby features. If your question involves a specific UPI, Paytm, PhonePe or Google Pay record, keep the reference ID ready and contact us through a logged-in account message when possible.

It covers registration details, login records, device signals, cookie choices, support messages and payment references linked with your account. It also explains why we collect each category and how you can contact us about it.

We collect payment records to confirm wallet activity, match UPI, Paytm, PhonePe or Google Pay receipts, resolve failed transactions and meet legal duties. We avoid asking for payment secrets such as UPI PINs.

Yes, you can ask for a copy of key account data we hold about you. We first verify your identity, then explain what can be shared and whether any legal restriction affects the request.

Cookies help keep you logged in, remember preferences and support fraud checks. The policy separates required cookies from analytics cookies, and you can manage many choices through your browser settings.

Only teams or service providers with a clear account, payment, safety or support reason can access relevant data. Access is limited by role, and sensitive requests require additional checks before action is taken.

We keep data for as long as needed for account operation, legal duties, payment checks or dispute handling. Short session data may expire sooner, while transaction records can be retained for longer periods.

Contact us with the account email, the data you want corrected or deleted, and any reference that helps us find it. We will verify your identity and act where law allows.