Skip to content
Lorca Labs
Live demo
Compliance

Redaction Receipt Engine

Redaction you can prove — what was removed, and that the released text is the true redacted version.

The problem

Redaction is easy to get wrong. The redactor must prove what was removed and that the released text is the true redacted version — a claim that should not rest on trust alone.

What it does

01

Creates a receipt for redacted text with pre-image and redacted hashes.

02

Verifies redacted text and hashes against the receipt.

03

Retrieves and lists receipts from the registry.

04

Seals a receipt into an image carrier for air-gap transfer.

Who it’s for

  • Legal and compliance teams releasing redacted documents
  • Anyone producing redacted disclosures under scrutiny
  • Teams that must demonstrate redaction integrity

In context

Receipts can be sealed into carriers with the Air-Gap Courier for offline or cross-boundary verification.

Spec & limits

Interface Input limits Output artifact Failure mode Non-claim
Studio ephemeral /demo; pilot durable /v1 on your infrastructure. TBD — verified in pilot acceptance TBD — verified in pilot acceptance TBD — verified in pilot acceptance TBD — verified in pilot acceptance

Related guide

See the verifiable redaction guide for a deeper problem walkthrough and verification notes — evaluation notes for the live demo and for a private pilot. Also: try the live experiment and read the product overview.

Frequently asked questions

/ 05
01 How is "what was redacted" proven without revealing the original?

A receipt is emitted over the redaction operation with a hash of the removed span; verification confirms the span was removed without exposing its content.

02 What cryptographic guarantee does a receipt provide?

The receipt is signed and hash-bound to the redacted document, so a reviewer can confirm what was removed and that it is no longer recoverable.

03 Can redactions be verified independently of your system?

Yes — verification re-hashes the document and checks the receipt chain offline, without contacting the redaction service.

04 Does this integrate with legal-hold tooling?

Yes — redaction receipts chain into the same audit ledger as legal-hold flags, so holds and redactions share a single verifiable trail.

05 Is "verifiable redaction" the same as a redaction certificate / PDF marking?

No — it is a receipted, verifiable process rather than a PDF tag or visual marking; the proof is cryptographic, not presentational.

Try it live in the studio

A no-signup, in-browser experiment against an isolated demo host. Load sample data, run the flow, and see the result — nothing is stored.