Privacy Policy
Privacy policy text describes how personal data is collected, processed, stored, and protected when users access the betting and casino service. The operator processes data under applicable privacy standards tied to its gaming licence.
Data Controller
Pelican Entertainment B.V. acts as data controller for account and service information. Billing agents Edric Ltd and Faren Ltd may process payment-related data as authorised processors.
Pelican Entertainment B.V. acts as controller for account and payment data processed through the Melbet India service. Billing agents may process transaction data as processors or separate controllers where stated.
Satellite sites that describe Melbet India still point to Pelican Entertainment B.V. as the operator holding player data. Indian users exercising rights should name the Melbet account ID in the request.
Information Collected
Collected data may include name, date of birth, contact details, account credentials, transaction history, betting activity, device identifiers, IP address, and verification documents submitted for KYC.
Registration fields, device data, bet history, and payment references are typical categories. Live chat transcripts may be stored to resolve disputes.
App installs add device identifiers and crash logs. UPI and IMPS create payment references stored for AML. Indian users who contact chat create a transcript linked to the profile.
Purpose of Processing
Data supports account creation, payment processing, fraud prevention, legal compliance, customer support, marketing where permitted, and improvement of site performance. Processing occurs only for defined legitimate purposes.
Data supports account access, fraud prevention, bonus eligibility, withdrawals, and regulatory duties. Marketing messages follow consent rules where required.
Responsible gambling limits need deposit and session data to enforce caps. Indian users who request self-exclusion rely on that processing. Marketing can be switched off where a preference centre exists.
Legal Basis
Processing relies on contract performance, legal obligations, legitimate interests, and consent where required by law. Users may withdraw marketing consent without affecting core service data needed for the account.
Contract performance, legal obligation, and legitimate interests cover most processing. Consent applies where the banner or form requests it.
Licence and AML duties are not optional even if an Indian user wants data minimised. Contract basis covers bet settlement. Consent is the basis for non-essential cookies and some newsletters.
Data Sharing
Information may be shared with payment providers, identity verification vendors, regulatory bodies, and technical partners under confidentiality agreements. Data is not sold to unrelated third parties for their independent marketing.
Regulators, payment partners, and fraud vendors receive data only as needed for their role. Ambassadors and marketing partners do not receive full account dossiers.
KYC vendors compare ID images. Banks and UPI apps receive only what a payment needs. Indian users’ data is not listed for sale. Courts or regulators may compel disclosure.
Data Retention
Records are kept for the period required by gaming regulation, tax law, and dispute resolution. After closure, certain data may remain archived for compliance before secure deletion.
Retention mirrors licence and bookkeeping duties. Closed accounts may keep limited records for dispute windows.
Bet history often outlives a closed account because of dispute and licence clocks. Indian users asking for erasure still leave legally required traces. Marketing lists can be dropped faster than payment records.
Security Measures
Technical and organisational controls include encryption, access restrictions, and monitoring designed to reduce unauthorised access. No online system guarantees absolute security.
Encryption in transit, access controls, and staff permissions reduce unauthorised access risk. No online service can promise absolute security.
Staff access is role-based. Indian users should enable device lock and unique passwords. SMS OTP is a second factor, not a reason to reuse the account password elsewhere.
User Rights
Users may request access, correction, deletion, restriction, or portability of personal data where applicable law grants those rights. Requests are submitted through [email protected] with identity confirmation.
Access, correction, and deletion requests follow applicable law and identity checks. Some records must stay for licence reasons even after a closure ask.
Access packs may exclude third-party studio data held only by Evolution or payment processors. Indian users can still request what Melbet stores. Identity matching is required before files leave support.
International Transfers
Data may be processed in jurisdictions outside the user's country with safeguards consistent with licence obligations and applicable transfer rules.
Data may move to servers and vendors outside India under contractual safeguards. Licence jurisdiction remains Curaçao for the operator.
Curaçao licensing, EU or other vendor clouds, and India-facing support can all see parts of a file. Clauses in vendor contracts set transfer safeguards. Indian users accept cross-border processing when they register.
Policy Updates
This privacy policy may be revised when practices or law change. Material updates appear on this page with an updated effective date.
Updated privacy text posts to this page with a new date. Significant changes may also appear in account messages.
Material purpose changes may need a new consent for marketing. Operational tweaks post silently with a new date. Indian users who keep the registered email receive the notices that matter.
Contact
Data protection enquiries go to [email protected].
Privacy questions: [email protected] with subject Privacy Request, or via contacts. Cookie controls are described in cookie information. The official Melbet site remains the account entry point.
Use a clear subject and the registered name. Indian users sending from a different inbox should include the account ID and registered phone.