Privacy Policy
Last updated: draft, not yet published.
1. What we collect
| Data | Why | Retention |
|---|---|---|
| Email, password hash | Authentication | No automated deletion in this release; final policy pending |
| SharpSports account/bet-slip ids and synced bet history (stakes, outcomes) | Bet tracking and analytics, if you connect a sportsbook | No automated retention or deletion in this release; final policy pending |
| Account balances (if synced) | Account status display | Latest value only |
| Webhook delivery payloads | Durable processing and audit trail | No automated retention job in this release; final policy pending |
| Responsible-gaming limits and history | Enforcing your own limits; first caps and decreases apply immediately, while increases and removal are rejected | Permanent, immutable history |
2. What we never collect
Sportsbook login credentials and one-time OTP codes are never collected, stored, or logged by this service — linking your sportsbook account happens on SharpSports’ own hosted UI, outside of our systems.
3. Sharing
We do not sell or share your data with third parties for marketing. Data is processed by:
- SharpSports (odds and, if you connect an account, bet-sync data provider)
- Neon (database hosting)
- Vercel (application hosting)
4. Your rights
This draft does not yet define a verified request channel or a production process for a complete account export or deletion. Authenticated users can download a bounded CSV of their normalized tracking rows; that file is not a complete account-data export and excludes raw provider payloads. There is no self-service deletion workflow. Before publication, qualified counsel and the platform owner must approve an identity-verification, response, retention, and deletion process. Responsible-gaming limit history is append-only in the current system and can only be superseded.
5. Security
Passwords are hashed with scrypt (never stored in plain text). Sessions are stored as SHA-256 hashes of opaque tokens, never the raw token. See the project’s threat model documentation for further detail.