Reference

Open the onewin Privacy Policy clearly

Your Privacy Policy explains what account data we collect, why we need it, how cookies work and how payment records linked to UPI, Paytm and PhonePe are handled.

Account dataCookie choicesUPI recordsPaytm logsPhonePe receipts
onewin Open the onewin Privacy Policy clearly
CONTACT ROUTES

Check privacy contact routes for your account

Privacy requests need a clear route, so we separate account help from data-rights handling. Before changing or releasing data, we may ask for account details that confirm you are the account holder.

Privacy email Write to our privacy team with your registered mobile number, email address and the request you want handled. Avoid sending card images or full payment screenshots unless we specifically ask for them.
Account chat Use in-account chat when you can still sign in and need a privacy query linked to your profile. We can see your account context faster after basic verification inside the session.
Security report Contact us quickly if you notice unknown logins, changed profile details or payment records you do not recognise. We may pause sensitive changes while we check device and access signals.
POLICY CARE

Browse how we care for data

The Privacy Policy is not only a legal page; it describes daily handling inside our account, wallet and service systems.

Data we collect

We collect account details you provide, device signals, login records, wallet references and communication history. Each category helps us run the account, secure access, meet legal duties or answer your privacy request.

Cookie handling

Cookies help keep you signed in, remember language choices, measure page errors and detect unusual activity. You can manage browser settings, but blocking some cookies may affect account sessions and security checks.

Payment records

UPI, Paytm, PhonePe and Google Pay references are used to reconcile wallet activity and investigate disputed transactions. We store only the payment data needed for matching, compliance checks and account safety.

Security checks

When a password, device or withdrawal detail changes, we may compare login history, location signals and prior account activity. These checks reduce unauthorised access while keeping privacy handling tied to clear purposes.

Retention periods

Some records are removed when they are no longer needed, while others must stay for legal, tax, dispute or security reasons. We review retention by record type rather than keeping everything forever.

Change requests

You can ask to correct inaccurate profile data, request a copy of eligible data or seek deletion where allowed. We confirm identity first and then respond with the action taken or reason for refusal.

See answers on Privacy Policy rights

These answers focus on how the Privacy Policy works when you open an account, use payment methods, contact us or ask for changes to your data. They are written for India and should be read with local law in mind, because access and eligibility are available where local law permits.

We collect data you provide during account setup, profile changes and contact with us. We also process login records, device signals, cookie data and payment references needed for account security and wallet reconciliation.

UPI, Paytm, PhonePe and Google Pay references help us match wallet activity to your account, investigate failed or disputed transactions and meet record-keeping duties. We do not use these records for unrelated sharing.

Yes. Send the details that need correction and proof that links the request to your account. We will update eligible fields after verification, unless a legal or security reason requires the old record to remain.

Cookies support sign-in, language settings, error checks and security monitoring. You can control many cookies through your browser, but blocking essential ones may interrupt account access or make verification steps appear more often.

Access is limited to teams and service providers that need it for account operation, payment matching, security checks, customer contact or legal duties. We aim to keep each access tied to a clear task.

Retention depends on the record type. Some account and cookie records expire quickly, while payment, dispute and security records may stay longer where law, tax handling or account protection requires it.

Use the privacy email or signed-in account chat and include the request type, registered contact detail and any relevant date. We may ask extra questions before releasing, correcting or deleting eligible data.