Answering wrong is embarrassing. Acting wrong costs money and trust. So Inflection is built the other way round from a chatbot: every capability starts closed, and the rules that keep it closed are yours to write.
Nothing that changes state runs without an explicit confirmation, with the value shown.
Reads are open. Writes are earned, flow by flow, and only after you verify them.
Card numbers and similar values are refused at the source, not filtered afterwards.
Every action is recorded with the exact control it touched, so it can be replayed.
Inflection proposes; a person decides. When Inflection is about to click or type, it stops and surfaces exactly what it intends to do — the action, the target, and the value — and waits.
Name the actions Inflection may only explain, never perform. Closing accounts, deleting data, anything irreversible.
Mark inputs Inflection must never fill, even when a customer asks it to.
Cap what an action may be worth. Above the line, it goes to a human.
When an escalation reveals a rule, Inflection proposes it — and it stays a proposal until someone accepts it.
The safest way to handle a card number is never to receive one. Inflection refuses to type values that look like payment or identity numbers, regardless of who asked or how the request was phrased.
Payment-card and identity-number patterns are rejected before they reach an action.
Login details used for training are write-only — stored for replay, never returned or displayed.
Training a login captures the shape of the form, not what was typed into it.
Account-specific actions require the customer's own authenticated session. Inflection acts inside the app they are already signed into — it never holds a master key to your customer base, and it cannot reach another customer's account from one customer's conversation.
Anything Inflection cannot attribute to a verified session stays informational.
Because Inflection resolves a specific element rather than clicking a coordinate, every action has a name. That is the difference between a log you can defend and a video you have to interpret.
What ran, on which control, with what value, and who confirmed it.
Step through any conversation exactly as it happened.
What was attempted before a human took over.
Who verified a flow, who accepted a boundary, and when.
Deployments are provisioned to a chosen region; conversation history and customer data stay in it.
Encrypted in transit, and at rest on managed storage.
Each workspace's knowledge, memories, flows, and credentials are scoped to that workspace.
Public keys for the browser, secret keys for the server. Rotatable, scoped, revocable.
If none of the above is enough, run the whole stack yourself.
Inflection is early, and we would rather tell you that than imply a badge we haven't earned. Here is the honest status.
If your procurement process needs something specific, ask — we will tell you plainly whether we have it today.
Report it to security@inflection.network. We will acknowledge quickly, keep you updated while we fix it, and credit you if you want the credit. No legal threats for good-faith research.
Bring your security questionnaire. We will answer it straight, including the parts where the answer is "not yet".