Trust
Security
Precision is the product, and precision only means something if the numbers can be trusted. Here is how we protect accounts, scores and data.
Account security
Accounts are protected today by password authentication with standard hashing and rate-limited sign-in attempts. Multi-factor authentication and passkey support are on our roadmap, and will ship before any paid feature is introduced.
Server authority
Clients never write a final score. Every competitive run is submitted as a timestamped event log, and the server replays that log to calculate the result — the number shown on screen at the end of a run is a preview, not the record. Database access follows deny-by-default row-level security: a client can only read or write the rows it is explicitly permitted to touch.
Match seeds are sealed: a SHA-256 commitment is published before play, and the seed itself stays in the database, unreadable by clients, until the match settles and the reveal happens. See fair play & verification for the full mechanics.
Data protection
We collect the minimum personal data needed to run the service: account details, gameplay event logs and basic device and region metadata. Event logs exist to verify results and support anti-cheat review — not to profile players. Full detail is in the privacy notice.
Responsible disclosure
If you find a security issue, tell us before you tell anyone else. Email webmaster@betgames.co.uk with enough detail to reproduce it. We will acknowledge reports and keep you updated as we investigate.
Honest scope
Pre-launch: hardening in progress
BetGames has not launched publicly and is still undergoing security hardening. Nothing on this page should be read as a claim of independent certification or audit completion — where a claim like that becomes true, we will link the evidence here rather than assert it in prose.