| Version | Supported |
|---|---|
| 1.x.x | ✅ |
| < 1.0 | ❌ |
If you discover a security vulnerability in AI Advantage Sports, please report it responsibly.
- Do NOT create a public GitHub issue for security vulnerabilities
- Email security concerns directly to: ian@allowayllc.com
- Include the following in your report:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
- Response Time: You will receive an acknowledgment within 48 hours
- Updates: We will provide status updates every 5 business days
- Resolution: Critical vulnerabilities will be addressed within 7 days
- Credit: Security researchers will be credited in release notes (unless anonymity is requested)
This application handles betting-related financial data. Security considerations include:
- Payment Processing: All payment data is handled by Stripe (PCI compliant)
- User Credentials: Never store passwords in plain text
- Betting Data: User betting history should be encrypted
- API Keys: Never expose API keys in client-side code
- Use HTTPS for all connections
- Store API keys in environment variables
- Enable rate limiting on API endpoints
- Implement proper CORS policies
- Use secure session management
- Validate all user inputs
- Sanitize data before display (XSS prevention)
- Keep dependencies updated
-
Odds API Keys: The Odds API key should be server-side only. Never expose in client bundles.
-
Stripe Integration: Use Stripe's recommended security practices. Never log full card numbers.
-
User Data: Betting preferences and history are sensitive. Handle according to privacy regulations.
-
ML Model Integrity: Ensure prediction models aren't tampered with.
While not a security issue per se, responsible gambling features should be implemented:
- Deposit limits
- Self-exclusion options
- Session time reminders
- Links to gambling addiction resources
We follow responsible disclosure practices:
- Reporter notifies us of vulnerability
- We acknowledge and begin investigation
- We develop and test a fix
- We release the fix and notify users
- After 90 days (or upon fix release), details may be published
- Security Email: ian@allowayllc.com
- General Contact: @ianallowayxyz