Privacy Policy: Short, Because There's Nothing to Disclose
This site is built not to collect your data — no analytics, no tracking cookies, no accounts, no advertising — so this policy is mostly a documented absence. Here's the complete picture.
What we don't collect
No analytics or tracking: the site runs no analytics platform, sets no tracking cookies, embeds no advertising or social scripts, and uses no fingerprinting — we don't know who you are, which pages you read, or that you visited at all beyond the ordinary short-lived technical logs any web server produces (IP-level request logs kept briefly by hosting infrastructure for security and reliability, not used to profile anyone). No accounts or profiles: no sign-up, no login, no personalisation of any kind. The calculators run entirely in your browser: every tool — the cost-per-hour, the wagering pricer, the limit planner and the rest — computes client-side in JavaScript; no figure you enter (not a stake, not an income) is stored, transmitted or visible to us, architecturally. No third-party data sharing: none exists to hand over.
The two things that do exist
Email, if you write to us: messages to hello@casinosunitedkingdom.com naturally include your address and whatever you send; we use them only to reply and fix what you've reported, we add you to no list (we have none), and we'll delete correspondence on request — please never send account credentials, identity documents or financial details, per the contact page. Outbound links: where the site links to external resources — the Gambling Commission, GAMSTOP, GamCare, GambleAware — those sites' own privacy policies apply once you're there; we link to no casinos and no advertisers, so the outbound surface is small and public-interest by design. Your rights: UK data protection law gives you access and deletion rights over any personal data we hold — and per the above, the honest answer to such requests will almost always be at most an email thread — via the same address. Only a change to the site's architecture would change this policy — if that day comes, the date below moves and the standards page's loudly-first rule applies.