Skip to content

Draft, under legal review. Not yet a binding agreement. Items in square brackets, such as the company number and registered address, are still to be confirmed.

Sub-processors

Last updated 16 Oct 2026

Sub-processors: purpose, data received, location and status
Sub-processorPurposeData it receivesLocationStatus
GitHub, Inc.Your code host: sends webhooks, serves pull-request content, receives the review we postRepository and pull-request metadata; diffs and files, fetched live; review comments and check runs we post[to confirm]Live
Anthropic, PBCAI model provider that writes and verifies findingsPull-request content needed for the review (diff, related files, title and description), with secrets redacted firstUnited States or global processing (the API offers US or global inference)Live
StripePayments, credit top-ups and invoicesBilling contact, payment details (held by Stripe, never by us), invoices[to confirm]Planned
VercelHosting: the website and dashboard, the API's server functions and the background review workersWeb requests and IP addresses, contact-form messages in transit, and the service data our functions and workers handle; code only in memory during a reviewFunctions and workers in London, UK; pages served from Vercel's global edge networkLive
NeonPostgres databaseAll service data we hold (account, workspace, findings, audit log) and contact-form messages; never your repository or diffsLondon, UK (AWS eu-west-2)Live
ResendSign-in links and invitation emailEmail address and the message we sendIreland, EU (eu-west-1)Live
Amazon BedrockOptional EU route for model inferenceAs Anthropic, for workspaces that choose the EU routeEU regions (planned)Planned

About this list

These are the providers that process personal data on our behalf to run Forseti. “Live” means the product uses the provider today; “Planned” means the integration is built or chosen but not yet connected in production. We will give at least [30] days’ notice before adding or replacing a sub-processor, as our data processing agreement describes.

Services you choose

Integrations you connect yourself, such as Slack, Microsoft Teams, Jira and Linear, and Google if you sign in with it once available, act under your own agreement with them and are not our sub-processors. They receive only what you configure.

Lookups without personal data

Supply-chain checks look up package names and versions in public sources, such as the OSV.dev vulnerability database and package registries. No code and no personal data are sent.

Updates

To be told about changes, workspace owners receive notice by email. Questions go through our contact page.