Trust
Cookies on NewSlot.co.uk.
We set no cookies of our own. None. The third-party demo player embedded on every slot review page does. This notice tells you which cookies those are, who controls them, the position the ICO takes on third-party iframes like this one, and how to block them today.
What NewSlot.co.uk sets
Nothing. The site is statically built and served from Cloudflare Pages. We use no first-party tracking cookies, no localStorage analytics identifiers, no session cookies, and no preference cookies. The newsletter form does not set a cookie when you submit it.
One narrow exception: when you opt out of our anonymous engagement measurement via the opt-out button, we write a single key to your browser's localStorage so the engagement timer never fires again on this device. That key is your choice, not a tracking marker. It contains no identifier and is never sent to our servers. You can clear it by clearing site data for newslot.co.uk in your browser.
What SlotsLaunch sets
Every slot review page embeds a demo iframe from slotslaunch.com. When the iframe loads, your browser makes a direct request to slotslaunch.com. That request can carry and receive cookies that SlotsLaunch sets and reads. We don't see those cookies, we don't control them, and we don't share data with SlotsLaunch.
SlotsLaunch is a third-party demo provider serving free play of real-money slot games. They are an independent data controller for any cookies their iframe sets. Their cookie and privacy notice lives at slotslaunch.com/privacy-policy. Read theirs alongside this one to see what their iframe does on your device.
The ICO position on third-party iframes
Under the UK Privacy and Electronic Communications Regulations and ICO guidance updated in 2024 to 2025, a website operator is responsible for cookies set through the site, including cookies set by third-party embedded content like iframes. The fact that we don't control SlotsLaunch's cookies does not remove the responsibility to disclose them and to give you a way to refuse.
We are honest about where we are on this. Today, the SlotsLaunch iframe loads as soon as you open a review page. We are working on a consent gate that blocks the iframe until you explicitly press a button to load the demo. Until that ships, the controls in the next section are how you refuse.
How to block them today
Three options, ordered by strength.
- Don't load review pages with a demo embed. The homepage, calendar, demo catalogue index, provider pages, and most editorial pages contain no iframe and set nothing. The cookies only arrive when a SlotsLaunch demo iframe loads.
- Browser-level blocking. Most modern browsers let you block third-party cookies entirely. Safari, Firefox, and Brave block them by default. Chrome users can enable the same setting in Settings → Privacy and Security → Third-party cookies. With this enabled, the SlotsLaunch iframe still loads but its cookies are rejected by your browser.
- Browser extensions. uBlock Origin, Privacy Badger, or a similar extension can block requests to slotslaunch.com entirely. With this enabled, the iframe will not load at all. The review prose and verdict still render normally.
Why we don't show a cookie banner
We set no cookies of our own, so a banner for our own cookies would be a banner about nothing. We are working on a consent gate for the SlotsLaunch iframe specifically, which is the surgical fix the ICO guidance points at. That gate will live on the iframe itself, not as a sitewide popover that you have to dismiss every time you arrive.
The interim version of that fix is honest disclosure on this page plus the browser-level controls above. We are not hiding behind "legitimate interests" for someone else's cookies.
What changes will get called out
When we ship the consent gate, this page will say so on the line below. The change will also be called out in the next Sunday newsletter. If we ever add an analytics platform, a marketing pixel, or any cookie of our own, that lands here first with the lawful basis and the opt-out, before the cookie is set.