Hand your examiner evidence they can check.
RedactWall gives you a signed record of decisions made on the governed paths you deployed, covering a period you name. The verifier runs without contacting RedactWall-operated services and states what the record does not prove.
The questions you actually get asked
“What member data reached an AI provider last quarter?”
Hand over a signed package for that period and the governed paths in scope.
“Could this record have been edited after the fact?”
Your own team checks the entries present and signed-checkpoint coverage on its systems.
“Who released this held incident?”
One accountable record, with the name and the time.
“Can we check the package ourselves?”
Yes, with nothing of ours running anywhere.
What you get
A signed record for the period you name
Covers recorded decisions on governed paths between the dates you give. It does not prove an event was recorded or describe a path you did not deploy.
What a package containsCheckable without us
Whoever you hand it to can check the packaged entries and signatures on their own, with no system, configuration or key of ours involved.
A check that never guesses
The check gives one of four results: intact; broken, and exactly where; unable to complete; or intact, with the newest entries still awaiting their seal.
Verify it yourselfWho decided, and when
Releasing a held incident takes a named person who confirms their identity, and the record keeps exactly one entry for that decision.
Where this product stands
Your diligence team can read where this product stands today, surface by surface, in one place. Disclosures.
Proof you do not have to trust us for.
Work with RedactWall to confirm fit, agree the scope and verify one managed device before expanding.
- Bundle covers the governed paths deployed
- Integrity checked on your systems
- The report states what it does not prove
Related: Protect customer records · Built for credit unions · Coverage