How we protect it
Security
The architectural choices that reduce risk today, how to report a vulnerability, and what we will not overstate.
The promise
Security posture is described in terms of what the system actually does, not in badges.
Architecture that reduces exposure
The most reliable protection is not holding sensitive data in the first place. This site has no user accounts, no payment processing, no wallet, no deposits and no identity documents — the categories that make a breach serious are simply absent.
- Transport
- All traffic is served over HTTPS.
- Credentials
- Provider API keys are read server-side inside request handlers and are never exposed to the browser bundle.
- Payments
- None processed. No card or bank data is handled anywhere in the stack.
- Server boundary
- The AI Analyst calls the model through a server-side route; the client never holds the gateway key.
Reporting a vulnerability
If you believe you have found a security issue, report it privately before disclosing it publicly. Include the URL, the steps to reproduce, and what an attacker could obtain. We will confirm receipt, investigate, and credit reporters who ask to be credited.
Please do not run automated scans that degrade service for other readers, do not attempt to access data that is not yours, and do not use social engineering against anyone associated with the site.
Ongoing review
Backend security posture is reviewed as part of the build process, including access rules on any stored data. Findings are fixed rather than documented; unresolved findings are never listed publicly, because a public list of open holes is itself an attack aid.
Sources
- Source: SportsWager.com editorial desk — Security standard, published on this site · Retrieved: 2026-08-01
Last reviewed: 2026-08-01
Owner-published documentation for SportsWager.com, not an independent certification or audit. SportsWager.com is an information platform. It is not a sportsbook and accepts no wagers.