Built for the people who answer for disclosure.
Redactics started inside organisations that receive subject access requests, not in a product studio. The founding team has run information governance and technology functions in UK public and regulated bodies, and has sat in the meeting where someone asks how a redaction decision was made and nobody can say.
- What we believe
- Every finding has evidence. Every decision has a reason. Every disclosure has an audit trail. A process that cannot show those three things is not defensible, however fast it is.
- What we build
- A platform that does the searching, sorting and linking, records everything it did, and leaves the judgement to named people with the evidence in front of them. Sold as software, or delivered as a managed service with the same record.
- How we work
- UK-based, Azure-native, processor obligations designed in from the start. We say what is certified and what is not. We publish subprocessors. We run pilots on real data before asking anyone to commit.
AI is the mechanism, not the point.
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 structured, review-ready and auditable view of what an organisation holds about a person, and a record of what was done with it.
That is why the platform is described as SAR processing and personal data discovery rather than redaction, and why the review workspace is designed as a control room: calm, dense where it needs to be, and clear about what is automated and what is decided by a person.
We are early, and we say so. The Trust Centre lists certifications by real status. Case studies are published with permission or not at all. Pilots produce a report with your figures rather than ours.
Make SARs manageable.
Try Redactics yourself or talk to us about your current process.