SquadSlips
SquadSlips

Privacy Policy

Effective Date: May 17, 2026

Welcome to SquadSlips. We believe your betting data is your business, not ours. SquadSlips is designed with a local-first architecture for your personal betting data. We also use a small amount of anonymous, aggregate analytics on our own servers to understand how the app is used and to keep the service running reliably — never tied to your real identity. This Privacy Policy explains those practices, how we handle the mobile phone number you provide to sign in, and how your information is handled when you use our iMessage extension and application.

1. Age Requirements

SquadSlips is an informational and social tool designed for mature audiences. You must be at least 18 years of age to use this application and view the odds provided. We do not knowingly collect any information from individuals under the age of 18. Please note that while 18 is the minimum age to use SquadSlips, you are solely responsible for complying with the legal sports betting age requirements of your specific jurisdiction, which is typically 21 in the United States.

2. Information Stored Locally on Your Device

The core of your SquadSlips experience lives primarily on your device. We do not store complete betting histories on our servers. The following data is saved locally on your device:

  • Your chosen nickname.
  • Your customized avatar configuration.
  • Your base unit size preferences.
  • Your detailed bet log entries (selections, odds, stakes, outcomes, and timestamps) — these live on your device only. When you share a bet to a chat, an anonymous count of the bet (with sport and bet type only) is sent to our servers for aggregate analytics; the full bet content is not.
  • Your manually selected US state, used solely to filter available sportsbooks locally.

3. Information Shared via iMessage

SquadSlips allows you to share betting cards directly with your contacts via Apple's iMessage platform. When you send a bet card, the following information is embedded in the message payload and shared with the chat participants:

  • Your nickname.
  • The visual representation of your customized avatar.
  • The specific bet selections, odds, and stake amounts for that card.

When the recipients of a shared bet card also have SquadSlips installed, the bet content is additionally synced through our backend so it appears in their app's Active Bets view; see Section 4.

SquadSlips uses Apple's native frameworks to determine if a chat is a group chat to function properly. We do not have access to the phone numbers, Apple IDs, or real names of the people in your conversations.

4. Information Handled by Servers

To provide live odds, sign-in verification, room-based bet sync, push notifications, and basic operational analytics, SquadSlips communicates with our backend infrastructure (operated on Cloudflare Workers). The following categories of data are handled server-side:

  • Live Data: We route requests to fetch live sports data and odds. This is a server-to-server connection; no personal user profiles are transmitted.
  • Device and Session Tokens: When you sign in to SquadSlips, we issue a bearer token tied to a per-install device identifier. This token authenticates your device to our backend. It is associated with your verified mobile phone number (see Section 5) so your account and shared bets stay consistent across sign-ins; it is not linked to your name, Apple ID, or email address. It is stored on our servers in encrypted Cloudflare KV until you sign out, uninstall, or revoke the token.
  • Avatar Configuration: The numeric configuration of your customized avatar (skin, hair, accessories, etc.) is stored alongside your device token so it appears consistently across your shared bet cards.
  • Room-Based Bet Sync: When you share a bet to a group iMessage thread where other participants also have SquadSlips installed, the bet payload (selections, odds, stake, your nickname, and avatar configuration) is stored on our servers for up to 30 days so that recipients can view the bet on their own devices without needing to tap each iMessage card. Bets sent in solo conversations are not stored on our servers; only an anonymous count is recorded (see "Aggregate Analytics" below).
  • Push Notifications: To alert you about game commencements, completions, and bet outcomes, our application registers for Apple Push Notifications. We temporarily store an anonymous APNs device token alongside the specific game IDs you are tracking. This data is retained for a maximum of 7 days for the purpose of delivering notifications and is not tied to your personal identity.
  • Aggregate Analytics: See Section 6.

5. Phone Number and SMS Verification

