[ PRIVACY ]

What we store, and for how long.

Fireround is a public funding feed run by Firecrawl. You can read it, query the API, and subscribe to its feeds without an account. This page lists everything the site keeps about the people who use it.

Last updated September 29, 2026.

Reading the site

There is no sign-up and no tracking cookie. The site uses Vercel Web Analytics and Speed Insights, which count page views and measure page speed without cookies. Your light or dark theme choice stays in your browser's local storage and is never sent to us.

The one cookie we set ourselves is for Add to Slack: it carries your picks through Slack's screen, expires after 10 minutes, and is cleared when you come back.

Request logs and rate limits

Our host, Vercel, keeps a log of each request (IP address, user agent, path, time, and response status). We use it to debug and to stop abuse, and it is kept for the retention period of our Vercel plan.

To keep the free API, feeds, and MCP server available, we count requests per IP address. The count is stored under a SHA-256 hash of the address, never the address itself, and counts older than a day are deleted as the limiter runs.

Slack

When you add Fireround to a Slack channel, we store:

  • the workspace name and ID, and the channel name and ID;
  • the incoming webhook Slack issues for that channel, encrypted (AES-256-GCM);
  • the Slack IDs of the app's bot user and of the person who approved the install, so that when Slack revokes those credentials we can find and delete the webhook;
  • your preferences: the watchlist, how often to post, whether to include expected rounds, and whether the channel is paused;
  • delivery records: when we last posted, how many posts went out today, and a short error code when a post fails.

Beyond that opaque user ID we store nothing about who clicked the button: no name, no email address. When you unsubscribe, or Slack tells us the channel or the app is gone, we delete the webhook and stop posting. The row with the workspace and channel names and IDs stays, marked as ended, so the per-workspace limits hold and a reinstall keeps its manage link. Ask us and we will delete it.

Who else handles it

  • Vercel hosts the site and keeps the request logs and analytics.
  • PlanetScale hosts the database.
  • Slack receives the posts for the channels you connect.
  • Firecrawl reads the public web pages the feed is built from. None of the data on this page is sent to it.

We do not sell any of it, and we do not use it for advertising.

The data in the feed

The funding records come from public reporting: news articles, company announcements, and public filings. They name companies, investors, and sometimes people as those sources name them, and every record links to its sources. To correct or remove a record, follow the corrections process.

Retention and deletion

  • Rate-limit counts: deleted after about a day.
  • Request logs: kept for our Vercel plan's log retention period.
  • Slack webhook: deleted when the channel unsubscribes or is removed.
  • Slack workspace and channel names and IDs, and preferences: kept until you ask us to delete them.

To have something deleted, tell us the Slack workspace and channel, and we will delete it and confirm.

Contact

Open an issue on GitHub, or email maxwell@sideguide.dev. No account is needed for either.

More ways to reach us are on the support page. When what we store changes, this page changes with it, and the date at the top says when.