Sub-processors
Last updated October 10, 2026
SigWise uses the third parties below to run the service. This is the list referred to in our Data Processing Agreement.
Analysis providers
To produce an answer, the content of the events being analyzed is sent to one analysis provider. An account uses one provider at a time: the platform default, unless SigWise has pinned the account to a specific one. Every provider receives the same data. Model names in API responses and the console show which model answered.
| Sub-processor | Purpose | Data it receives | Applies when |
|---|---|---|---|
| Typesafe AIJev decision model | Language-model analysis of events | The object ID and type, its recent events (type, name, content, metadata, time), a rolling summary of older events, and the signal definitions being scored | The account's analysis provider is Jev |
| OpenAIDecisions API | Language-model analysis of events | The object ID and type, its recent events (type, name, content, metadata, time), a rolling summary of older events, and the signal definitions being scored | The account's analysis provider is OpenAI |
| MicrosoftMicrosoft-Decision-1 on Microsoft Foundry | Language-model analysis of events | The object ID and type, its recent events (type, name, content, metadata, time), a rolling summary of older events, and the signal definitions being scored | The account's analysis provider is Microsoft |
Infrastructure and services
| Sub-processor | Purpose | Data it receives | Applies when |
|---|---|---|---|
| RailwayApplication hosting | Hosts the API, the background worker, the database and the cache | All account data and stored events | Always |
| CloudflareEdge network and hosting | Hosts the console, the website and the docs, and serves DNS | Console requests and cookies, including the API calls the console makes on your behalf | Always |
| StripePayments | Card payments for prepaid balance | Your billing email and amounts. Card details are entered on Stripe's page and are not seen by SigWise | You top up by card |
| ResendTransactional email | Sends account and alert email | The recipient address and the email's content, such as verification, password reset and rule alerts | Email is sent from your account |
Optional sign-in
| Sub-processor | Purpose | Data it receives | Applies when |
|---|---|---|---|
| GoogleSign in with Google | Optional sign-in | The profile details Google shares when you choose to continue with it | You sign in with Google |
| GitHubSign in with GitHub | Optional sign-in | The profile details GitHub shares when you choose to continue with it | You sign in with GitHub |
Destinations you configure
Webhook URLs, Slack webhooks and alert email addresses that you add are your own destinations. They receive the data you route to them and are not sub-processors of SigWise.
Changes to this list
We update this page before a new sub-processor starts processing customer data, and the date at the top changes. Customers with a signed DPA can ask to be told of changes by email at legal@sigwise.ai, and may object to a change on reasonable data-protection grounds as described in the Data Processing Agreement.
| Date | Change |
|---|---|
| October 10, 2026 | Added Microsoft (Microsoft-Decision-1 on Microsoft Foundry) as an analysis provider. |
| October 10, 2026 | Added OpenAI (Decisions API) as an analysis provider. |
Related
- Security: how requests, secrets and message content are protected.
- Data retention: how long events are stored and how to delete them.
- Privacy Policy and Data Processing Agreement.