SureMatters

Founder story

Built by someone who lived the disclosure-preparation pain.

SureMatters was founded by Simon, who built the PDF signature redactor (now SureRedact) and the SAR operator console by sitting alongside school IG officers and DPOs working through real SAR caseloads. The tools came out of the work, not the other way around.

In Simon’s words

Hi, I’m Simon. For the past twenty years I’ve worked alongside the people who keep schools running — IT, administrators, business managers, and leaders — and I’ve seen the often heroic effort they put in, never more so than when they’re working through a real SAR caseload. At the start of this year I took on what seemed a small challenge: to detect and permanently redact the signatures in a large set of PDF documents. I’m tenacious by nature, but after what felt like endless iteration with conventional code I was close to giving up. I’m also a firm believer in mulling things over — so I set it aside for a few days, and that’s when the breakthrough came: train a small, local, single-purpose AI model to do the detection. It was quick, accurate, and it just worked.

Those experiences led me to found SureMatters and build SureRedact: local-first document redaction for DSARs and other regulated disclosure work. It’s made for work where accuracy and consistency aren’t negotiable — where AI earns its place only when it genuinely adds value, and where real people always make the final call.

What was built first

The PDF signature redactor came first — a tool to redact handwritten signatures from complaint-disclosure documents in the public domain. It taught the design language: the operator confirms every redaction, the redaction commits at the pixel level, every entry in the audit log is kept and any tampering is detectable.

A matter-preparation companion came next — a tool to triage thousands of records against a SAR scope without losing the audit trail. The plain-text scope file the operator can read and edit, and the Matter-type-keyed templates, came out of working with real school caseloads.

Why two products

The two halves of disclosure preparation — deciding what’s in scope, then redacting what’s in — are different jobs done by sometimes-different people. A school DPO might triage on Tuesdays; the school office manager might handle the redaction on Thursdays. SureRedact is what ships at launch for the redaction half. SurePrepare, the matter-preparation companion, is in private pilot — apply via the contact form. Both run locally; both respect the operator’s authority; both produce the audit trail.

The brand SureMatters is the umbrella. The products kept their working names because that’s how the real customers we built with referred to them.

Trust is what sets us apart

Every SaaS vendor in 2026 says it takes privacy seriously. Most can’t say “your documents do not transit our infrastructure” because they do. We can say it because we built the product around it — the architecture is the commitment, and the AI Policy documents what it already does.

That posture comes from school DPOs who told us, repeatedly, that their regulator-facing job gets much harder if they upload SAR material to a third-party AI service — even one with a published DPA, even one in the EU. So we don’t: not in any tier, not in any add-on, not as a future feature.

If you’re reading this from a schools sector event

SBMs, SBLs, bursars, and DPOs — /for-schools → covers where SureMatters fits, whether you’re a state-maintained primary or secondary, part of a MAT or local authority, an independent charitable school, or part of an independent schools group. We’re interested in pilot conversations with schools and groups handling DSAR / FOI / SAR / complaints and safeguarding-disclosure caseloads. Get in touch →

Get in touch.

Pilot conversations, questions, or just to say hello — we read every message ourselves.

This page was drafted with AI assistance for structure only. Simon wrote in the first person and signed off the final copy on 4 June 2026.