Lucy Bet Privacy Policy

Before you provide a phone number, upload an identity document or request a withdrawal, you should understand why that information is needed. Lucy Bet respects your privacy and is committed to protecting personal information. We collect account, verification, payment, betting, device and communication data to deliver services, protect accounts and meet applicable obligations. You can raise privacy questions through Contact Us.

This policy covers the website, mobile version, app, account services, sports and live betting, games, Keno, bonuses, payments, support channels and communications. It applies to visitors, registered players and people contacting support before registration, whether in Addis Ababa or elsewhere in Ethiopia. “Personal data” means information identifying you, directly or indirectly; “processing” means collecting, using, storing, sharing or deleting it.

Who We Are

Lucy Bet is the betting and gaming brand through which services are offered to eligible adult users in Ethiopia. In this policy, “we” refers to the operator responsible for these services. For operator identification and service information, consult About Us. Check License & Regulation and the competent authority’s latest information to verify current licensing and regulatory status. Availability is subject to applicable Ethiopian laws and regulations, relevant license conditions and regional restrictions.

Information We Collect

The Lucy Bet personal data needed depends on your interaction with us. Browsing does not normally require the same information as opening an account or completing a withdrawal. Collection should be limited to information necessary for lawful, operational, security and regulatory purposes.

• Account data: name, phone number, email, date of birth, username and password-related security data used for registration and authentication.
• Verification data: identity documents, age-check results, customer due diligence records and fraud-prevention information. KYC means “Know Your Customer”: checks to establish who holds an account and whether they are eligible.
• Transaction data: deposits, withdrawals, payment method details, payment references, balance history and bonus activity.
• Betting and gaming data: selections, stakes, odds, results, live betting activity, Keno entries and game sessions.
• Technical data: IP address, device type, browser, operating system, app version, cookies and log files.
• Communication data: support messages, complaints, emails, chat logs and call information, including recordings where used and appropriately disclosed.
• Responsible gaming data: limits, self-exclusion requests, relevant risk indicators and account restrictions.

Do not send unrelated sensitive information or another person’s documents. If verification is requested, use the designated submission channel rather than posting documents in a public message.

How We Use Personal Data

We use betting account data to create and manage accounts, confirm identity and age eligibility, enable secure login, process deposits and withdrawals, settle bets and winnings, and administer bonuses and promotions. For example, matching account-holder information with a withdrawal request helps establish whether payment is going to the entitled person.

Activity records also support checks for multiple accounts, payment abuse, bonus abuse, fraud and suspicious betting patterns. Technical and support information helps us investigate faults, improve the website, app and games, and respond to complaints. A disputed live bet may require its recorded acceptance time, odds and settlement result.

Other purposes include service notifications, responsible betting measures and applicable legal, tax, accounting, anti-money laundering (AML), licensing and regulatory duties. Marketing is sent only where allowed, with available opt-out options. Declining marketing does not prevent essential account or security notices.

Legal Basis / Lawful Reasons

The lawful reason for processing depends on the information and purpose involved. It may be necessary to provide requested services, comply with legal obligations, protect users and the platform, prevent fraud or resolve disputes. Where consent is required, processing must follow that requirement; withdrawing consent does not invalidate earlier lawful processing.

These descriptions do not assume that every legal ground applies to every activity. Our compliance team should confirm the specific grounds and requirements under the applicable regulatory framework. You can ask us to explain the reason for a particular use of your information.

Cookies and Tracking

Cookies are small files stored on your device; similar technologies can recognise a browser or app session. They may keep you logged in, remember preferences, protect accounts, analyse traffic and improve performance. Marketing measurement may also be used where permitted and subject to applicable consent requirements.

Browser controls and app permissions offer different options, so review both when comparing mobile access methods. Blocking essential cookies can affect login or payment functions. See the Cookie Policy for further information on cookies and available controls.

Data Sharing

Lucy Bet does not sell personal data as a product. Necessary information may be shared with third-party service providers—external businesses helping deliver or protect the service—including payment processors, identity verification providers, hosting and cloud providers, analytics and security tools, and customer support tools.

Professional advisers may receive relevant records for advice or disputes. Regulators, law enforcement or courts may receive information when legally required. Third-party access should be limited to the stated purpose, with appropriate confidentiality, security and contractual controls. A payment provider, for instance, need not receive your complete gaming history simply to process a transaction.

International Transfers

Some providers may store or process Lucy Bet player information outside Ethiopia. Where this happens, transfers must follow applicable legal requirements and use suitable safeguards for the information involved. Location alone does not establish how well data is protected; access controls, provider obligations and lawful transfer arrangements also matter. Contact us with questions about overseas processing.

Data Storage and Retention

Records are retained only as long as necessary for account operation, financial records, legal obligations, dispute resolution, fraud prevention, responsible gaming and regulatory requirements. Retention may differ between a support enquiry and a verified transaction record.

Closing an account does not necessarily remove all records immediately. Information still required for a lawful purpose may be retained with restricted access; once no longer needed, it should be securely deleted or anonymised. Ask us about the retention rules relevant to your request.

Security Measures

Lucy Bet data protection relies on reasonable technical and organisational measures. Depending on the system and information involved, these include encryption where appropriate, access controls, secure login systems, monitoring, staff confidentiality, backups, fraud detection and internal handling procedures. No online service can promise absolute security.

To support Lucy Bet account security, use a unique password and keep authentication codes private. Access Lucy Bet login through a verified official address, not an unsolicited message. Before installing an app or APK, confirm its source through an official communication channel and review permissions. Report unfamiliar logins or transactions promptly; support should not need your password to investigate.

User Rights

Depending on applicable data protection laws, you may request access, correction, deletion, restriction, objection or information about processing. Some requests may be limited because records must remain available for legal, financial, security or regulatory reasons. Identity checks may be needed before we disclose or change account information.

1. Step 1: Use Contact Us and explain your Lucy Bet privacy question or the right you wish to exercise.
2. Step 2: Provide enough account information to locate the record, but do not send passwords or unnecessary documents.
3. Step 3: Follow any proportionate verification request through the authorised channel and keep the reply or reference for follow-up.

Ask support about the complaint-handling procedure if a concern remains unresolved. Applicable law may also provide a route to a competent authority.

Age Restrictions and Children’s Data

Services are intended only for eligible adults. Lucy Bet must not knowingly collect personal data from underage users. If you believe a child has submitted information, contact support so the account and records can be reviewed and handled under applicable requirements. Parents, guardians and users can consult the Age Restriction Policy.

Responsible Gaming and Account Restrictions

Account activity, deposit limits, self-exclusion requests and relevant risk indicators may be processed to support responsible gaming and enforce restrictions. Certain records may need to remain after closure to help prevent access during an exclusion period. These purposes should not justify collecting unrelated personal information. See Responsible Gaming for available controls and assistance.

Terms, Bonuses, and Payments

This privacy policy in Ethiopia should be read alongside the Terms and Conditions, applicable bonus rules, payment checks and anti-fraud controls. Before registration or a payment, check eligibility, KYC requirements, transaction limits, disclosed fees, processing times and the withdrawal procedure.

When comparing payment options, use published requirements rather than assuming every method has identical checks. Bonus activity may be reviewed against promotion conditions; payment authorization and identity verification serve different purposes. Keep your record of transaction and ask support about unclear requirements before supplying additional data.

Updates to This Policy

This policy may change when services, laws, security practices or processing activities change. The revised version will be made available on this page, with additional notice where required. Review it when using a new feature or responding to a new information request, and contact us if the purpose or handling of that information is unclear.