Beta
​
Sign In
Sign Up

Privacy Policy

Betwatch, Inc. Privacy Policy

Effective Date: November 5, 2026

1. Who we are and what this policy covers

Betwatch, Inc. ("Betwatch," "we," "us") runs the Betwatch.io website (the "Site"), the Betwatch app for iPhone and iPad (the "app"), and the services offered through them (together, the "Services"). This policy explains what we collect, why we collect it, who we share it with, and the choices you have. If you have a question, email [email protected].

This policy covers the Betwatch.io website and the Betwatch app for iPhone and iPad. BlackJack Lab, our blackjack training app, has its own privacy policy at https://betwatch.io/BJL/privacy, and that policy governs BlackJack Lab. A Betwatch account works for all of them, so the account details below are the same in both policies, and deleting your account deletes it everywhere. BlackJack Lab records its usage data with its own system, described in its policy.

2. Information we collect

We collect personal information. Here is what we collect and where it comes from.

Information you give us:

- Account details: your email address, your password (stored only as a secure hash by Google Firebase), your first and last name, your date of birth and, if you add one, your mobile phone number.

- A profile photo, if you upload one.

- Your answer to "How did you hear about us?" and whether you want product emails.

- Comments and chat messages you post. These are public on the Services, with your display name and photo.

- Messages you send us through the contact form or by email, and your email address if you join a waitlist. Contact form messages are stored in our database with your email address and emailed to our support inbox.

- If you import a fantasy league into Start/Sit: the league ID you enter and, for a private ESPN league, the espn_s2 and SWID values you paste. They are sent through our server to ESPN or Sleeper for that import only, and we do not store them. The league settings that come back are saved on your device.

- Purchase records if you buy a subscription: a customer and subscription ID from the payment processor, the plan, the amount, invoice IDs, the brand and last four digits of the card as shown on your receipt, the renewal date, and the country used for tax. We never see your full card number (see Stripe and Apple in section 4).

- If you use the Betwatch.io API: the name you give each API key, a scrambled form of the key and its first few characters (never the full key), your plan, the version of the Terms you accepted when you bought it and when, and a record of each request: the time, which key, the endpoint, the filters you used such as league, sportsbook and market, the response status and how long it took. We do not store the data we send back to you.

- If you start to buy an API plan: that you started a checkout, when, for which plan, and whether it was completed. If you tick the optional email box at checkout, we also record that you did and when, and which version of its wording you saw.

- If you cancel an API plan: the reason you give, if you give one, and whether you took or declined the offer we showed you.

- If you ask for a refund: the payment, the amount, your reason, our decision and any note we add, and what was refunded and when.

Information from Google and Apple sign-in:

If you sign in with Google, Google gives us your name, email address and profile photo. We do not get your contacts or anything else from your Google account. If you sign in with Apple in the app, Apple gives us your name the first time you sign in, and an email address, which may be a private relay address that Apple forwards to you.

Information we collect automatically:

- Your IP address, browser, device type, operating system, language, screen size and the time of each visit.

- The pages you view and how long you stay on each, the links you click (including which outside site a link leads to), the features you use, the page that sent you here, and any campaign codes in the link.

- Two random identifiers stored in your browser: one for the current visit and one that recognizes your browser when it comes back. If you are signed in, we attach your account ID to this activity.

- Your approximate location (country, and region or city where available), worked out from your IP address by Cloudflare. We do not collect your precise location.

- Page speed measurements, including your device's processor count and memory size.

- Security signals from your browser or phone (see section 6).

- Your IP address when you sign up, verify a phone number and use our Services, and, when you verify a phone number, a random device identifier stored in your browser or on your phone. In the app, the IP address from sign-up is also saved on your account. We keep these to keep the Services secure, to prevent fraud and abuse, and to enforce bans (see section 6).

Information from the app:

- Usage data, if you are signed in. The app records the screens you open and how long you stay, what you tap or swipe and how far you scroll, the options you pick (such as sport, league, market and sportsbook), what you type into search boxes, calculator numbers (dollar amounts only as a rough range, such as 100-999), whether results loaded, whether you are online, how you signed in, and errors. Each record carries your account ID, a random ID for the install, a session ID, the app version, your device type, operating system, language and time zone. We never record your password, contact details, name or date of birth. This is on by default. You can turn it off at any time with the "Share usage data" switch in More, then Settings, and recording stops when you do, apart from one last record that you turned it off.

