Salus sits on the action path. Here is what we see.
Palo Alto · May 13, 2026
Trust, plainly stated.
What crosses Salus, what does not, how data is handled, and where we are on security. We will not claim things we cannot back up today.
I. The wire
What crosses Salus, and what doesn't.
What crosses
The action, and what justifies it.
- Tool name
- Arguments
- Session id
- Policy
- Evidence snippet if provided
- Decision result
What does not, by default
Audio, transcripts, card data, PII you don't need to send.
- Audio
- Full transcripts
- Card data
- Unneeded PII
II. Two modes
Shadow first, live when you're ready.
Shadow mode
Read-only replay.
Salus reviews proposed actions and logs what would have been decided. No production behavior changes. Nothing is blocked, rewritten, or escalated.
Live mode
Selected tools, on the path.
Selected tool calls route through Salus before execution. Allow, clarify, repair, rewrite, or escalate. You decide which workflows to enroll.
III. Data handling
Plain rules, not paragraphs.
Decision events.
Retained for 90 days by default. Exportable any time.
Customer data.
Not used for model training. Ever.
Imported logs.
Deletable on request, or by you in the dashboard.
Field-level redaction.
Hash, drop, or mask any argument field before it reaches Salus.
IV. The security review
Bring your questionnaire.
We will answer in full.
Write to us. We respond within one business day.
Write to us →
❦