Privacy policy

Data Collection & Platform Scope

This Privacy Policy defines how MDM Bet India handles user-related information within a controlled digital environment. The platform operates as an interface layer where data collection is structured around functionality, security, and compliance rather than behavioral prediction or outcome optimisation.

Data is collected to enable account access, maintain system integrity, process transactions, and ensure compliance with applicable regulatory frameworks. The platform does not collect data for the purpose of influencing game outcomes, modifying RTP models, or altering RNG behavior.

Types of Data Collected

User data may include:

• account registration information (name, contact details)
• technical data (device, browser, IP)
• transaction-related data (deposits, withdrawals)
• verification data (identity checks when required)

This data is collected either directly from the user or automatically through system interaction.

Functional Purpose of Data

Each data category exists within a defined purpose:

• access control
• fraud prevention
• transaction processing
• compliance verification

Data is not used to:

• predict individual outcomes
• influence gameplay
• modify probability distributions

RNG systems remain independent and unaffected by user data.

Data Boundaries

The platform maintains separation between:

• account data (identity, login)
• transaction data (payments, balance)
• system data (technical interaction)

These layers are processed independently where possible to reduce risk exposure and ensure structural clarity.

User Awareness

Users retain visibility over their account information and may request clarification regarding stored data categories. The platform aims to keep data usage understandable rather than abstract.

Data collection is limited to what is necessary for operational functionality.

Data Usage, Storage & Protection Framework

Data within the platform is processed through clearly separated operational layers. Each layer serves a defined purpose and is not used outside of its functional scope. The system does not aggregate data to influence gameplay mechanics or to derive predictive behavioral models.

Data usage is limited to:

• enabling account access
• maintaining transaction integrity
• supporting verification procedures
• ensuring platform security

No data layer interacts with RNG systems, RTP models, or volatility distribution.

Storage Logic

User data is stored within controlled environments with access limitations based on role and function. Storage systems are segmented to reduce exposure and to prevent unnecessary cross-layer interaction.

Retention periods depend on:

• account activity
• legal obligations
• fraud monitoring requirements

Inactive data may be archived or removed in accordance with applicable compliance standards.

Security Measures

The platform applies technical and procedural safeguards, including:

• encrypted data transfer
• restricted access layers
• monitoring for unauthorized activity
• anomaly detection

Security systems operate continuously and are designed to detect irregular patterns such as unauthorized access attempts or data misuse.

Data Retention

Data is not stored indefinitely without purpose. Retention is based on operational necessity rather than convenience.

Users may request data clarification or deletion where legally applicable. Some data may remain stored if required for compliance, fraud prevention, or legal obligations.

Data Layers & Protection Model

User Rights, Third-Party Access & Data Control

Users retain control over their personal data within the limits of applicable law and operational requirements. The platform is structured to allow visibility, clarification, and controlled modification of stored data where appropriate.

Users may request:

• access to stored personal data
• correction of inaccurate information
• deletion of data where retention is not legally required
• clarification of how specific data categories are used

Requests are processed through internal review procedures. Where identity verification is required, additional confirmation steps may apply before changes are executed.

Cookies and Technical Tracking

The platform uses cookies and similar technologies to maintain session continuity, support functionality, and improve system stability. These tools do not interact with gameplay logic and do not influence RNG, RTP, or volatility.

Cookies may be used for:

• login session persistence
• security checks
• basic analytics (non-predictive)

Users may control cookie behavior through browser settings. Limiting cookies may affect certain platform features.

Third-Party Services

Some platform functions rely on external providers, including:

• payment processors
• identity verification services
• infrastructure and hosting systems

These providers operate under their own privacy frameworks. The platform does not extend control over third-party policies but selects providers based on operational reliability and compliance alignment.

Data Transfers

Where data is processed through external systems, it may be transferred across jurisdictions depending on infrastructure requirements. Such transfers are handled with safeguards designed to maintain data protection standards.

Dispute and Data Requests

If a user believes their data has been handled incorrectly, they may contact platform support with relevant account details. The platform will review the request and may request supporting information to validate the claim.

Resolution timelines may vary depending on:

• verification requirements
• third-party involvement
• legal obligations

User Rights & Official Data Protection Resources

Data Responsibility & Practical Use Context

This Privacy Policy should be read as a functional explanation of how data exists within the platform environment rather than as an abstract legal layer. The system is designed to use data in a controlled and limited way, aligned with access, security, and compliance needs.

User data is not treated as a predictive asset. It is not used to influence outcomes, adjust gameplay behavior, or create advantage-based models. The platform maintains a clear separation between operational data and game logic systems.

Users are encouraged to approach their data in the same structured way — understanding what is required for access, what exists for compliance, and what remains optional. Account activity, verification steps, and transaction records form part of a standard digital service model rather than a hidden system.

Where data choices are available, they should be made with awareness of how they affect access to features and services. Limiting or modifying certain data permissions may reduce functionality but does not change system behavior.

This policy reflects a controlled environment where clarity is preferred over complexity, and where data is handled as a necessary component of service operation, not as a tool for influence.