Why we built Redactics.
Redactics started inside organisations that redact sensitive documents by hand. The founding team has run information governance and technology functions in UK public and regulated bodies.
- What we believe
- Redaction should take minutes, not weeks, and a person should always see the result before it leaves. Speed without review is not a saving.
- What we build
- One product: automated AI redaction. Upload the documents, review the redactions, export the result. The judgement about what can be released stays with named people in your organisation.
- How we work
- UK-based, built on Microsoft Azure, with processor obligations designed in from the start. We say what is certified and what is not. We publish subprocessors. The trial uses synthetic documents, so nobody sends us sensitive data to see it work.
AI does the reading.
Language models are part of how Redactics reads context, in the same way that OCR is part of how it reads scans. Neither is the point. The point is a redacted document set that a person can check quickly and trust, with a record of what was done to it.
That is why the review application is built as a workspace rather than a black box: calm, dense where it needs to be, and clear about what was redacted automatically and what a person changed.
We are early, and we say so. The Trust Centre lists certifications by real status. Customer stories are published with permission or not at all.
Redact your first document set.
Try Redactics on a synthetic sample set, or talk to us about your documents.