This site uses cookies for four practical reasons: to make pages work, to remember your display preferences, to measure how pages are used, and to record that a referral came from here so affiliate commission can be credited. You can refuse everything except the strictly necessary group, either through the cookie prompt or through your browser's privacy settings. Attribution cookies do not change your odds, your bonus eligibility or your account terms.
A cookie is a small text file that a website asks your browser to store, and that your browser hands back the next time you visit. It is not a program and it cannot run anything on your device. It is closer to a cloakroom ticket than to software — a short string that lets a site recognise the same browser twice without you having to identify yourself again. Related technologies such as local storage and pixels work differently under the bonnet but serve much the same purpose, and everything described on this page applies to them too.
A session cookie lives only while the browser tab or window is open and is discarded when you close it. A persistent cookie carries an expiry date and survives being closed, which is what lets a site remember a choice you made last week. Session cookies handle the mechanics of a single visit; persistent ones handle memory across visits.
A first-party cookie is set by the domain in your address bar — this site. A third-party cookie is set by some other domain whose content is loaded into the page, such as an embedded video or an analytics script. We control the first group. We do not control the second, only whether that content is embedded at all.
Rather than list individual cookie names — which change whenever a plugin or provider updates and are therefore out of date the moment they are published — this policy describes cookies by what they do. Lifetimes are given as ranges, because the exact values are set by the software concerned and can change without any decision on our part.
This is the category most sites bury, so here it is in plain terms. When you click a link from this site to an operator, the destination address usually carries a tracking parameter, and a cookie may be set on the way through. Between them they record one thing: that this particular referral came from u88betting.com. If you go on to open an account, the operator's affiliate system matches that record and credits a commission to us. That is how the site is paid for.
What that record does not do is more important than what it does. It does not change the odds you are shown on any market. It does not make you eligible for a better or worse promotion than someone who arrived by typing the address directly — the welcome bonus, the daily rebate, the weekly rescue bonus and the streak bonus are the operator's offers on the operator's terms, and terms apply to all of them regardless of how you got there. It does not alter your account terms, your limits, or how withdrawals are handled. And it does not give this site any visibility into your account, your balance or your bets.
It also has an expiry, and the expiry is set by the operator's affiliate system rather than by us. If you click through today and open an account long afterwards, the attribution may simply have lapsed. Nothing about your account is affected either way. If you would rather no attribution be recorded at all, block third-party cookies and strip tracking parameters, or reach the operator by typing its address directly — the site works the same for you and you should not feel obliged to do otherwise.
When a page includes content served from another domain — an embedded video, a social widget, a font or script host, an analytics provider — that domain can set its own cookies when the content loads, under its own policy and its own retention period. We do not write those cookies, we cannot inspect them, and we cannot delete them on your behalf. Our only real control is the decision to embed the content in the first place, which is why we keep embeds to a minimum.
The general principle is worth understanding beyond this site: any time third-party content appears inside a page, you are dealing with that third party as well as the site you are visiting. If you want to know what a given provider stores, its own privacy and cookie documentation is the authoritative source. Blocking third-party cookies at browser level is the blunt but effective answer, with the trade-off that some embedded content will not render.
Two layers of control exist. The first is the cookie prompt on this site, where you can accept or decline the optional categories and change your mind later. The second is your browser, which overrides everything a website asks for and is the control worth learning, because it applies everywhere rather than only here.
Open Settings, find the privacy or privacy-and-security section, then the cookies or site-data entry. From there you can block third-party cookies, clear existing data, or set exceptions for individual sites.
Open Settings or Preferences and go to the privacy section, where cross-site tracking prevention and stored website data are managed. On iPhone and iPad the same controls sit under Settings, then Safari.
Open Settings and go to privacy and security, where the tracking-protection level, cookie handling and an option to clear data on close are grouped together.
Every major browser offers a private or incognito window that discards cookies when the window closes. Useful for a one-off visit, but it does not make you anonymous to the sites you use.
Menu names shift between versions, so treat the paths above as a direction rather than an exact route: settings, then privacy, then cookies. One warning worth taking seriously — blocking strictly necessary cookies breaks things. Consent prompts reappear on every page load, security checks may fail, and some pages may not load at all. If a site behaves strangely after you tighten these settings, that is usually the cause rather than a fault with the site.
Browsers can send a signal indicating that you do not wish to be tracked — the older Do Not Track header, and newer global privacy signals that some browsers and extensions send in its place. It is worth being factual about what these achieve: support varies considerably across browsers, and support varies even more across the websites receiving the signal. There is no single standard that every site is obliged to honour, and some jurisdictions treat certain signals as legally binding while others do not.
The practical consequence is that sending such a signal is worth doing but should not be relied on as your only protection. Browser-level cookie controls and the consent choices you make on each site remain the tools that actually take effect, because they operate on your device rather than depending on the good behaviour of the site at the other end.
This policy is updated when what the site actually does changes — when an analytics tool is added or removed, when an embed is introduced, or when the way attribution works is altered. The revised version replaces the old one on this page and the date shown on the page is updated at the same time, so the date is a reliable indicator of when the described behaviour was last accurate.
Where a change materially expands what is collected, we will make it visible rather than relying on you to notice a new date — in practice, by re-presenting the consent prompt so the choice is put in front of you again.
Questions about this policy, or about anything the site stores on your device, can be sent through the contact form on this site. Tell us which page you were on and what you want to know, and we will answer with what we actually know rather than with boilerplate. If a question concerns your account with an operator rather than this website, that has to go to the operator directly — we have no access to accounts, balances or betting records.
18+. Play responsibly.