Subprocessor List
1. Introduction
To provide the Foreman AI orchestration platform, we engage third-party service providers ("Subprocessors") to process data on our behalf. We maintain rigorous standards for any partner that handles your workspace data.
2. Authorized Subprocessors
The following entities are authorized to process data as part of the Beta Service operations:
| Subprocessor | Purpose | Data Categories Processed | Region |
|---|---|---|---|
| Descope | Authentication, magic link, and social login | Identity attributes, login metadata, authentication events | United States |
| GitHub (identity provider) | Sign-in via GitHub OAuth when a user chooses that login method | Identity attributes (GitHub username, profile, and email) shared with GitHub during the OAuth exchange | United States |
| Neon | PostgreSQL database hosting | Workspace configurations, user accounts, agent memory, operational logs | United States |
| Stripe | Payment processing | Billing details, subscription state, invoice history | United States |
| OpenAI | LLM inference and orchestration | Prompts, business context, tool execution results (transiently) | United States (provider-managed; processing region not guaranteed) |
| DeepInfra | LLM inference (Open weights) | Prompts, conversation excerpts (transiently) | United States (provider-managed; processing region not guaranteed) |
| OpenRouter | LLM model routing and fallback | Prompts, payloads requested during capability escalations (transiently) | United States (provider-managed; processing region not guaranteed) |
| Nylas | Managed email and calendar connectivity for the Hub (message sync, sending, and calendar access) | Email messages and bodies, calendar events, contact and participant addresses, and OAuth grants for connected mailboxes and calendars | United States |
| Composio | Third-party integrations and tool execution | OAuth tokens, execution payloads between agents and external platforms | United States |
| Pipedream | Third-party integration connection and execution | OAuth metadata, execution payloads, and integration logs where enabled | United States |
| Fly.io | Application hosting and runtime infrastructure | User requests, application responses, and transient runtime data | United States |
| Cloudflare R2 | Private object storage | Uploaded documents, attachments, and export bundles | United States |
| Tavily | Web content extraction and search | Search queries, specified URLs requested by agents | United States |
| Brave Search | Managed web-search backend (Foreman-keyed) for agent research and failover | Agent search queries (transiently) | United States |
| SerpApi | Managed web-search backend (Foreman-keyed) for agent research and failover | Agent search queries (transiently) | United States |
| cron-job.org | Scheduled job triggering for hosted background tasks | Endpoint URLs and a service credential used to invoke scheduled jobs; no customer content | European Union (as applicable) |
| Resend | Transactional email delivery (sign-in, beta invitations, account and system notifications) | Recipient email addresses and the contents of transactional messages | United States |
| ipapi.co | IP geolocation used for sanctions/jurisdiction screening at sign-up and billing | Client IP address (used transiently to resolve approximate country/region) | United States |
| U.S. Department of Commerce — Consolidated Screening List API (trade.gov) | Sanctions and denied-party screening required for legal compliance | Names submitted for screening against U.S. government sanctions lists | United States |
3. Customer-Directed Services and BYOK
If you utilize Bring Your Own Key (BYOK) functionality to connect directly to an LLM provider (such as OpenAI, Anthropic, or Google), data transmitted using your key is governed by your direct relationship and Data Processing Agreement with that specific provider. In such cases, they act as your direct processor, rather than our subprocessor, for inference data.
The same distinction applies when you connect your own mailbox, calendar, social account, CRM, prospecting source, or enrichment account. The account provider and any destination platform you select are Customer-Directed Services, not Foreman subprocessors merely because Foreman sends data to or retrieves data from them at your direction. Infrastructure and connector providers that Foreman engages to implement those connections, such as Nylas, Composio, and Pipedream, remain listed above as Foreman subprocessors.
4. Updates and Change Notification
We keep this list current as our infrastructure evolves. Before we add or replace a subprocessor that will process customer personal data, we will update this page and provide at least 30 days' advance notice to account administrators — by email and/or an in-app notice. During that notice period you may object to a new subprocessor by writing to privacy@foreman.company; if we cannot reasonably accommodate a good-faith objection, you may terminate the affected Service and receive a pro-rata refund of prepaid, unused fees as your exclusive remedy. This mechanism is also described in our Data Processing Addendum.
Customers may configure provider exclusions for model-routing providers that their organization does not permit.