SafeRedact

Release notes

What changed, build by build.

Every build of the enterprise application carries a stamp in its header. These notes describe what each stamped build changed, in customer terms. Notes before 30 July 2026 predate build stamps and are not listed.

v2026.09.11.211 September 2026

Checkpoint integrity

  • A file whose extraction is a small fraction of a previously saved version of the same file is no longer allowed to overwrite the saved version. The file is failed with an explanation (typically a cloud placeholder or partial download) and listed in the processing failure manifest.
  • A file whose detection was degraded by rate limiting is now remembered as such across a page reload. It is re-detected on the next run rather than restored as complete, and the review warning and export check still apply.
v2026.08.17.317 August 2026

Extraction integrity

  • A file that cannot be read completely from disk is failed at extraction and excluded from the disclosure pack, never attested as complete.
  • A large file that yields almost no text is flagged in the processing log with a request to re-add it from a fully synced local copy.
  • A read failure during a resumed batch run now fails that file and continues, instead of stopping the run.
v2026.08.17.217 August 2026

Progress dashboard

  • An organization-level progress view for case leads, enabled per organization.
v2026.08.17.117 August 2026

Batch throughput

  • Large jobs run more detection waves concurrently.
v2026.08.16.216 August 2026

EU processing route

  • Detection can run on AWS infrastructure within the UK and EU (European regions including London), fixed per organization and recorded in an audit trail. Extracted text is not transferred to the United States on this route.
v2026.08.16.116 August 2026

Batch mode per organization

  • Organizations can be set to run jobs of fifty files or more through batch processing regardless of the default threshold.
v2026.08.15.115 August 2026

Batch threshold

  • Jobs of 1,000 files or more now run through batch processing by default (previously 5,000), matching the size of real partitions.
v2026.08.14.114 August 2026

Processing visibility

  • Per-section progress for dense files, an announcement when a very dense file begins, fractional progress credit so the bar keeps moving, and clearer wording when a file is retried automatically.
v2026.08.12.412 August 2026

Export safety

  • Every export path now fails closed: if a redacted artifact cannot be built, the export stops and says so rather than shipping an unredacted or partial file.
v2026.08.12.112 August 2026

In-app help

  • A help drawer inside the application, answering from the published documentation only, with a reset control. Questions from customer organizations are logged without content for documentation improvements.
v2026.08.08.28 August 2026

Memory model for very large cases

  • Detections and text are released from memory once checkpointed and rehydrated on demand, so cases of tens of thousands of files stay within browser memory. Exports, summaries and audit files hydrate what they need.
v2026.08.07.47 August 2026

Batch resilience

  • Oversized batch results are paged rather than forfeited; waves are capped by chunk count; rate-limit retries no longer double-submit work.
v2026.08.06.36 August 2026

Batch processing

  • Large jobs run through a batch detection path with resumable waves.
v2026.08.04.94 August 2026

Storage and propagation

  • The browser is asked for persistent storage and warned of low disk before a large case begins.
  • Cross-file propagation of decisions is resumable and runs in minutes rather than hours at twenty thousand files, with exact matching for structured identifiers.
v2026.08.04.34 August 2026

Agreements

  • The data processing agreement can be executed in-app by an authorized signatory and is recorded against the organization with the document version and hash.
v2026.08.04.24 August 2026

Export assembly

  • The export ZIP is assembled as a stream, bounding memory at download time.
v2026.08.01.31 August 2026

Mailboxes

  • PST mailboxes are expanded in the browser into individual messages with their attachments; embedded Outlook messages are expanded and their headers and bodies become scannable text.
  • All third-party runtime dependencies are served from our own domain.
v2026.07.31.231 July 2026

Disclosure pack

  • Files that fail processing are excluded from the disclosure pack and listed in a manifest.
  • Email extraction is MIME-aware, with attachments routed to the matching extractor and a clean redacted rendering of the message.
v2026.07.30.931 July 2026

OCR

  • Per-page OCR progress in the processing log; recognition input capped to keep high-DPI scans fast.
v2026.07.30.730 July 2026

Build stamp

  • The build version is shown in the application header and logged at start, so any screenshot identifies the exact code in use.

Run your next subject access request through it.

One real case under a signed data processing agreement, with support through the first week.