Current release
What ships, by control code.
Detection. 31 classes and a nine-category semantic layer (SC-01) found by format rules with checksums, seven in-house language models and a verifier that re-checks every candidate (SC-04). Validators for TCKN, VKN, IBAN and card numbers (SC-02); telecom identifiers IMSI, ICCID, IMEI and MSISDN (SC-03); tenant-defined classes activated at runtime (SC-05); PDF, DOCX, XLSX, PPTX, PNG, JPG and scanned pages protected in place; signatures, identity documents and faces blocked on the page image, never sent; unreadable input refused (SC-06).
Protection and restoration. Opaque per-case tokens, one per entity (SC-07); optional format-preserving mode with the key held by the customer (SC-08); restoration inside the perimeter, scoped to the case (SC-09); fail-closed on any protection failure (SC-10); streaming protect and restore for gateway-fronted traffic (SC-11); endpoint deployment with human review before send (SC-12).
Operations and evidence. Tenant-scoped API keys and organisation isolation (SC-13), rate limiting (SC-14), administrator console with local accounts (SC-15), reviewer feedback loop (SC-16), ECS security events with stable codes and no values reprinted (SC-17), PostgreSQL audit store (SC-18), OpenMetrics (SC-19).
Delivery. Private OCI Helm chart, six images, OpenShift 4.x, mirrored-registry install (SC-22); signed release manifest and CycloneDX SBOM (SC-23); no Salus-side data, keys or telemetry (SC-24); CPU-only inference (SC-25).
Extended identifiers. Foreign identity, tax and social-security numbers, driving licence numbers, MAC addresses, credentials, domestic banking formats, healthcare identifiers and crypto-asset addresses, each with its own validator and reference tests (SC-01). Country-aware IBAN extraction against the full registry, one casing rule for every labelled identifier, phone paths reconciled with the numbering plan (SC-02).
Semantic layer. Two purpose-trained models screen a passage for a sensitive category and locate the stated disclosure; the spans are merged with the core result and rendered as one protected text. Additive only: it never removes, re-types or re-bounds what the core found (SC-01, SC-04).