Privacy policy

Last updated 6 October 2026

This policy explains what Fermi Technologies Inc. collects when you use Kill Switch, why we hold it, who else sees it, and what you can do about it. Kill Switch is a safety product, so much of what it stores exists specifically so that you can prove later what your AI systems did.

The short version

  • Your account details are ours to look after. The message content your systems send us to screen is yours, and we only act on your instructions with it.
  • Hash-only mode stores a SHA-256 digest instead of the text. The audit chain still verifies, and no message content reaches our database.
  • The audit log is insert-only by design. We cannot quietly edit or remove a single event, including at our own request. We can delete whole ranges, or your whole organization.
  • We do not sell or share personal information, and we do not use it to train models.
  • Five named companies process data on our behalf: Supabase, Vercel, Stripe, Resend and Typesafe. They are listed in section 7 with what each one sees.
  • Write to hi@fermi.world to see, correct, export or delete what we hold. We answer within 30 days.

A summary is not the agreement. The numbered sections below are.

1. Who we are, and which hat we are wearing

Fermi Technologies Inc. is a Delaware corporation. In this document, Fermi, we and us mean that company. You and your mean the organization that holds a Kill Switch account, and the people who use it under that account.

We wear two hats, and the difference matters. For your account details, billing information and the way you personally use the dashboard, we are the controller: we decide why that data exists. For the message content your systems send us to be screened, we are a processor acting on your instructions: you decide what gets sent, what the rules are, and how long it is kept. If the people in those conversations have questions about their data, those questions belong to you as the controller, and we will help you answer them.

Our data processing addendum sets this out in contract form and is available on request at hi@fermi.world. Where it conflicts with this policy for data we process on your behalf, the addendum wins.

Reach us at hi@fermi.world for anything in this policy, including a request to exercise the rights described below.

2. What we collect

Account and identity. Email address, name and company given at signup, hashed password or identity-provider subject, organization name, role, and the timestamps of your sessions. We use a third-party authentication service and do not store your password in a form we can read.

Message content. The text of every message your deployments send us to screen, inbound and outbound, plus proposed agent tool calls. If your users type personal data into your chatbot, that personal data reaches us. You control this: hash-only mode stores a SHA-256 digest of each message instead of the text, and the chain still verifies without it.

Screening results. The score per harm category, the overall risk, which of your rules matched, the verdict, the one-sentence reason, the model used, latency and token counts.

Configuration and audit. Deployments, thresholds, rule text and every prior version of it, alert channels, team membership, API key metadata, and a record of who halted or released what, when, and the reason they gave.

Operational data. IP address, user agent and request metadata in server logs, kept for security and abuse investigation.

Audience measurement. Page views and visitor counts, collected by our hosting provider's analytics. It sets no cookies, does not follow anyone across other sites, and the visitor count is derived from a hash rather than an identifier we could trace back to a person.

Billing. Plan, subscription status and usage counts. Card details go directly to our payment processor and are never held by us.

Swarm Tracker. If you submit an incident report, we keep what you type and the email address you give, if you give one. If you subscribe to the mailing list, we keep that address. Neither is required to read the tracker.

We do not use third-party advertising or cross-site tracking on the product. Cookies are limited to what keeps you signed in and what remembers your interface preferences; section 13 lists them.

3. What we do not do with it

We do not sell personal information, and we do not share it for cross-context behavioural advertising, as those terms are defined under California law. We have not done so in the preceding twelve months.

We do not use your message content, your rules or your screening results to train or fine-tune any model, ours or anyone else's. The model that scores a message is given the message in order to answer one question about it, and the provider is contractually barred from retaining it for training.

We do not read your message content except where you ask us to for support, or where we must to investigate abuse or a security incident. Access of that kind is limited to staff who need it and is itself logged.

4. Why we are allowed to hold it

Where the GDPR or similar law applies, we rely on these bases.

  • Performance of a contract, for everything needed to run the account you signed up for.
  • Legitimate interests, for security, abuse prevention, debugging and improving reliability, balanced against the rights of the people involved.
  • Legal obligation, for tax records and lawful requests.
  • Consent, only where we ask for it explicitly, such as the mailing list, which you can withdraw at any time.

For message content processed on your behalf, your customers' legal basis is a matter between you and them. Our agreement with you is the instruction we act on.

5. Automated decisions, and how to contest one

Kill Switch scores messages with a language model and can block a message, end a conversation, or halt a deployment without a human involved. That is the point of the product, and it is an automated decision within the meaning of Article 22 of the GDPR.

Two safeguards exist in the product for this. Every automated verdict records the score, the rule and the reasoning that produced it, so it can be explained afterwards rather than being a black box. And any verdict can be overridden by a person, which appends a new event rather than editing the original.

If one of your users wants to contest a decision that affected them, you hold the transcript and the reasoning and can act on it. We will help you retrieve what you need.

6. Why the log cannot be edited, including by us

Events, halts and chain verifications are insert-only. Update and delete are revoked on those tables for every database role, ours included, and a trigger rejects them on top of that. Each row is hash-chained to the row before it, so altering one breaks every row after it.

This is deliberate and it has a consequence you should understand: we cannot edit or selectively delete an individual event on request, because a log we could quietly edit would be worthless as evidence. What we can do is delete whole ranges by retention or on account closure, which removes the rows without pretending they were never there.

Where an erasure right applies to something inside that log, tell us and we will work out the right approach with you. Usually that means hash-only mode going forward, or shortening retention, rather than surgery on a chain.

7. Who else touches it

These are every company that processes personal data on our behalf. We require each to protect it to a standard no lower than this policy, and to use it only for what we have engaged them to do.

