Skip to content

Included in Better

Redact & Remove

Redaction removes sensitive content as a controlled release step, not as a cosmetic overlay.

Problem

Overlay-based redaction can leave sensitive text, objects, or metadata recoverable in the released file.

Use

Search or mark sensitive regions, apply true redaction, and verify the released artifact.

Evidence plan

What this unlocks

  • Permanently remove text and the underlying content (verified)
  • Run from the document workspace once signed in
  • Available for repeatable batch or pipeline workflows
Simple pathForm W-9

Quick OCR and field check

Turn a scanned form into a searchable PDF and verify the obvious fields before routing it.

  1. 1Upload the W-9
  2. 2Run OCR
  3. 3Inspect detected text and form regions
  4. 4Save a searchable copy
Searchable PDFField review notesClean source metadata

Inputs & outputs

Accepted formats
pdf
Produced formats
pdf

Common use cases

  • Prepare legal productions
  • Remove PII before external sharing
  • Verify sensitive terms are gone before delivery

Workflow steps

  1. 1Search or mark sensitive regions
  2. 2Apply true redaction to the selected pages
  3. 3Run verification and keep the result evidence

Outputs

  • Redacted PDF
  • Redaction verification report
  • Review mark history

Review checks

  • Verify output after redaction
  • Search for sensitive terms again
  • Keep markup and final redacted artifacts distinct

API

Endpoint family: /v1/security, /v1/forensics, /v1/jobs
  • Treat redaction as destructive and verify the output before download.
  • Use scoped keys and idempotency for automated release pipelines.
Integration overview

Limits

Availability
Included in Better
Readiness
beta
Automation
Pipeline-ready

Confirm entitlement, input requirements, and deployment fit in the package and API documentation before you automate this capability.

Integration overview

Evidence

Browse proof

Public example workflows

Integration overview

Roles and use cases