Cases
—
ingested locally
Drop in case files. The runtime classifies each one, extracts entities, builds a graph, and writes a local SQLite file. Detector-class PII is redacted from summaries and entity names are salted hashes. Nothing leaves the machine until you click "share aggregates" and walk through the anonymization preview.
Counts come from the SQLite file on this machine. Nothing here travels to the public hub.
Demo path: paste a file's text below. Production path (folder upload + folder watch) is documented in BULK_INGEST_PLAN.md; this page handles single-text intake today.
Click a case ID to fetch the full record (entities + edges + summary) from the local API.
The local KB stores a redacted summary excerpt, detector labels, source metadata, relationship edges, and hashed entity names in the operator-side SQLite file. Entity names are hashed with a per-deployment salt; the raw name never lands in the entity table. The salt is in your environment (DUECARE_LOCAL_KB_SALT). Lose the salt and the names are unrecoverable even with the file.
When you want to wipe everything, click below. There is no "soft delete"; the rows are gone.