Reference

t670 Privacy Choices in India

Our Privacy Policy explains how account data, device signals, cookies, and UPI, Paytm, PhonePe records are collected, used, shared, and protected when you access t670 where local law…

Account dataCookie choicesUPI recordsPaytm and PhonePePrivacy requests
Explore our lobby Read FAQ
t670 t670 Privacy Choices in India
CONTACT PATHS

Three Privacy Contact Routes

Privacy questions should reach the team that can act on them, not a general queue. Use the route that matches your request: account data access, payment-record clarification, cookie preference changes, or correction…

Privacy email Send privacy requests through the contact email listed in your account area. Include your registered mobile number or account name, the privacy action you want, and any payment reference only if it helps us locate the record.
Live chat handoff Start with live chat when you need help finding the right privacy route. The chat team can collect a brief summary, verify your account, and pass the matter to the privacy team for a recorded response.
Account centre request Use your account centre for changes to basic profile details, communication choices, and cookie settings where the tool is available. Sensitive changes may still need a manual check before the update is applied.
DATA CARE

Six Ways We Protect Data

Our privacy work is practical: we collect what is needed for account access, payments, security checks, support, and legal duties, then keep control over who can view it.

Account data handling

We collect details such as your name, mobile number, email address, device data, and login records to open and maintain your account. Access to this data is limited to teams that need it for account or safety work.

Cookie control

Cookies help keep your session active, remember basic choices, and detect unusual access patterns. You can adjust browser settings, but some account functions may not work correctly if required cookies are blocked.

Payment record care

UPI, Paytm, PhonePe, and Google Pay records are used to match wallet activity, verify payment status, and resolve disputes. We store transaction references rather than unnecessary payment credentials wherever the payment flow allows.

Security checks

We review login signals, device changes, failed access attempts, and wallet actions to protect your account. If activity looks unusual, we may pause some actions until you confirm that the request came from you.

Retention windows

Some records must be kept for legal, accounting, dispute, and security reasons. When a record is no longer required, we remove it, anonymise it, or separate it from active account use.

Correction requests

You can ask us to correct personal details that are wrong or incomplete. We may need identity checks before changing sensitive records, especially where the update affects payment matching or account access.

Privacy Questions Before You Join

Before you open an account, you should know what data we request, how long we keep it, and how you can reach us about changes. These answers focus only on the Privacy Policy, including payment records, cookies, support history, account access, and requests to view, correct, or remove eligible data.

We may ask for your name, mobile number, email address, login details, device signals, support messages, and payment references. The exact data depends on your account activity, verification needs, and local law.

Payment references help us match wallet activity, confirm transaction status, respond to disputes, and meet record-keeping duties. We use these records for privacy, security, and account support purposes, not for selling personal data.

Yes, you can contact us to request access to eligible personal data linked to your account. We may verify your identity first and may withhold data where the law requires or allows restriction.

Use your account centre where edits are available, or contact privacy support for details that need manual handling. We may request proof before changing sensitive data tied to wallet checks or account access.

Cookies support login sessions, preference storage, security checks, and site measurement. You can manage many cookie settings through your browser, but blocking required cookies may affect account access or payment confirmation.

We may share limited data with partners that help with hosting, analytics, payment processing, fraud checks, or support tools. They receive only what is needed for their task and must handle it securely.

You can ask us to delete eligible data after closure. Some records may be kept for legal duties, dispute handling, security checks, or accounting needs, then removed or anonymised when retention is no longer required.

Related Pages

Floating Dragon t670 App FAQ Wicked Witch