Skip to the page
KilbyDocs
Legal View as Markdown
On this page

Data Processing Addendum

Effective November 15, 2026.

This addendum is part of the Terms of Service between Neuramorphic, Inc. ("Neuramorphic", "we", "us") and the customer who accepted them ("you"). It applies on its own, with no signature, whenever we process personal data in your content for you. If you need a signed copy for your records, write to legal@neuramorphic.ai.

Words used here#

  • Customer Personal Data: personal data in your content, that is, in what you run, store or send through Kilby (see "Your content" in the Terms).
  • Data Protection Law: the laws on personal data that apply to that processing, where they apply to you or to us: the GDPR and the UK GDPR, the Swiss Federal Act on Data Protection, the California Consumer Privacy Act as amended by the California Privacy Rights Act ("CCPA") and the other laws of the states of the United States on personal data, and any other law of that kind.
  • Controller, processor, subprocessor, personal data, data subject and processing have the meaning that Data Protection Law gives them.
  • Security Incident: a breach of security of Kilby that leads to the accidental or unlawful destruction, loss, change, disclosure of or access to Customer Personal Data.

Roles#

You are the controller of Customer Personal Data, and we are your processor. If you process it for someone else, you are a processor and we are your subprocessor, and you promise that your instructions to us are authorized by the controller. What we hold about you as a user of Kilby is covered by the Privacy Policy, not by this addendum.

What we do with it#

We process Customer Personal Data only to provide Kilby to you, and only on your documented instructions. Your instructions are these terms and this addendum, and what you do with the dashboard, the API, the command line tool and the MCP server. If we think an instruction breaks Data Protection Law, we tell you, and we may stop carrying it out. If the law requires us to process it in some other way, we tell you first, unless the law forbids us to.

We do not sell Customer Personal Data, we do not use it for our own purposes and we do not use it to train models. When a workspace turns on Kilby AI, the redacted text that feature sends goes to Google, a subprocessor, and only because the workspace chose it.

Our people#

Those who may reach Customer Personal Data on our side are bound to confidentiality, and only get access when it is needed for a support request you made, to investigate abuse or a threat to the security of Kilby, or because the law requires it.

Security#

We protect Customer Personal Data with the measures in Annex B, which are the ones described in Security and isolation. We may change them, but not in a way that makes the protection of Customer Personal Data worse. You are responsible for choosing what you put on Kilby and for configuring your own applications, access and backups in a way that fits it.

Subprocessors#

You authorize us to use the subprocessors in Subprocessors. We have a written agreement with each that asks the same level of protection of Customer Personal Data that this addendum asks of us, and we remain responsible to you for what they do for us. We tell you about a new one at least 30 days ahead, and you may object, as that page says.

Transfers#

Neuramorphic, Inc. is a United States company and Kilby runs in the United States, so Customer Personal Data is processed there (see Privacy Policy). Where Data Protection Law requires a transfer mechanism for it, the following applies, and nothing in the Terms overrides it:

  • From the European Economic Area: the standard contractual clauses of the European Commission (Decision 2021/914) are part of this addendum, Module Two (controller to processor) or Module Three (processor to processor), with you as exporter and us as importer. Clause 7 (docking) is not included. In clause 9, Option 2 (general authorization) applies with the notice period above. In clause 11 the optional language is not included. In clause 17, Option 1, the law is that of Ireland, and in clause 18 the courts are those of Ireland. The competent supervisory authority in clause 13 is the one for your establishment. Annex I is Annex A below with the parties' details in the Terms, Annex II is Annex B, and Annex III is Subprocessors.
  • From the United Kingdom: the International Data Transfer Addendum to those clauses issued by the Information Commissioner applies, with the tables filled in as above.
  • From Switzerland: the same clauses apply, and references to the GDPR include the Swiss Federal Act on Data Protection.
  • From any other country whose law requires a safeguard for a transfer to the United States, the safeguards that law requires apply, and this addendum is one of them.

The CCPA#

To the extent the CCPA applies to Customer Personal Data, we are your service provider, and you disclose it to us only for the business purpose of providing Kilby to you, as these terms say. We will not sell it or share it for cross-context behavioral advertising, will not retain, use or disclose it outside the direct business relationship with you or for any purpose other than that business purpose, and will not combine it with personal information we receive from others or collect on our own, except as the CCPA allows. We tell you if we can no longer meet our obligations under the CCPA, and you may take reasonable steps to stop and fix any unauthorized use. We understand and will comply with these restrictions.

