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-processorPurposeData it receivesApplies when
Typesafe AIJev decision modelLanguage-model analysis of eventsThe object ID and type, its recent events (type, name, content, metadata, time), a rolling summary of older events, and the signal definitions being scoredThe account's analysis provider is Jev
OpenAIDecisions APILanguage-model analysis of eventsThe object ID and type, its recent events (type, name, content, metadata, time), a rolling summary of older events, and the signal definitions being scoredThe account's analysis provider is OpenAI
MicrosoftMicrosoft-Decision-1 on Microsoft FoundryLanguage-model analysis of eventsThe object ID and type, its recent events (type, name, content, metadata, time), a rolling summary of older events, and the signal definitions being scoredThe account's analysis provider is Microsoft

Infrastructure and services

Sub-processorPurposeData it receivesApplies when
RailwayApplication hostingHosts the API, the background worker, the database and the cacheAll account data and stored eventsAlways
CloudflareEdge network and hostingHosts the console, the website and the docs, and serves DNSConsole requests and cookies, including the API calls the console makes on your behalfAlways
StripePaymentsCard payments for prepaid balanceYour billing email and amounts. Card details are entered on Stripe's page and are not seen by SigWiseYou top up by card
ResendTransactional emailSends account and alert emailThe recipient address and the email's content, such as verification, password reset and rule alertsEmail is sent from your account

Optional sign-in

Sub-processorPurposeData it receivesApplies when
GoogleSign in with GoogleOptional sign-inThe profile details Google shares when you choose to continue with itYou sign in with Google
GitHubSign in with GitHubOptional sign-inThe profile details GitHub shares when you choose to continue with itYou 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.

DateChange
October 10, 2026Added Microsoft (Microsoft-Decision-1 on Microsoft Foundry) as an analysis provider.
October 10, 2026Added OpenAI (Decisions API) as an analysis provider.
Sub-processors · SigWise