Sub-processors as at the date of this policy.
CompanyWhat it doesWhat it sees
SupabaseDatabase, authentication and file storageAccount details, message content or hashes, screening results, audit log
VercelApplication hosting, audience measurement, and the gateway to the scoring modelRequest metadata and server logs; page views and visitor counts; message text in transit while a message is scored
TypesafeScoring model, where you use the hosted scorerThe message being scored, for the duration of the call
StripePayments and subscriptionsBilling contact, plan and payment status. Card details go to Stripe, never to us
ResendTransactional and alert emailRecipient address and the content of the alert

On Enterprise the scorer runs on your own hardware. In that arrangement no message content leaves your network to be scored, and the model provider is not a sub-processor of yours at all.

We will give you at least 30 days' notice before adding a sub-processor that handles your message content, and you may object. Write to hi@fermi.world to be told when the list changes.

Separately from this list, we disclose data when the law requires it. Where we are permitted to tell you first, we will.

8. Where the data sits, and transfers

Our database and application are hosted in the United States. If you are in the United Kingdom, the European Economic Area or Switzerland, using Kill Switch means your data is transferred there.

For those transfers we rely on the European Commission's Standard Contractual Clauses, together with the UK Addendum where the UK GDPR applies, and we carry out a transfer risk assessment for each sub-processor that receives personal data outside the originating region. Copies are available at hi@fermi.world.

If you need data to stay in a particular region, that is an Enterprise arrangement; tell us before you sign up rather than after.

9. Retention and deletion

You set retention per organization, within the limit your plan allows. A scheduled job deletes events older than your window.

WhatHow long
Events and message contentYour retention window. 30 days on Basic, up to one year on Team, by arrangement on Enterprise
Anchors and chain verification resultsLife of the account. These are hashes, not message content, and they are the evidence the log was not rewritten
Account, organization and configurationLife of the account
Server logs containing IP addresses30 days
Billing recordsSeven years, because tax law requires it
Mailing list addressUntil you unsubscribe
Swarm Tracker reportsKept while the entry stands, so a published claim can be traced back to its source

Close your account and we delete your organization's data within 30 days, except where we are required to keep records for tax or legal reasons. Backups roll off on their own schedule, which can be up to 35 days behind live data.

10. Your rights

Wherever you are, you can ask us to show you what we hold about you, correct it, export it in a portable form, or delete it. You can object to processing we base on legitimate interests, and withdraw consent where consent is what we relied on.

Depending on where you live you may also have the right to opt out of sale or sharing, of which we do neither; the right not to be discriminated against for exercising a right, which we would not do; and the right to appeal a refusal, which you can do by replying to our answer and asking for it to be reviewed.

Write to hi@fermi.world. We will verify that the request is really yours, usually by replying to the address on the account, and answer within 30 days. If we need longer we will tell you why before that deadline passes. An authorised agent may act for you if they can show they are authorised.

If the request concerns message content inside a customer's organization, we are the processor and will refer you to that organization, which holds the data and can act on it. We will tell you who they are.

We honour Global Privacy Control signals where they reach us. There is no behavioural advertising on this site for such a signal to switch off, but we treat it as a valid opt-out request regardless.

If you are in the UK or the EEA and think we have got this wrong, you can complain to your supervisory authority. We would rather you came to us first so we can fix it.

11. Security

Data is encrypted in transit with TLS and at rest by our hosting provider. API keys are stored as hashes, shown once at creation and never again. Access to production is limited to the people who need it, and the audit log is insert-only at the database level rather than by convention.

Row-level security separates one organization's data from another's, and it is enforced by the database rather than by application code remembering to filter.

No system is perfect, and we would rather say so than imply otherwise. If we discover a breach affecting your personal data we will notify you without undue delay, and in any event within 72 hours of becoming aware of it, with what we know, what we are doing and what you should do.

If you find a vulnerability, write to hi@fermi.world. We will not pursue you for research carried out in good faith against your own account.

12. The Swarm Tracker

The Swarm Tracker is a public page and needs no account. Reading it collects nothing beyond the server logs described above.

If you submit a report, we keep what you wrote and, if you give one, your email address, so we can come back to you with a question. A person reads every report. Nothing you submit is published automatically, and we do not publish your address or your name.

Entries on the tracker summarise published reporting about organizations, and they link their sources. If you believe an entry is wrong or unfair about you or your organization, write to hi@fermi.world: we will look at the sources again, and correct, annotate or remove the entry. Where a named party disputes an account, the entry carries that dispute alongside it.

The mailing list is an address and nothing else. Unsubscribe at any time and we stop.

13. Children

Kill Switch is a business product and is not directed at children. We do not knowingly collect personal data from anyone under 16. If you believe a child's data has reached us through your deployment, tell us and we will work out the right way to remove it.

14. Cookies

We use the smallest set we can, and none of it is advertising.

CookiePurposeLife
Authentication sessionKeeps you signed in and refreshes that sessionUntil you sign out, or it expires
Interface preferencesRemembers choices such as whether the sidebar is openUp to a year

Both are strictly necessary or functional, so there is no consent banner to click through. Our audience measurement sets no cookie at all. If either of those changes, you will be asked rather than told.

15. Changes

We will update this policy as the product changes. The date at the top always reflects the current version.

If a change materially reduces your rights or materially widens what we do with personal data, we will tell account holders by email at least 30 days before it takes effect, and the change will not apply retroactively to data already collected.

Fermi Technologies Inc.

A Delaware corporation.

Questions about this document can go to hi@fermi.world.