Privacy layer
Privacy and Cookies
A plain-English note on what crazy-time.uk collects, what stays on the device, and which details still need operator legal review before final publication.
Privacy layer
A plain-English note on what crazy-time.uk collects, what stays on the device, and which details still need operator legal review before final publication.
Data minimisation
Use the hub without creating an account. The current static build asks for no name, email, password, date of birth, payment details or registration profile.
Hosting, security and API delivery can create technical logs such as IP address, requested URL, browser type, device class, referrer, approximate location and timestamp. Those records are used to operate pages, protect the service, debug live-feed problems and understand traffic at an aggregate level.
Cookies
Check the banner before accepting non-essential cookies. The reviewed static files do not currently include Google Analytics, Clarity, Hotjar, Meta Pixel or a cookie banner script.
If an analytics stack or marketing tag is added, the provider name, purpose and consent route must be confirmed in this policy before launch. Necessary cookies or edge security signals may still be used where required to deliver pages, route affiliate protection or keep abuse controls working.
Browser storage
Some tools may keep preferences in the browser if a future version ships saved tabs, player settings or a personal watch panel. That storage should stay on the device unless the interface clearly says it is being sent to a server.
Clear browser storage to remove local preferences. The current code scan found no use of localStorage, sessionStorage or IndexedDB in the static build, so any future storage module needs a fresh privacy review before it goes live.
Outbound services
Follow operator links with the expectation that the destination has its own privacy policy, cookies and account checks. crazy-time.uk does not send account data to those operators because the hub does not hold accounts.
Support links may point to organisations such as BeGambleAware, GamCare and GAMSTOP. Live data and media should be served through the project's own infrastructure where possible; any third-party embed or CDN added later must be listed during operator review.
Retention
Technical logs are handled on the basis of legitimate interest in operating, securing and improving the service. Consent is the expected basis for non-essential analytics or marketing cookies if those are added.
The site is served over HTTPS and deliberately avoids accounts, deposits and payment data. Retention periods for hosting logs, API logs and any analytics provider must be confirmed by the operator before this page is treated as final legal copy.
UK GDPR
Under UK GDPR, users may ask for access, correction or deletion of personal data held about them, and may object to or restrict certain processing. Users may also complain to the Information Commissioner's Office.
The final controller name and privacy contact route are pending operator legal confirmation. Until those details are signed off, privacy requests should be routed through the operator's published contact channel and recorded for counsel review.