Subprocessors
Effective date: 14 September 2026
SyncingBeam uses the third-party subprocessors below to provide the service. Each one processes personal data only to perform the function listed, under a contract imposing data-protection obligations equivalent to those in our Data Processing Agreement.
| Subprocessor | Function | Location |
|---|---|---|
| Cloudflare, Inc. | Network, CDN, DNS, and secure tunnel between the public edge and our infrastructure | Global edge network (EU/US; US-headquartered) |
| Resend, Inc. | Transactional email (sign-in links, service and report notifications) | United States |
| Oracle Cloud Infrastructure (Oracle Corporation) | Virtual machine hosting for the application, the database, and the sync pipeline | European Union region; Oracle Corporation is US-headquartered |
| OpenAI | Large-language-model API used to generate report narrative text, for workspaces on the platform-managed provider. A workspace that configures its own provider key (BYOK) sends that text to the provider it chose instead, and that provider is not engaged by us. | United States |
| Anthropic | AI report analysis and narrative generation when selected on the platform-managed provider. | United States; provider subprocessors may process data in other locations |
| Google (Gemini API) | AI report analysis and narrative generation when selected on the platform-managed provider. | Global infrastructure, including the United States |
| xAI | AI report analysis and narrative generation when selected on the platform-managed provider. | United States; provider subprocessors may process data in other locations |
Approved but not engaged yet
The following provider is planned but is not processing personal data today. It is listed here for transparency only, and will move into the table above — with its function and location — under the notice procedure below, before it processes any personal data.
- Stripe — Payment processing and billing. Not engaged: no paid plans are live, so no personal data has been sent to a payment processor.
Platforms that are not subprocessors
Sources you connect. Google and HubSpot are not our subprocessors: they are separate providers you authorize directly through your own account grants, and we read from them on your instruction.
Destinations you nominate. The same applies in the other direction. Where SyncingBeam is configured to post report or brief content into a Slack workspace you nominate, that content is transmitted to Slack's servers through the incoming webhook you supplied, and Slack handles it under your own agreement with Slack — not under a contract of ours. We disclose the flow because it leaves our infrastructure; we do not present Slack as a subprocessor we engaged on your behalf. No content is sent to Slack unless a Slack delivery target is configured for your workspace.
Changes to this list
Keeping this list current is a binding obligation under Section 7 of our DPA — an out-of-date list is a breach of that agreement, so every addition or replacement is published here before it takes effect. We give customers advance notice of intended changes via an update to this page, with material changes emailed to affected customers, at least 15 days before the new subprocessor begins processing personal data, and customers may object as described in the DPA.
Last updated: 14 September 2026
Questions about this list: [email protected].