- Push notifications, only if you turn them on in the app: your phone's push token and the kinds of notification you chose. When you turn notifications on, we ask which kinds you want (alerts, updates, and offers and promotions) on a screen that says so in plain words. Offers and promotions is selected there to start with, and you can turn any kind off at any time in Settings in the app or in iOS Settings. The token record is deleted when you turn notifications off in the app, sign out or delete your account.

- The update check. When the app starts, and from time to time while it is open, it downloads https://betwatch.io/app-config.json to see whether an update is required. This request carries no account data.

We do not collect government ID numbers or your precise location. We never ask for your sportsbook logins or passwords.

3. How we use your information

- To create and run your account and keep you signed in.

- To show your comments and chat messages, and to moderate them.

- To understand how the Services are used so we can fix and improve them.

- To measure which links, campaigns and referral sources bring people to the Site.

- To keep the Services secure, prevent fraud, stop scraping and abuse, block automated traffic and enforce bans.

- To process purchases and send the confirmations, renewal reminders and notices about them. These are sent whether or not you opted into marketing.

- To run the API: check your keys, apply your plan's limits and quotas, bill you, spot misuse and show you your own usage.

- To answer your messages and requests.

- To send product emails. If you are in the United States we may send them unless you opt out; everywhere else we send them only if you opted in. Every product email has an unsubscribe link.

- To send push notifications of the kinds you chose (see section 2). You can opt out at any time.

- To email you about an unfinished API checkout or about API updates, only if you ticked the optional box at checkout or already opted in to product emails. Each of these emails has an unsubscribe link. We do not send them to anyone who unsubscribed after opting in.

- To decide cancel offers and refund requests, send you the emails about them (these are not marketing and are sent whether or not you opted in), and keep the records the law and our accounts need.

- To meet legal obligations and enforce our Terms of Service.

Some of our pages can be embedded on other websites. When someone views an embedded Betwatch page, our own analytics record that view the same way as a visit to Betwatch.io. Google Analytics does not run on embedded pages.

4. Third parties we share data with

We share personal information only with service providers, and only for the reasons given. They are cloud hosting and content delivery providers, authentication and database providers, SMS and email delivery providers, AI service providers, payment processors, and Apple for Sign in with Apple and push notifications. They include the companies below. They provide services to us. We do not let them use your data for their own advertising, and we do not use any advertising network.

- Google: Firebase Authentication (sign-in), Cloud Firestore (account records) and Cloud Storage (profile photos). Google Analytics (page views, device and browser details, and your IP address, which Google uses to estimate your location and does not store). In the US it runs unless you opt out. Elsewhere it runs only if you accept analytics cookies (section 8). Google Fonts (your browser loads our fonts from Google, which sees your IP address). Google reCAPTCHA, only on the phone verification step, to stop abuse.

- Cloudflare: every request to the Site passes through Cloudflare for delivery and protection. Cloudflare sees your IP address and request details, runs a bot-detection script on our pages, and may set security cookies.

- DigitalOcean: hosts our servers and stores our images.

- Backblaze: stores encrypted backups of our systems, which can contain account and usage records.

- Prelude: sends the one-time code when you verify a phone number. It receives your phone number.

- Purelymail: delivers the emails you send us through the contact form, including your email address and message.

- OpenRouter, and the AI model provider it routes your question to: receives the questions you type into the Stat Cards question box. See section 5.

- ESPN and flagcdn.com: some team logos and country flags load directly from their image servers, which see your IP address.

- Stripe: processes payments where Betwatch is the seller. Stripe collects your card details directly and is an independent controller of that payment data under its own privacy policy.

- Apple: where you buy through an in-app purchase, Apple is the seller and handles payment, renewal and refunds. In the app, Apple also handles Sign in with Apple and delivers push notifications to your phone.

We may also disclose information if the law requires it, to protect the safety or rights of our users, Betwatch or others, or as part of a merger, acquisition or sale of assets. In a sale of the business, your information would move to the new owner under this policy. Each company above has its own privacy policy that covers what it does with your data.

