Skip to content

Enterprise control

Retention + Redaction

Retention and Redaction Controls connect data retention policy with release-time content removal.

Request accessContact supportView capability
ToolboxBrowse the capability directoryWorkflowBrowse pathsAPIRoutes, scopes, and recipesProofInspect evidence

Problem

Sensitive PDFs can contain visible secrets, hidden data, active content, weak permissions, or signatures that need validation.

Use

Apply protection controls or inspect trust state, then retain evidence for the release decision.

Evidence plan

What this unlocks

  • Redact PII from exported evidence bundles and stamp a retention window (retention is currently advisory)
  • Run from the document workspace once signed in
  • Best package access keeps the path explicit

Workflow

Explore the workflow
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

Tool chain

OCRForms Ops StudioSet Metadata Studio
Searchable PDFField review notesClean source metadata
Explore the workflow

Inputs & outputs

Accepted formats
pdf
Produced formats
report

Common use cases

  • Apply retention policy before disclosure
  • Track why content was removed
  • Bundle redaction evidence for audit review

Workflow steps

  1. 1Choose the policy profile
  2. 2Apply or review redaction decisions
  3. 3Export the retention and redaction log

Outputs

  • Protected or sanitized PDF
  • Verification report
  • Security audit entry

Review checks

  • Verify destructive changes
  • Separate secret delivery from artifact generation
  • Retain reports with the final version

API

Endpoint family: /v1/security, /v1/forensics, /v1/jobs
POST/v1/documents/uploadPOST/v1/ocr/{document_id}GET/v1/jobs/{job_id}/downloadGET/v1/forensics/{document_id}/standards-preflightPOST/v1/forensics/{document_id}GET/v1/forensics/{document_id}/evidence-bundle
  • Security operations should use scoped API keys and idempotency where supported.
  • Destructive operations such as true redaction and sanitization should be followed by verification jobs.
Integration overview

Limits

Availability
Enterprise control
Readiness
private preview
Automation
Single-document workflow

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

Integration overview

Evidence

Browse proof
Evidence is published with the related workflow and proof artifact when it is available for this capability.

Public example workflows

Integration overview
Simple

Quick OCR and field check

Form W-9

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

Proof artifacts

Searchable PDF, Field review notes

Complex

Compliance evidence pack

NIST Cybersecurity Framework 2.0

Preflight a standards PDF, inspect hidden structure, validate trust signals, route findings, and export an evidence bundle.

Proof artifacts

Preflight report, Trust verdict

Roles and use cases

Governance and compliance teams

Compliance / Audit

Validate standards, signatures, audit trails, and retention posture.

Connected tools

Standards Preflight, Trust Chain Validation, PDF X-Ray

Preflight report: Standards preflight reportVerification result: Trust-chain verdict

Security teams

Security / IT

Control self-hosted processing, active content, and data paths.

Connected tools

Sanitize, JavaScript Control, Codec Policy

Review report: X-ray reportGenerated artifact: Parser diff scan

Legal and review teams

Legal Ops

Prepare evidence-ready PDFs and review packages.

Connected tools

Compare PDFs, Signature Center, Redact & Remove

Decision history: Compare review decisionsAudit record: Provenance ledger