Privacy Policy
Last updated: November 12, 2026
Breakwatch is a product operated by Yield Sniper, Inc., a Delaware corporation. Throughout this policy, "Breakwatch," "we," "us," and "our" refer to Yield Sniper, Inc.
1. Our Core Commitments
Before the details, here is what matters most:
- We never sell your personal data or code data to anyone, under any circumstance.
- We never share your data with third parties except the minimum necessary to operate the service (see Sub-processors below). No data brokers, no ad networks, no marketing partners.
- We never use your code or data to train AI models. Not ours, not anyone else's. Your code never reaches an AI model at all: the only text we send to our AI provider is the public text of vendor changes (see AI Processing below).
- Your data is siloed. Dependency maps and alerts are scoped strictly to the installation that generated them. They are never mixed, compared, aggregated, or shared across accounts.
2. What We Collect and Why
a) GitHub Account Info
We collect your GitHub username, email, and avatar via OAuth to authenticate you and create your Breakwatch account.
b) Repository Metadata (your dependency map)
We scan your connected repositories, with read-only access, to identify vendor API usage (imports, SDK calls, API base URLs). During a scan, source files are read in memory and then discarded: your code is never stored. We keep only the result, your dependency map: the repository names, which files use which vendor, and the short text that identified the vendor in each file (an import statement such as import stripe, or an API address such as api.stripe.com). No other part of your code is kept.
c) Billing Information
Payment processing is handled entirely by Stripe. We never see or store your card numbers. We receive only the information needed to manage your subscription (plan, status, invoice history).
d) Slack Integration
If you connect Slack, we store your workspace ID and the channel you choose so we can deliver alerts. We do not read your Slack messages or access any other Slack data.
e) Usage and Analytics
We use Google Analytics 4 to collect aggregated usage data (page views, feature usage, conversion funnel metrics) to understand how people use Breakwatch and improve the product. We do not use this data to identify individuals beyond what is needed for aggregate analytics. We do not send advertising signals, Google Signals is disabled, and ad personalization is turned off. For EU visitors, we use Google Consent Mode v2 and do not store analytics cookies until you consent.
When you create an account, we keep where your first visit came from: the first page you opened, the campaign tags in its link (such as utm_source) and the website that linked to it (its domain only). On our own servers we also count sign-ups, installs, trials and payments per campaign. These are counts, with nothing about you, and tell us which channels work.
To tell people from link scanners, our own server also counts one visit per browser session once a page has been on screen for a few seconds and used. The browser sends the page group it landed on and what sent it (campaign tags or the referring site's domain); a marker in your browser's session storage stops it from being counted twice. No cookie is set and nothing about you (no IP address, no identifier) is stored.
f) The weekly API change email
If you ask for the radar's weekly email (no account needed), we keep your email address, the vendors you picked, and where the request came from (the page group and channel, never anything else about you). Nothing is sent until you confirm through the link we email you; if someone enters your address, you may get that confirmation email (at most 3 a day), and ignoring it is enough. Every email has a one-click unsubscribe; after you unsubscribe we keep the address with its unsubscribed status so the weekly email stops for good, and delete it on request. We use the address for this email only and never sell or share it.
3. How We Use Your Data
We use the data described above to:
- Authenticate you and manage your account.
- Build your dependency map and scan for vendor API changes that affect your code.
- Send you alerts via email and/or Slack when relevant changes are detected. You can turn alert emails off from the link in any alert email or in Settings.
- Process billing and manage your subscription.
- Operate, maintain, and improve the Breakwatch service.
That is it. We do not use your data for advertising, profiling, or any purpose unrelated to delivering the service.
4. AI Processing
When a vendor changes its changelog, documentation or API specification, we send the text of that change (from the vendor's public pages) to Anthropic's API to classify it and write a migration hint. Your code and your dependency map are never sent to an AI model: matching a change to your files happens on our own servers, with rules. Under Anthropic's API data usage policy, what we send is not used for model training.
We do not use your code or data to train, fine-tune, or improve any AI model, whether our own or any third party's.
5. Data Retention
Dependency maps and alert history are retained only as long as your account is active and the associated repository is connected. When you disconnect a repository or delete your account, this data is removed within 30 days.
Email addresses for the weekly API change email are kept while the subscription is active. Requests never confirmed are deleted within about five weeks of their last confirmation email.
We may retain anonymized, aggregate statistics (such as total alerts sent across the platform) that cannot be traced back to any individual or account.
6. Sub-processors
We use the following third-party services to operate Breakwatch. Each receives only the minimum data required for its function:
| Provider | Purpose |
|---|---|
| MongoDB Atlas | Database |
| Upstash | Queue and caching (Redis) |
| Anthropic | AI classification (no training use) |
| Resend | Email delivery (alerts, the weekly API change email and its confirmation) |
| Stripe | Billing and payments |
| Vercel | Web hosting |
| Railway | Background processing |
| GitHub | Integration (you explicitly connect) |
| Slack | Integration (you explicitly connect) |
| Google Analytics (Google LLC) | Aggregated usage analytics (page views, feature usage, conversion funnel). Not used to identify individuals or combined with code/repo data. |
7. Your Rights
You can access, export, or delete your data at any time from your account settings or by emailing support@breakwatch.ai.
For EU users (GDPR)
You have the right to access, rectify, port, and erase your personal data. You may also object to or restrict certain processing. To exercise these rights, contact us at the email above.
For California users (CCPA)
You have the right to know what personal information we collect, to request its deletion, and to opt out of its sale. Since we never sell personal data, there is nothing to opt out of, but you may still exercise your right to know and your right to delete at any time.
8. Security
All data is encrypted in transit using TLS. We enforce access controls and follow security best practices for credential management. We do not store secrets in plaintext.
No system is perfectly secure. If you discover a vulnerability, please report it to support@breakwatch.ai.
9. Children
Breakwatch is not directed at children under 16. We do not knowingly collect personal information from children. If you believe a child has provided us with personal data, please contact us and we will promptly delete it.
10. Changes to This Policy
We may update this policy from time to time. When we do, we will update the "Last updated" date at the top of this page and notify you by email if the changes are material. Continued use of Breakwatch after changes take effect constitutes acceptance of the revised policy.
11. Contact
Questions about this policy or your data? Reach us at support@breakwatch.ai.