5. How we use AI

We use artificial intelligence (AI) in these ways:

- Stat Cards question box. When a signed-in user types a question into the Stat Cards box, we send the text of the question to an AI model through OpenRouter. The model only picks which stat card to show. It never sees your name, email or account, and it does not write the numbers you see, because those come from our data. We ask OpenRouter to use only providers that do not keep or train on questions. Please do not type personal information into the box. In the app, we ask your permission before your first question is sent to a third-party AI service provider. We keep your question in our server logs for a few days, and in our own usage records, linked to your account ID, for as long as they are useful for improving the Services. When you delete your account, they are de-identified.

- Organizing odds data. We use AI models to match and label betting markets from different sportsbooks. No personal information is involved.

- Images and writing. Some images on the Site were made with AI tools. We may use AI to help draft content and social media posts.

- Running the Site. We use AI coding assistants, such as Anthropic's Claude, to help write code and investigate problems. While doing that work, they may read server logs and records that contain personal information.

- AI crawlers. We allow AI assistants and search tools to read our public pages, including AI companies that collect pages to train their models, and we show some of them a text version of the Site.

AI output can be wrong. Our Terms of Service explain what that means for you.

6. Security checks and automatic blocking

To protect the Services from scraping and abuse, your browser runs a short security check when the Site loads live data, and the app runs the same check in the background. The check reads technical details about your browser or device, such as graphics card details, installed fonts, screen size and whether the browser is automated. We use the result right away to decide whether to allow access, we do not store these details, and we never use them for advertising. If the check passes, we set a cookie that lasts 10 minutes. Cloudflare runs a similar check on its side. If your browser fails in a way only automated tools do, or sends too many requests, your IP address may be blocked automatically for a period of time. Email [email protected] if you think you were blocked by mistake.

We also keep security records: IP addresses, the random device identifier in section 2, account IDs, how many requests are made and how fast, and records of abuse and bans. We use them to keep the Services secure, prevent fraud and abuse, and enforce bans, including recognizing someone who comes back after being banned. We keep them whether or not you share usage data, because we need them to run and protect the Services. We may keep them after an account is deleted or banned, for as long as we need them to stop abuse and repeat violations. The device identifier stays in your browser or on your phone when you delete your account.

7. We do not sell your personal information

We do not sell your personal information, and we have never sold it. Our referral links to some sportsbook and pick'em sites (see our Terms of Service) do not pass any information about you to them. Because we do not sell personal information, we do not offer a "Do Not Sell" link. If that ever changes, we will update this policy first and give you a way to opt out.

8. Cookies and similar technologies

On the Site, we use cookies and browser storage for three things:

- Needed to run the Site: keeping you signed in, remembering your board and theme settings, the security cookie in section 6, remembering your cookie choice, and remembering for one day whether you are in the US.

- Our own analytics: the random identifiers and the attribution details in section 2, and a cookie that records which version of the home page you saw (kept 90 days). These run on every visit because we use them to keep the Site working and secure. They do not use advertising cookies and are never shared with advertisers.

- Google Analytics: cookies named _ga and _ga_ that last up to 2 years. In the US these are set unless you opt out. Elsewhere they are set only if you accept analytics cookies.

If you are in the US, Google Analytics runs unless you opt out, and we do not show a cookie notice. Anywhere else, we ask whether you accept analytics cookies, with Accept and Reject side by side, and Google Analytics loads only if you accept. We tell whether you are in the US from your IP address and your browser's time zone. If we cannot tell, we ask. You can opt out or change your answer at any time with the "Cookie settings" link in the footer of the Site, or under Security in your account settings. If your browser sends a Global Privacy Control signal, we treat it as an opt-out, wherever you are. You can also block or delete cookies in your browser settings, but some features, such as staying signed in, need them. We do not respond to Do Not Track signals. The cookie choice and Global Privacy Control apply to the Site. The app does not run Google Analytics; its usage data is controlled by the "Share usage data" switch (section 2).

9. How long we keep information

- Account details and settings: until you delete your account. Deleting it removes your profile, photo and settings right away.