To let you sign in and to keep your account secure, SquadSlips collects and verifies your mobile phone number.

  • Phone number collection: When you sign in to SquadSlips, you provide your mobile phone number. We use it to confirm that you control that number and to authenticate you on later sign-ins and when you add a new device.
  • One-time verification codes: We send a one-time six-digit verification code to your number by SMS, which you enter in the app to complete sign-in. These codes are short-lived and single-use.
  • SMS provider: Verification messages are sent through Twilio, our SMS and verification service provider, acting on our behalf. Your phone number is disclosed to Twilio only to deliver and verify these codes.
  • How your number is used: Your phone number is used solely to verify your identity and secure your SquadSlips account. We do not use it for advertising or marketing, we do not sell it, and we do not share it with anyone other than our SMS provider as described above.
  • Message frequency and rates: Verification messages are transactional and are sent only when you request a sign-in code — typically one message per sign-in attempt. Message and data rates may apply, depending on your mobile carrier and plan.
  • Opt-out and help: Standard carrier keywords are supported: reply STOP to opt out of further messages, or HELP for help. Because the verification code is required to sign in, opting out will prevent you from signing in. You can also reach us at support@squadslips.com.
  • Retention: Your verified phone number is retained while your SquadSlips account remains active so you can sign in again and recover access. Verification codes themselves are not retained once they expire or are used.
  • Consent: By entering your mobile phone number and requesting a verification code, you consent to receive that one-time verification SMS from SquadSlips.

6. Anonymous Aggregate Analytics

We collect anonymous, aggregate usage data to understand how SquadSlips is used and to keep the service running reliably. The categories of analytics events we record are:

  • Activity counts: how many bets are sent per day, how many devices are active, how many bootstraps occur. These counts are not tied to any individual user; the device identifier is hashed (SHA-256) before it is written to analytics, in a form that cannot be reversed back to your token.
  • Aggregate bet metadata: the sport (e.g. NBA, NFL, golf), bet type (straight, parlay, prop, futures), and number of legs of each bet sent. We do not record the specific players, teams, lines, or stakes; only the categorical breakdowns used to understand which features are popular.
  • Server operational metrics: API request volume, error rates, cache hit rates, and rate-limit headroom. These help us keep the service available and responsive.
  • Approximate recipient counts: when a bet is shared, we record how many people the bet was shared with (e.g. 0 for a solo conversation, 3 for a four-person group). We do not record who the recipients are.

Aggregate event-level analytics are retained for up to 90 days. Daily aggregate counts (e.g. 'devices active on May 4'), with no per-user data, are retained indefinitely so we can observe long-term trends.

We do not share this analytics data with third-party advertisers or marketers, and we do not use it to build advertising profiles.

Our infrastructure provider (Cloudflare) processes requests on our behalf and may log IP addresses at the network edge for security purposes (DDoS protection, abuse prevention). IP addresses are not stored in our own analytics layer; where we need to throttle abusive traffic, IPs are hashed before storage.

7. App Discovery and Deep Linking

To provide seamless navigation, SquadSlips checks your device locally to determine if supported third party sportsbook applications are installed. This allows us to generate functional deep links and pre-populate your bet slips. This process occurs entirely on your device, and we do not transmit the list of your installed applications to our servers.

8. What We Do Not Collect

We are committed to minimizing data collection. SquadSlips strictly does not collect or utilize the following:

  • Real names or email addresses.
  • GPS or precise location data.
  • Financial information, payment details, or real money transactions.
  • Third party advertising trackers.
  • Third-party behavioral analytics SDKs (such as Mixpanel, Amplitude, Google Analytics, or Facebook SDK).

The mobile phone number you provide to sign in is collected and handled only as described in Section 5.

9. Changes to This Policy

We may update this Privacy Policy from time to time as we add new features or comply with legal requirements. We will notify you of any significant changes by updating the effective date at the top of this document.

10. Contact Us

If you have any questions or concerns about this Privacy Policy or how your data is handled, please contact us at support@squadslips.com.