Evidence
What is redacted, and when
The decision is made against the real request. What a reviewer sees is a preview safe to read, alongside the fingerprint that proves which request it was.
- Activity & evidence
- 3 min read
Redaction happens on the way out
If sensitive values were stripped on arrival, the request could not be evaluated properly and the fingerprint would not identify it. So the record is complete internally, and redaction is applied when a record is displayed or exported.
That is what lets an approval preview be safe to read while the approval itself still binds to the exact inputs.
Where you see it
- The redacted input preview in the Approval Center.
- Input previews on activity entries.
- Evidence exports.
In each case the fingerprint travels alongside the redacted view, so you can still line records up without seeing the values.
What redaction cannot do for you
If an agent is allowed to read personal data and write it into a post, that is a permission decision, not a redaction question. Redaction keeps secrets out of the audit view; it does not stop an authorised action from being taken.
The controls for that are upstream: which Abilities the agent may call, and what its connection user can reach.
Activity & evidence
Keep the boundary while you fix the problem.
A good fix restores intended behaviour without creating a second path around WordPress or the governed request lifecycle.