Sub-processors
The current list is also published at sigwise.ai/subprocessors.
SigWise uses the services below to run the product. The last column says when each one applies to your account.
| Service | Purpose | What it receives | Applies when |
|---|---|---|---|
| Typesafe AI (Jev) | Language-model analysis of events | The object ID and type, recent events (type, name, content, metadata, time), a rolling summary of older events, and the signal definitions | The account's analysis provider is Jev |
| OpenAI (Decisions API) | Language-model analysis of events | The same as above | The account's analysis provider is OpenAI |
| Microsoft (Microsoft-Decision-1 on Microsoft Foundry) | Language-model analysis of events | The same as above | The account's analysis provider is Microsoft |
| Railway | Hosts the API, the background worker, the database and the cache | All account data and stored events | Always |
| Cloudflare | Hosts the console and these docs, and serves DNS | Console requests and cookies, including the API calls the console makes on your behalf | Always |
| Stripe | 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 |
| Resend | Sends transactional email | The recipient address and the email's content, such as verification, password reset and rule alerts | Email is sent from your account |
| Google, GitHub | Optional sign-in | The profile details the provider shares when you choose to continue with it | You sign in with that provider |
Choosing the analysis provider
The provider for an account is set by SigWise, not by API calls. An account uses the platform default unless it has been pinned to a specific provider. Every provider receives the same data, listed above, and API responses show which model answered. If you need a specific provider for your account, ask.
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 they are not sub-processors of SigWise.
Related
- Security for how requests, secrets and message content are protected.
- Data retention for how long events are stored and how to delete them.