Subprocessors

To operate the FireFight hosted service, we rely on a small set of third-party providers ("subprocessors") that process data on our behalf. Each is bound by appropriate confidentiality and data-protection obligations and processes data only to provide services to us. This page lists our current subprocessors.

Self-hosting note: if you run FireFight yourself, none of these apply except the ones you choose to configure (for example, your own AI model provider). You control your own deployment and its subprocessors.

Current subprocessors

Subprocessor	Purpose	Data processed
Slack Technologies	Core platform the Service runs in	Account identity, incident channels and messages you capture
PlanetScale	Managed database hosting	Application data: accounts, incidents, timelines, postmortems
Northflank	Application hosting and compute	Data in transit while the Service processes requests
Cloudflare	DNS, CDN, and object storage (R2) for uploaded files	Website delivery; incident file attachments
Anthropic	AI model provider for generative features	Incident content submitted to generate postmortems and summaries
Polar	Payment processing and subscription billing	Billing contact and payment metadata (no full card details)

Our AI provider processes submitted content solely to return the requested result and is bound not to train on or retain it. We do not use your data to train AI models.

Changes to this list

We may add or replace subprocessors as the Service evolves. When we make a material change, we will update the "Last updated" date above. If you would like advance notice of subprocessor changes, email us at privacy@firefight.app and we will add you to the notification list.

Questions

For questions about our subprocessors or data handling, see our Privacy Policy or contact privacy@firefight.app.