Campfire Software, Inc. Subprocessors
Campfire provides Ember, an AI accounting assistant for accounting and bookkeeping workflows.
- Subprocessors
- 17
- Categories
- 14
- Last scanned
| Name | Category | Purpose | Location | Data processed |
|---|---|---|---|---|
| Amazon Web Services | Cloud Infrastructure | Primary cloud infrastructure provider. All Campfire production systems — application servers, databases, file storage, caching, and search — run in AWS (us-west-2). All customer data is encrypted in transit and at rest. | – | PII; All Production Data; Logs and Production Traces |
| Anthropic | AI | LLM provider powering Ember, Campfire's AI accounting assistant. Receives the prompts and context needed to answer a request; API data is not used to train Anthropic's models. | – | Prompts and context for Ember Chat |
| Cloudflare | Cloud Infrastructure | DNS, content delivery, and web application firewall. Terminates and proxies HTTPS traffic to the Campfire application; does not store customer data at rest. | – | – |
| Finch | Payroll | Payroll connectivity provider. When a customer connects their payroll system, payroll and employee compensation data flows through Finch's API to generate payroll journal entries in Campfire. | – | Payroll and employee compensation data |
| Fivetran | Data Platform | Managed data pipeline. Replicates production data into Snowflake. | – | Production data |
| GitHub | Developer Tools | Source code hosting and CI/CD. Stores Campfire's application code; no customer data is processed. | – | Application code (no customer data) |
| Google Workspace | Productivity | Business productivity and identity provider. Used for company email, SSO into internal systems, and email delivery for select workflows. | – | Company email and SSO identity data |
| Langchain | AI | LLM observability platform. Stores traces of Ember chat sessions (prompts, responses, and tool calls) for debugging and quality evaluation. | – | Ember chat traces (prompts, responses, and tool calls) |
| Mailgun | Transactional email delivery. Sends outbound email from the Campfire platform (notifications, invoices, reports) and receives inbound email for email-based workflows. | – | Outbound and inbound email content | |
| OpenAI | AI | LLM and embeddings provider used for select Ember features and document understanding. API data is not used to train OpenAI's models. | – | Ember chat content and document understanding data |
| Plaid | Fintech | Bank connectivity provider. When a customer links a bank account, Plaid retrieves account balances and transactions used for bank feeds and reconciliation. Campfire never sees or stores bank credentials. | – | Bank account balances and transactions |
| PostHog | Analytics | Product analytics. Collects in-app usage events (pages viewed, features used) tied to user IDs to improve the product; no accounting data is sent. | – | In-app usage events tied to user IDs |
| Pylon | Customer Support | Customer support platform. Processes support conversations and contact information. | – | Support conversations and contact information |
| Sentry | Error Tracking | Application error monitoring. Captures error reports and stack traces from the Campfire application, which may include request context and user identifiers. | – | Error reports, stack traces, request context, and user identifiers |
| Snowflake | Data Warehouse | Data warehouse. Holds a replicated copy of production data for reporting and high-volume data aggregations. | – | Replicated production data |
| Sprig | Product | In-app survey and user research tool. Collects voluntary survey responses linked to user IDs; no accounting data is sent. | – | Voluntary survey responses linked to user IDs |
| TurboPuffer | Database | Vector database supporting AI search and retrieval. Stores embeddings of documentation and customer content used to give Ember relevant context. | – | Vector embeddings of documentation and customer content |
No subprocessors match your filters.
Your data may flow beyond direct subprocessors. Click to expand and see the chain.
Loading data flow...
No changes recorded yet. Changes will appear here after the next scan detects updates.