Requests from data subjects and help#

You can reach, correct and delete Customer Personal Data with the product itself. If a data subject asks us for something about their data in your content, we tell them to ask you and we tell you, unless the law forbids it. We help you, as far as we can and as the nature of Kilby allows, to answer such requests, to carry out data protection impact assessments and to consult authorities. If that help takes more than what the product already does, we may ask for a reasonable fee.

Security Incidents#

We tell you without undue delay, and within 72 hours of knowing, about a Security Incident that affects Customer Personal Data. The notice goes to the owners of the workspace by email and says what we know: what happened, what data and which workspaces, what we have done, what we advise you to do, and a contact. We add to it as we learn more. A notice is not an admission of fault.

Deletion and return#

During the account you can take your content out and delete it with the product. After the account ends, we keep Customer Personal Data for 30 days so that you can take it out, and delete it within 60 days of the end of the account, as the Terms say. What is in backups disappears on the schedule in the Privacy Policy. If the law requires us to keep something, we keep only that, protect it and use it for nothing else.

Information and audits#

We give you what you reasonably need to check that we comply with this addendum. We hold no third-party security certification or audit report, and we say so (see Security and isolation); so we answer, in writing, reasonable questionnaires about our measures. We allow an audit by you or a firm you appoint, once a year or after a Security Incident, or when Data Protection Law or an authority requires it, with notice that lets us prepare, during working hours, under a confidentiality agreement, at your cost, without access to the data of other customers and without harming the working of Kilby.

Liability, order and changes#

What each of us owes the other under this addendum is subject to the limits in the Terms, as far as Data Protection Law allows and without limiting what data subjects can claim. If documents disagree about Customer Personal Data, the standard contractual clauses win, then this addendum, then the Terms. We change this addendum as the Terms say changes are made, and a change required by Data Protection Law takes effect when the law requires it.

Annex A: description of the processing#

  • Subject matter and nature: hosting and running the applications, databases, jobs and files of the customer on Kilby, and the operations the customer asks for: storing, copying, backing up, transmitting, deleting.
  • Purpose: to provide Kilby to the customer.
  • Duration: while the account exists, plus the period in "Deletion and return".
  • Data subjects: whoever the customer's content is about. We do not know who they are; the customer decides.
  • Types of personal data: whatever the customer puts in its content. The customer decides, and must follow the Terms on sensitive data.
  • Frequency: continuous, while services and databases run.

Annex B: security measures#

These are the measures in force, and each is explained in Security and isolation:

  • Isolation. Each workspace has its own namespace and a network policy that allows traffic only from the same workspace and from Kilby's public proxy. Every query for the dashboard and the API is scoped to the workspace of the person or the key.
  • Confinement of containers. Containers run in their own user namespace, with no privilege escalation, with the Linux capabilities dropped except a few, with the container runtime's default seccomp profile, with no credentials for the cluster, under the Pod Security baseline standard and with a resource quota.
  • Encryption. Environment variable values, secret files and registry credentials are encrypted with AES-256-GCM before they are stored. Disks are encrypted volumes. Database backups are encrypted copies in Amazon S3. Traffic to Kilby and to the public address of your services is HTTPS.
  • Credentials. Passwords and second factors are held by the sign-in service (Amazon Cognito), never by Kilby, and every sign-in requires a second factor. API keys, deploy hook addresses and session tokens are stored only as hashes. Sensitive actions ask the person to sign in again.
  • Access control and records. Roles limit what each member can do and see, and Activity records who did what in each workspace.
  • Outgoing connections. Webhook endpoints must be public HTTPS addresses, and Kilby does not send to private or internal addresses.
  • Our staff. Access is limited as the section "Our people" above says.
  • Backups. Postgres databases are archived continuously and backed up every day, and can be restored to any second of the last 7 days. Customers must keep their own copies of what they cannot lose.
  • Incidents. We follow the procedure in "Security Incidents" above.

Annex C: our contact#

Neuramorphic, Inc., a Delaware corporation (Delaware file number 10236902), San Francisco, California, USA. Data protection and contract questions: privacy@neuramorphic.ai and legal@neuramorphic.ai.