Reference

Privacy Policy for your winslots account

This Privacy Policy explains how winslots handles account data, cookies, payment references, and support records when you open or manage an account.

Account dataCookie choicesUPI recordsPaytm and PhonePePrivacy requests
Explore Lobby Read FAQ
winslots Privacy Policy for your winslots account
CONTACT ROUTES

Three routes for privacy requests

Privacy questions need a clear route, so we keep contact choices direct and easy to verify.

Email privacy desk Send privacy requests to the email shown in our footer with your account email, mobile number, and the change you want. We use those details to match your request before replying.
Chat route check Use chat when you need to know where to send a privacy request or how to confirm account ownership. The chat team can route you, but we may answer data requests by email.
Security escalation If you think your account email, mobile number, or payment reference was exposed, contact us quickly. We can mark the ticket for security checks and tell you what proof we need.
ACCOUNT CARE

Six controls behind data care

Behind the policy, our team works with payment partners, security tools, and account systems that create records each time you log in, contact support, or use UPI, Paytm, or PhonePe.

Data collection

We ask for details that let us create your account, verify login activity, answer tickets, and handle payment checks. Extra fields are checked so we can avoid collecting data that has no clear purpose.

Cookie controls

Cookies help keep your session active, remember language choices, and measure page errors. You can adjust browser settings, though some account pages may ask you to sign in again after changes.

Payment records

For UPI, Paytm, and PhonePe, we store transaction references, timestamps, status results, and matching account details. These records help trace a failed credit, withdrawal query, or refund request.

Access checks

When you sign in, we may compare device signals, IP range, password attempts, and session history. If something looks unusual, we may ask for extra confirmation before account data is shown.

Retention periods

We keep records for legal, tax, payment, security, and dispute needs, then reduce or remove data when it is no longer required. Exact timing depends on the record type and local rules.

Change requests

You can ask us to correct account details, update contact choices, or remove data where we are allowed to do so. We may keep some records when law or disputes require it.

Privacy Policy questions before you join

Privacy rights are easier to use when the steps are plain. The answers below cover what we collect, why we keep certain records, how payment references are handled, and how you can contact us about corrections or deletion. If your request involves legal access, we will check the rules for your location before confirming what we can do. We may also ask for identity proof when the request affects account access or wallet records.

We collect details you give us, such as your name, email, mobile number, login credentials, payment references, and support messages. We also record device, session, and cookie data needed for security checks and service operation.

UPI, Paytm, and PhonePe references help us match deposits, check withdrawal requests, trace failed credits, and answer wallet disputes. We do not publish your payment details, and sharing is limited to service partners handling those tasks.

Yes. Send the correction request through the contact route shown on this page or in the footer. We may ask for account proof before changing email, mobile, payment, or identity details linked to your account.

Cookies support sign-in sessions, fraud checks, language choices, and page measurement. You can manage them through your browser, but blocking some cookies may mean you need extra login checks before account pages load.

Retention depends on the record. Payment and identity records may be kept for legal, tax, security, or dispute needs, while some cookie and session data can be removed sooner when it is no longer needed.

Only teams or partners who need to handle the request should access it. For example, privacy staff, support leads, payment processors, or security vendors may view the relevant records under access controls.

Access or eligibility depends on local law and is available where local law permits. Even when access changes, we still handle privacy requests through the policy process and applicable retention rules for your account records.

Related Pages

Olympus Glory FAQ Book of Fallen Gold Rush