bet builder melbet
melbet official app
melbet bet race

TOP MATCHES

Privacy Policy

Scope and India context

What this policy covers

This policy describes how Melbet may collect and process personal data when users in India access the service, create an account, complete verification, or use wallet functions.

Jurisdiction note

Data protection and consumer requirements may differ across jurisdictions. Where a specific requirement is not described here, users should check the official privacy policy and terms available in the account area.

Service identifiers and controller details

Service identifiers

ItemValue
BrandMelbet
Primary domain identifiermelbet; india.melbet
OperatorPelican Entertainment B.V.
Company number134359

Data controller or responsible entity

Not provided. Check official privacy policy and terms in account area.

Categories of data

Data users may provide

CategoryExamples
Account dataName, date of birth, login details, account settings
Contact dataEmail address, phone number, support communications
Verification dataIdentity documents, address evidence, age confirmation
Payment dataTransaction references and wallet history

Data collected through service use

CategoryExamples
Device and log dataDevice identifiers, IP-related data, timestamps
Usage dataPages or screens viewed, session events
Security signalsFraud indicators, risk checks, failed login attempts

Purposes and legal bases

Why data may be processed

PurposeTypical legal basis
Provide the service and manage the accountContract performance
Verify identity and eligibilityLegal obligation or legitimate interests
Process transactions and prevent fraudContract performance and legitimate interests
Provide support and handle complaintsContract performance or legitimate interests
Improve security and service reliabilityLegitimate interests
Marketing communications were enabledConsent, where applicable

Retention

How long data is kept

Retention period: Not provided. Check official terms and policy in the account area.

Factors that may affect retention

FactorEffect
Legal or regulatory dutiesMay require longer storage of specific records
Dispute or complaintMay require preservation until resolution
Fraud preventionMay require retaining security logs for defined periods

Cookies and similar technologies

What cookies may be used for

TypePurpose
EssentialCore site functionality, authentication, security
PreferencesLanguage and interface settings
AnalyticsAggregate measurement of performance and usage
AdvertisingShown only where enabled and permitted

Cookie details: Not provided. Check cookie notice in the account area.

Sharing and recipients

Who may receive data

Recipient typeWhy
Payment processors and financial partnersTo process deposits and withdrawals
Identity and fraud prevention providersTo verify users and reduce fraud
IT and hosting providersTo operate the service infrastructure
Professional advisersLegal, audit, and compliance support

Specific processors: Not provided. Check official policy in the account area.

Cross-border transfers

Transfer approach

Personal data may be processed in locations where service providers operate. Transfer safeguards: Not provided. Check official policy in the account area.

Security

Measures typically used

MeasurePurpose
Access controlLimit internal access to authorized staff
EncryptionProtect data in transit and, where used, at rest
MonitoringDetect suspicious activity and attacks
Incident handlingInvestigate and respond to security events

No security method eliminates all risk. Users should also protect their devices and credentials.

User rights and requests

Rights users may have

RightWhat it means
AccessRequest a copy of personal data where applicable
CorrectionRequest correction of inaccurate data
DeletionRequest deletion where legally permitted
Restriction or objectionRequest limits on certain processing
Consent withdrawalDisable consent-based processing where applicable

Availability of rights depends on applicable law and the service relationship.

How to submit a privacy request

  1. Identify the request type

    Access, correction, deletion, or objection.

  2. Provide identification details

    Provide information needed to verify you are the account holder.

  3. Submit through the data contact or support

    Use the contacts listed below and include “Privacy request” in the subject line where possible.

  4. Await verification and response

    Additional verification may be required for account security.

Contact information

Support channels

Data contact

Not provided. Submit requests via support channels.

Document updates

Last updated: Not provided