Subprocessors
Effective November 15, 2026.
A subprocessor is a company that Neuramorphic, Inc. uses to process personal data on behalf of its customers. This page lists them, and it is the list the Data Processing Addendum refers to. The column "Status" says whether Kilby uses the company today: a company that is not active receives nothing.
Who processes data for Kilby#
| Company | What it does for Kilby | Data it can see | Where | Status |
|---|---|---|---|---|
| Amazon Web Services, Inc. | Runs Kilby and your services: servers, networking, storage, disks, backups, encryption keys, the secrets Kilby itself needs, and sending email through Amazon SES, and the build service that builds from Git | Everything you run on Kilby, and the account data in Kilby's own database | United States: US East (Ohio). Email: US East (N. Virginia) | Active |
| Google LLC | Writes the text of Kilby AI | Only the redacted text that Kilby AI sends for a failed deploy or build, and only for a workspace that turned Kilby AI on | Where Google processes it, under Google's own terms for that service | Active, only for workspaces that turned Kilby AI on |
| Stripe, Inc. | Takes payments and sends invoices | The billing email, company name, address and tax number a workspace gives us, its invoices, and the payment method, which goes to Stripe directly and never reaches Kilby | As Stripe states it | Not active: billing is off, and the beta is free |
| GitHub, Inc. | Gives Kilby access to the repositories of a workspace that connects its GitHub account | The repositories you let Kilby read, to build them | As GitHub states it | Active, only for workspaces that connect GitHub |
This is the complete list. The hosting and the email delivery are always on. The other companies receive nothing until the feature in the last column is on and, where it says so, until a workspace turns it on.
Services you choose#
These are not our subprocessors: you decide to use them, Kilby sends them only what you set up, and your own agreement with them applies.
- Notification and log destinations: the Slack channels, webhook addresses and logging services (such as Datadog or Loki) that you add in a workspace.
- Container registries that hold your images, and the credentials you give Kilby to read from them.
- Git hosts of public repositories that you name (github.com, gitlab.com and bitbucket.org): Kilby downloads an archive of a repository you point to, and the host sees the request.
- Certificate authority for custom domains: Kilby asks Let's Encrypt for a certificate for each domain you add, and the domain name is public in certificate records.
Changes to this list#
We tell the owners of workspaces by email at least 30 days before a new subprocessor starts to process personal data in their content, and we update this page on the same day. If you object for a reason related to data protection, write to legal@neuramorphic.ai before that date. We will try to find a way that avoids the change for you. If there is none, you can end the account, as the Terms of Service say, and the new subprocessor will not process your content.
A subprocessor may be replaced at once only if that is needed to keep Kilby secure or running. We tell you as soon as we can.
Related#
- Data Processing Addendum: what subprocessors must respect.
- Privacy Policy: what we hold about you and where it is processed.
- Kilby AI: exactly what is sent to Google, and what never is.
- Security and isolation: how data is protected.