Privacy Policy

UK GDPR · Data Protection 2026 · PECR

This Privacy Policy sets out how Amunbet collects, uses and safeguards personal information when someone visits this website or uses this service.

Amunbet can be browsed without registering an account. For visitors who don't create one, the data processed is mostly technical — what's needed to load the site, keep it secure, and understand how it's performing. Registered players and anyone who contacts support directly will also have the content of that interaction processed, as described below.

This policy is written with reference to the UK GDPR and the Data Protection 2026 . Cookie use is additionally governed by the Privacy and Electronic Communications Regulations (PECR).

1. Who controls this data

Amunbet decides how and why personal data is processed on this site and is the data controller for that processing.

Full contact details for privacy requests are listed on the Contact page and in the site footer. Any request relating to personal data should be sent through those channels rather than through general support chat.

2. Account data

Creating an Amunbet account means providing an email address, date of birth, and a password. Depending on the payment method chosen and the stage of verification, additional data may be requested — full name, address, phone number, and identity documents for KYC purposes.

Account data is used to operate the account, process deposits and withdrawals, run the welcome bonus and other promotions correctly, and meet the identity-verification obligations that apply to a licensed gambling operator.

3. Data collected automatically

Every visit generates some technical data whether or not an account exists:

  • IP address
  • date and time of access
  • pages requested
  • browser type and version
  • device type and operating system
  • language settings
  • referring page
  • server log data

This is used to run the site, keep it secure, investigate errors, and prevent abuse such as bonus fraud or multi-accounting.

4. Data provided directly

If a visitor or player sends a message — through the contact form, live chat, or email — the content of that message is processed: name, email address, the message itself, and anything else the sender chooses to include.

This is used only to handle the specific request, respond to it, and keep a record where that's reasonably needed (for example, disputes or verification follow-ups).

5. Cookies

Amunbet uses cookies for three broad purposes: strictly necessary functions (session handling, security), performance and analytics, and remembering preferences.

Non-essential cookies are only set with consent, given through the cookie banner on first visit. Rejecting non-essential cookies should be exactly as easy as accepting them — one click either way. Consent can be changed at any time through the cookie preference centre linked in the footer.

6. Why data is processed

Personal data is processed to:

  • provide and maintain the website and account services
  • verify player identity as required under the operator's licensing obligations
  • process deposits, withdrawals and bonus eligibility
  • protect the platform from fraud and misuse
  • respond to support requests
  • meet legal and regulatory record-keeping requirements
  • understand site usage in aggregate to improve it

Data collected for one of these purposes isn't repurposed for something unrelated without a proper legal basis.

7. Legal basis

Technical and security data is processed under legitimate interest — running and protecting the site.

Account and KYC data is processed because it's necessary to perform the account contract and to meet the identity-verification obligations attached to the operator's gambling license.

Cookie-based analytics and any optional tracking run only on consent, which can be withdrawn at any time without affecting the rest of the service.

8. Analytics

Where analytics tools are used, they're configured to limit what's collected — page views, device type, load times, error rates — and data is aggregated wherever practical rather than tied to an identifiable individual.

9. Third parties and service providers

Amunbet works with payment processors, identity-verification providers, hosting and security infrastructure, and email/communication tools. Each provider only receives the data needed to do its specific job, under a data processing agreement where required.

10. International transfers

Some service providers may process data outside the United Kingdom. Where that happens, appropriate safeguards apply — adequacy decisions, standard contractual clauses, or another lawful transfer mechanism, depending on the destination.

11. Data retention

Data isn't kept longer than it needs to be. Server logs are retained for a limited period for security purposes. Account and transaction data is retained for the period required by gambling-licensing and anti-money-laundering obligations, which is typically several years after account closure. Support messages are kept for as long as a request is active, plus a reasonable follow-up window.

12. Security

Access to systems handling personal data is restricted, connections are encrypted (HTTPS), and software and infrastructure are kept up to date, backed up, and monitored. No system is unbreakable, but these measures are proportionate to the risk.

13. Your rights

Under UK data protection law, individuals can:

  • request a copy of the personal data held about them
  • ask for inaccurate data to be corrected
  • request deletion in certain circumstances
  • restrict or object to certain processing
  • request data portability where it applies
  • withdraw consent at any time

Requests can be sent through the contact details on the Contact page. Amunbet will respond within the timeframes set by UK GDPR.

14. Complaints

Anyone concerned about how their data is handled should raise it with Amunbet first. There's also a right to complain directly to the Information Commissioner's Office (ICO), the UK's data protection regulator, at ico.org.uk.

15. Changes to this policy

This page is updated when the site, its tools, or the applicable law change. The version published here is the current one; material changes will be flagged to registered users.