Last updated: 2026-08-14 · Operated by Takeoff Radar LLC, an Illinois limited liability company ("we", "us"). Mailing address: 225 West Randolph Street, Suite 2600, Chicago, IL 60606. Contact: nick@takeoffradar.com
The short version: we run a data product about companies, not about you. We collect the minimum needed to run your account and send you the email you asked for, and we don't sell or share it.
1. What we collect
- Newsletter: your email address, only after you confirm it (double opt-in). Every email has an unsubscribe link that works immediately.
- Paid accounts: your email address and your plan, stored with our database provider (Supabase). Your saved alert filters (states, sectors, amount bands) are stored so we can send your alerts.
- Payments: handled entirely by Stripe. Your card details go to Stripe, never to us; we see only your subscription status.
- API usage: per-key daily request counts, for rate limiting. API keys are stored hashed.
- Alert channels: if you connect Slack or an outbound webhook, the URL you provide is stored with your saved filters and your matching filing rows are delivered to it. Those endpoints are yours; where the data goes after delivery is under your control.
- Bulk list matching: a CSV you upload for matching is processed in memory to build your results and is not stored.
- BD Beast requests: the request text you type is sent to our AI provider to build your call sheet and kept with your account's usage record. Exactly how, and what not to type into it, is in §5.
2. What we don't do
- No advertising trackers, no third-party ad cookies, and we do not sell or share your account, newsletter, or usage data to anyone (including no "sale" or "sharing" as those terms are defined under California law).
- If analytics are enabled on this site, they are privacy-first and aggregate-only (page views and anonymous feature-usage counts), with no cookies and no way to identify you.
- The people you see named in the product (a filing company's officers, directors, and promoters) come from public federal filings, never from tracking anyone. Details in §3.
3. People named in SEC filings
Form D filings list a company's executive officers, directors, and promoters by name. When we show those names, they come straight from Item 3 of the filing on SEC EDGAR, a public federal record, with the title as filed. We add nothing to them: no addresses (we never publish street addresses, business or personal), no personal contact details, no profiles. A "LinkedIn search" link next to a name is exactly that, a search for the name; it is not a claim about who the person is online.
This is public-record information. The names and titles are drawn from a U.S. government record that anyone can read for free on SEC EDGAR. Information lawfully made available from government records is treated as "publicly available" and is outside the definition of personal information under the California privacy laws. We publish only what the filing itself states, and only the officer set from the latest filing in a company's lineage.
The one phone number, and where it does and doesn't go. Some deliverables include the telephone number from Item 2 of the filing, which is the contact number the company printed on its own federal filing for itself. It is not a personal number we hunted down: we never look one up, buy one, or add one, and we do not purchase contact data from anyone, for any tier. We haven't verified that it still rings, and at a small company the line may reach a founder directly, which is why every appearance is labeled as the phone on the filing and nothing more. The number appears in only two places: the briefings we prepare for Max subscribers, and the call sheets BD Beast writes for signed-in users, including the spreadsheet files those sheets export. It appears on no public page: the feed, the company pages, the digest, the feed and watchlist spreadsheet downloads, the API, and the MCP servers carry no phone numbers and no email addresses at all, and an automated check blocks any publish that would put one on a public page. If the number on a filing rings you personally and you would rather it not appear in our call sheets, email support@takeoffradar.com and we'll suppress it going forward.
This is not a consumer report. Takeoff Radar is not a consumer reporting agency, and nothing here may be used to judge a named person's eligibility for a job, credit, insurance, or housing (see the Terms of Service). The names identify who is behind a newly funded company, nothing more.
See an error in how we extracted a name or title from a filing? Email support@takeoffradar.com and we'll fix it promptly. The filing itself is a federal record we can't change; corrections to the record go through the SEC's amendment process (Form D/A), which our nightly update picks up automatically. Because these names are part of a public federal record, we do not remove accurately extracted names on request. If you're named in a filing and are concerned about how you appear here, contact support@takeoffradar.com and we'll review your report and fix anything we extracted wrong.
4. The hiring data (public job boards)
Some company rows show a count of open roles and a few sample job titles. Here is exactly where that comes from.
The source is the company's own public job board. We read the public jobs feed that the company's own applicant tracking system publishes for it (Greenhouse, Lever, Ashby, Workable, or Recruitee), with a declared user agent, the same page anyone can open from the company's careers link. The company does not supply it to us, and we do not buy hiring data or take it from social networks. We attach a board to a company only after independently confirming the board is that company's, and a board we cannot confirm is not published at all.
The number is open roles, on the date shown. It is the count of open roles the board was showing when we read it, and every count carries that date. We count open roles, not people: repeats of the same role count once and contractor postings are left out, so the board itself can list more than we show, and one role can cover several hires. It is an observation on one day, never a forecast and never a claim about what a company plans to do. No count on a row means we found or confirmed no board, never that a company is not hiring.
Sample job titles are the board's own words. We copy them as posted, then clean and screen them before publishing. A title that looks like it names an individual is dropped rather than published, so the promise in §3 holds: the people we name come from public federal filings and nowhere else. If you believe a job title on this site names you, email support@takeoffradar.com and we will remove it.
5. Where AI is involved
Two places, both disclosed here.
Your BD Beast requests. When you type a request into BD Beast, that text is sent to our AI provider, Anthropic, which turns it into data filters and picks companies from the filings. It is sent under commercial API terms that do not allow AI models to be trained on it. We also keep the request with your account's usage record, to enforce your plan's generation caps, watch for abuse, and account for our own costs. Treat the box like a search box: there is no reason to type personal or sensitive information into it, and what you type is processed and kept as described here.
Filing data and generated text. We use AI to help classify filings by sector and stage, to write short company descriptions, and to write the reason line under each company on a BD Beast call sheet and the summary at the bottom of each sheet. Labels carry their provenance: "inferred" means machine-classified from the filing's own fields, "verified" means checked against the company's own website. The reason lines and sheet summaries are drafted from the filing facts shown on the sheet, but they are generated text: they can be wrong, and they are never filing facts themselves. Every factual cell (names, titles, amounts, dates) comes from the filing record, not from a model.
No AI decisions about people. Nothing here uses AI to evaluate, score, or make any decision about a person, and per §3 and the Terms, nothing here may be used to judge a named person's eligibility for anything.
6. Your privacy rights (California and other US states)
State privacy laws (for example California's CCPA/CPRA, and the comprehensive privacy laws of Colorado, Connecticut, Virginia, Texas, Oregon, and other states) apply only to businesses above certain size and data-volume thresholds. Takeoff Radar LLC is below those thresholds, and Takeoff Radar is not governed by those privacy laws. What follows is how we treat your account data anyway, as a matter of practice rather than legal obligation:
- Know and access the personal information we hold about you and how we use it;
- Delete it;
- Correct it;
- Opt out of any "sale" or "sharing" of it, or of targeted advertising (we do none of these);
- Not be discriminated against for exercising any of these rights (we won't cut off or downgrade your service for asking).
The categories of personal information we collect are listed in §1: identifiers (your email), commercial information (your plan), the call-sheet requests you type into BD Beast (§5), and internet activity (per-key API request counts and anonymous, aggregate analytics). We collect it to run your account and deliver what you signed up for, and we keep it only as long as your account or subscription is active plus a short period for records. We do not collect Social Security numbers, government IDs, precise geolocation, or biometric data. The one piece of typed content we keep is the BD Beast request, described in §5.
How to make a request: email nick@takeoffradar.com from your account address. We'll verify and respond promptly. We do not charge for this. These requests cover your account data only; for the people data in §3 (names drawn from public SEC filings), see §3 and contact support@takeoffradar.com if you are concerned.
"Do Not Sell or Share My Personal Information": we do not sell or share your personal information and never have, so there is nothing to opt out of. If that ever changes, we will add a working opt-out here first.
7. If you are outside the United States
Takeoff Radar is intended for users in the United States and is not directed at people in the European Union, the United Kingdom, or other regions with their own data-protection regimes, and we do not market there. We are not established in those regions, and we are not governed by the GDPR, the UK GDPR, or similar data-protection laws. If you are a resident of one of those regions (including someone named in a filing) and are concerned about how your data appears here, contact support@takeoffradar.com and we'll review your report.
8. What stays in your browser
Your theme choice (light/dark) lives in your browser's local storage. If you sign in, your login session token does too. Neither follows you around the web.
9. Deleting your data
Email nick@takeoffradar.com from your account address and we'll delete your account, saved filters, and subscriber record. Unsubscribing from the newsletter removes you from all future sends immediately.
10. Changes
Material changes to this policy will be posted here with a new date.