1.1.0 ships server-side batch anonymization with sequential queue & states, reverse/whitelist also in batch, electronic signature detection & re-signing, and batch API with plan-aligned consumption.

Version 1.1.0 extends Anonimatum with server-side batch anonymization, strengthens reverse / whitelist in the same ecosystem, integrates electronic signature detection and re-signing in the batch flow, and aligns consumption with the group plan. Date: 2026-03-01.

Batch anonymization

Upload multiple PDFs with a single config (or per-file config in preview mode). The server queues and processes one by one (sequential queue to avoid CPU/storage saturation).

Complete

Queue with global config (patterns, zones, redaction, quality).

Reverse

Whitelist: reverse config serialized in the batch job.

Preview

Per-PDF review with coords/zones tweak; configs array aligned with file order.

Prior notice: documents are uploaded to server and kept until completion and, where applicable, until you download the ZIP (don’t show again option).
Queueing: pending jobs visible in Executions.
Processing: scheduler picks `PENDING` → `PROCESSING` → `DONE`/`FAILED`. Only one document in `PROCESSING` globally at a time.
Download: ZIP with completed; option for single PDFs; after bulk download server may delete files.
Auto-refresh in Executions every 30s if pending/processing.

Reverse anonymization

Available in dedicated screen and in batch.
In batch, config includes reverse flag and inclusion/exclusion patterns / word-sets.
Each successfully completed batch document consumes group anonymization; reverse counts as complete for quota.

Electronic signature

When enqueuing, each PDF may be detected as electronically signed; those hints (`signatureHints`) are stored in the job.
After result, if applicable, the anonymized PDF can be re-signed (AutoFirma / integration) and linked to public verification.

Plans, consumption and deployment

Each batch job in `DONE` increments group usage; classification pattern/zone/complete/reverse aligned with backend.
Limit & permission validation with JWT; usage logged after success.
Storage: configurable dir `batch.anonymization.storage-dir`.
Batch routes with JWT; each user sees only their jobs.

Batch API (technical reference)

`POST .../batch-jobs` — multipart: `files`, `config`, optional `configs`, `signatureHints`.
`GET .../batch-jobs` — user job listing.
`GET .../batch-jobs/{id}/output` — result PDF if `DONE`.
`DELETE .../batch-jobs/{id}` — delete job (not allowed in `PROCESSING`).
`GET .../batch-jobs/download-completed` — ZIP of completed & server cleanup.

Need to process hundreds of PDFs at once?

See batch processing

Anonimatum 1.1.0 — Server batch, reverse in batch, signature & batch API