Privacy Policy

Information We Collect and How the Data Layer Works

Winbuzz India uses a structured data layer to operate account access, wallet functions, security controls, customer support, and service continuity. This Privacy Policy explains what categories of information may be collected when a user creates an account, accesses platform tools, interacts with payment flows, or contacts support.

The platform does not treat all information equally. Some data is essential for account creation and verification, some is technical and session-based, and some is generated through normal use of the service environment. The purpose of this distinction is to make it clear that not every signal is used for the same reason.

Account and identity information

When a user registers an account, the platform may collect identification and profile data such as name, date of birth, contact details, residential information, and login credentials. Where verification or compliance checks apply, the platform may also request supporting documentation. This can include identity documents, address evidence, or payment-source confirmation material.

This information is used to establish account ownership, confirm eligibility, reduce duplicate-account risk, and support wallet and withdrawal processing. It is not collected to influence gameplay outcomes and does not alter the underlying behavior of game engines.

Transaction and wallet-related information

When a user deposits, withdraws, activates a promotion, or enters a payment review flow, the platform may record transaction references, timestamps, payment method metadata, wallet-state changes, bonus status, and related account events. These records help maintain accounting continuity across payment actions and ensure that the visible wallet state aligns with the service logic behind it.

Transaction history is therefore part of the operational record of the account. It exists to support reconciliation, fraud prevention, support review, and lawful processing obligations. It should not be understood as a gameplay profile.

Technical, device, and usage signals

The platform may also collect technical information such as IP-related signals, browser type, device identifiers, operating system details, language preferences, approximate access region, session timestamps, clickstream behavior, and error logs. This information helps the service adapt to device conditions, detect abnormal usage patterns, improve interface stability, and protect account security.

Technical signals do not function as predictive tools. They are part of the service and protection layer. For example, repeated failed logins, abrupt region changes, device switching patterns, or unusual access timing may trigger review logic designed to protect account integrity.

Support communications and submitted materials

If a user contacts support, the platform may retain the content of support messages, complaint details, attachments, verification submissions, and resolution notes. These records are used to maintain continuity across cases, avoid duplication, and review how a request was handled over time.

Support content is stored as part of the service relationship between the user and the platform. It helps preserve context for account recovery, payment clarification, and complaint handling, especially where multiple interactions are needed before a case is resolved.

How Data Is Used, Security Controls, Cookies, and Processing Logic

The data collected within the platform is not used as a single pool. Each category serves a defined operational purpose. Account data supports identity and access. Transaction data supports wallet state and reconciliation. Technical signals support stability and protection. Support data preserves continuity across interactions.

The platform does not use personal data to influence game outcomes. Gameplay logic remains isolated and is determined independently by game engines operating under RNG systems. Data usage is therefore tied to service delivery, not result generation.

Operational use of data

Personal and technical data may be used to:

• maintain account access and login integrity
• process deposits and withdrawals
• perform identity verification (KYC where required)
• detect irregular or high-risk activity patterns
• manage bonus eligibility and wagering state tracking
• respond to user support requests
• improve platform stability across devices and sessions

These processes are automated where possible and reviewed manually where necessary. The goal is consistency, not interpretation. The system does not “judge” user behavior; it checks whether actions align with defined account and transaction rules.

Security and verification layer

Security controls may include device fingerprinting, IP pattern checks, session validation, and anomaly detection. These mechanisms exist to protect account access and prevent unauthorized use. Where inconsistencies are detected, additional verification may be required before certain actions (such as withdrawals) are completed.

Verification steps may include identity confirmation, payment source validation, or document review. These checks are part of financial and security compliance and are not related to gameplay.

Cookies and session technologies

The platform may use cookies and similar session tools to:

• maintain login sessions
• remember user preferences
• support navigation flow across pages
• detect session interruptions or errors
• analyze basic interaction patterns for stability improvements

Cookies are not used to modify game probability or outcomes. They function as part of the interface and session layer.

Data Usage Overview

Data Retention, Sharing Boundaries, User Rights, and Policy Updates

Data within the platform is retained only for as long as it is necessary to support account operation, transaction processing, compliance requirements, dispute handling, and security review. Retention periods are not uniform. Identity data, transaction logs, and verification records may be stored longer than session-level or technical data because they are required for audit, fraud prevention, and legal obligations.

Short-lived data such as session cookies or temporary technical logs may expire automatically after a defined period or after a session ends. Account-related records may remain available even after account closure where retention is required by law or necessary to resolve outstanding issues.

Data sharing and third-party boundaries

The platform does not operate in isolation. Certain data may be shared with third-party providers where required to deliver core services. This includes:

• payment processors for deposits and withdrawals
• identity verification providers for KYC checks
• hosting and infrastructure providers for system operation
• fraud detection and security services
• customer support systems

Data sharing is limited to what is necessary for each function. Third parties are expected to process data within defined contractual and legal frameworks. The platform does not sell personal data and does not provide unrestricted access to user information for unrelated purposes.

Where required by law, regulation, or official request, the platform may disclose relevant data to authorities. This is handled within applicable legal frameworks and does not extend beyond what is required for compliance.

User rights and control over personal data

Users may have the ability to:

• request access to stored personal data
• request correction of inaccurate or incomplete information
• request deletion of data where retention is no longer required
• restrict or object to certain types of processing
• withdraw consent where processing is based on consent

The availability of these rights may depend on applicable law, identity verification status, and whether the data is required for ongoing legal or operational purposes. Requests are typically processed through support channels and may require identity confirmation before action is taken.

Users should also understand that deleting or restricting certain data may impact account functionality. For example, removing identity data may prevent withdrawals or account access where verification is required.

Data Rights and Control

Policy updates

This Privacy Policy may be updated where changes occur in platform structure, legal requirements, data processing methods, or security practices. Updated versions replace previous versions. Continued use of the platform after updates may be treated as acceptance of the revised policy.

Users are encouraged to review the current version periodically to stay aligned with how data is handled.