- Comments and chat messages: until you or we delete them. When you delete your account, your name and photo are removed and the text stays as "Deleted user", so other people's threads still make sense. When a comment is deleted on its own, its text is erased.

- Our own usage records (Site analytics and app usage data): for as long as they are useful for improving the Services. They are not deleted on a fixed schedule. When you delete your account, they are de-identified rather than deleted: the link to your account is removed.

- Google Analytics: no more than 14 months.

- Server logs: about 30 days.

- Stat Cards questions in server logs: a few days.

- Security blocks: hours to days, depending on the reason.

- Security records (IP addresses, device identifiers, account IDs, request counts and rates, and records of abuse and bans): for as long as we need them to protect the Services and stop abuse and repeat violations, also after an account is deleted or banned (see section 6).

- Push notification tokens: until you turn notifications off in the app, sign out or delete your account.

- Contact form messages and the emails we send about them: up to 2 years.

- Purchase records: 7 years, for tax and accounting. This survives account deletion.

- API records: each request for 90 days; request counts per quarter hour, with no other detail, for up to 7 years with purchase records. Your keys are kept, revoked, while your API account exists. These are not removed automatically when you delete your Betwatch account: ask us (section 16) and we will delete them, apart from what we must keep with purchase records.

- API checkout attempts, email consent records, cancellation reasons, offers and refund requests: kept with purchase records, 7 years. An email consent record is kept as proof, also after you unsubscribe.

- A record of which version of the Terms and this policy you accepted, with the date: kept after you delete your account as proof of consent. It holds no IP address.

Even after you delete your account, we may keep limited information that the law requires or that we need to prevent fraud, resolve disputes and enforce our Terms of Service.

10. Your choices and rights

Wherever you live, you can ask us to:

- give you a copy of your personal information,

- correct it,

- delete it,

- stop using it for analytics (see section 8; in the app, turn off "Share usage data"), or

- stop sending you product emails, including API checkout reminders and API updates (use the unsubscribe link in any of them, your account settings, or email [email protected]). Withdrawing costs nothing and does not affect your plan or the emails about your payments.

To delete your account on the Site, sign in, then go to Account Settings, then Security, then Delete account. You will be asked to confirm it is you and to type DELETE. In the app, go to More, then Settings, then Profile and security, then Delete account, and confirm with your password, or with Apple or Google if you signed in with them. Deleting a website subscription cancels it; an Apple subscription must be cancelled in Apple first. You can also email [email protected] from the address on your account. For any other request, email [email protected]. We will answer within 30 days (45 days where California law allows) and may need to confirm it is really you. We will not treat you differently for using these rights.

If you are in the European Economic Area, the United Kingdom or Switzerland, you also have the right to object to our processing, to restrict it, to data portability, and to complain to your local data protection authority.

If you are a California resident, you have the rights to know, delete and correct your personal information, to opt out of its sale (we do not sell it, see section 7), and not to be discriminated against for using these rights. An authorized agent can make a request for you with your signed permission.

11. Children

The Services are for adults. You must be at least 18 to create an account, and we check your date of birth at sign-up. We do not knowingly collect information from anyone under 18. If you think we have, email [email protected] and we will delete it.

12. Where we process data, and our legal bases

We are based in the United States, and our servers and service providers process data in the United States. If you visit from another country, your information is handled in the United States, where privacy laws may differ. Where our providers move data out of Europe, they rely on their own approved safeguards, such as standard contractual clauses.

For visitors in Europe and the UK, our legal bases are: performing our contract with you (your account and purchases), our legitimate interests (security, fraud prevention, our own analytics and improving the Services), your consent (Google Analytics cookies and product emails), and legal obligations (tax records).

13. Security

We use reasonable technical and organizational measures to protect your information, including encrypted connections, access controls and hashed passwords. No system is perfectly secure. If a breach affects your personal information, we will notify you and the authorities without undue delay, as the law requires.

14. Other websites

Links to sportsbooks, social networks and other sites take you to services we do not control. Their own privacy policies apply there, and we are not responsible for their content or practices.

15. Changes to this policy

We post any change here and update the effective date. For a material change, we also show a notice on the Site and ask signed-in users to agree to the new version before they continue. We record which version you accepted, and when.

16. Contact us

Betwatch, Inc. Email: [email protected]