1. Information We Collect
We collect the information needed to operate OddsOps, manage access, track picks, process subscriptions, and protect the platform.
- Account information: name, username, email address, profile image, provider IDs, and linked account identifiers from Discord, Google, or Whop.
- Subscription information: membership status, plan identifiers, checkout status, renewal or cancellation status, and payment-provider references.
- Bet and pick activity: tailed picks, manual bet logs, units, odds, selected bookmakers, statuses, and share-card settings you choose to save.
- Technical information: IP address, user agent, request paths, device/browser details, logs, error details, and rate-limit records.
- Community and social data: Discord identifiers needed for role access, and X post metadata when OddsOps posts approved public cards or recaps.
We do not receive or store your Discord, Google, Whop, or X password.
2. Payment Data
Billing is handled by Whop. OddsOps does not store your full credit card number, CVV, or complete payment details. We receive the account and subscription information needed to grant or remove access.
3. How We Use Information
- Create and secure your account
- Authenticate sign-ins and linked providers
- Manage subscription access and Discord roles
- Show picks, history, analytics, and bet tracking tools
- Generate share cards and approved social drafts
- Maintain public pick records and performance history
- Detect abuse, rate-limit requests, and diagnose errors
- Send service, billing, or support communications when needed
4. Third-Party Services
We use third-party services to run OddsOps. Each receives only the information needed for its role.
- Discord: sign-in, community access, role management, and alerts.
- Google: optional sign-in.
- Whop: sign-in, checkout, membership management, payment processing, and billing status.
- X: approved public posting from the official OddsOps account.
- Supabase/Postgres: database hosting for account, pick, and analytics records.
- Vercel: site hosting and standard web request logs.
- Upstash: Redis-backed rate limiting.
- Sentry: error tracking and limited performance monitoring. Session replay is disabled.
- Google Analytics: site traffic measurement when enabled.
5. What We Do Not Do
- We do not sell your personal data.
- We do not use your payment card number because we do not receive it.
- We do not use X data to train AI or machine-learning models.
- We do not send unsolicited X direct messages from automation.
- We do not use advertising cookies or cross-site tracking pixels in the core app.
6. Cookies
We use a small number of cookies for sign-in, account security, checkout flows, preferences, and basic site operation. See our Cookie Policy for more detail.
7. Data Retention
Account data is kept while your account is active or as needed for support, security, billing, legal, or operational reasons. Pick records are retained as part of the public OddsOps track record.
If you delete your account, we will remove or anonymize personal account identifiers where practical. Historical pick records may remain in non-personal or public aggregate form.
8. Your Choices
- Request a copy of personal data we hold about you
- Request correction of inaccurate account data
- Request deletion of your account
- Cancel paid access through the billing provider
- Disconnect third-party account access where supported
9. Security
We use environment variables or secret managers for credentials, HTTPS for production traffic, provider-based sign-in, and access controls for private features. No online service can guarantee perfect security, but we work to limit access to the data needed to operate OddsOps.
10. Changes To This Policy
We may update this policy as OddsOps changes. Material updates may be communicated through the site, Discord, email, or another reasonable channel.
11. Contact
Questions about privacy? Contact us through Discord or email support@oddsops.com.