Skip to main content
Coming soon · Design partners welcome

Give people their evenings back.

A Data Subject Access Request shouldn't cost someone their weekend, their sleep, or their peace of mind. For DPOs, HR managers, SENCos – anyone holding a 30-day clock.

Who this is for

A DSAR isn't a compliance task. It's a human problem that lands on real people.

Behind every DSAR is someone whose week just got harder, and someone else who's exercising a legal right and waiting for a proper answer. These are the four people we built Redactr Pro for.

01The teacher

A DSAR lands on a Friday afternoon.

The SENCo spends her weekend trawling through three years of emails, redacting names with a marker on printed pages.

That's not what she trained for.

That's not what the kids in her class need from her on Monday morning.

02The HR manager

A former employee files a DSAR mid-tribunal.

The HR manager at a fifty-person firm is now spending his evenings manually reviewing correspondence. He doesn't know if he's missed something. He isn't sleeping well.

The 30-day clock is ticking.

03The data subject

Someone genuinely wants to know what's held about them.

Maybe after a difficult school exclusion. Maybe after leaving a job badly. They have a legal right to a response, and they deserve one that's complete, accurate, and delivered on time.

Not one that's late, incomplete, or accidentally exposes someone else's name

because redaction was done manually at midnight.

04The accidental leak

Manual redaction fails. A name gets missed.

Now there's a reportable breach, an ICO notification obligation, and a very uncomfortable conversation with the person whose data was exposed.

All because someone used find-and-replace in Word at 11pm.

What we believe

Redactr Pro gives those people their evenings back, and gives data subjects the response they're entitled to.

The cost of getting DSARs wrong is real – fines, breach notifications, tribunals. But the cost of doing them by hand is paid in evenings, weekends, and sleep. We think both matter.

Built on Redactr

The workspace is new. The engine is already in production.

The Redactr API removes sensitive data from documents in production today, including patient data at the British Society of Echocardiography. Pro is the DSAR case management workspace that runs on top – the engine handles the redactions, full-depth and permanent, once you approve. Open-source core, zero data retention.

See the Redactr API →
In production today

BSEcho Logbook

The British Society of Echocardiography uses Redactr to remove patient data from clinical reports before they enter their accreditation platform. Permanently.

0
records retained
5,000+
members
6
accreditation pathways
Read the full case study →
Inside a case

A DSAR isn't an inbox thread. It's a case.

Email threads scatter across inboxes. Documents live in shared drives. Versions multiply. By day 20, no one's sure what's been done.

Redactr Pro turns every DSAR into a case – a workspace with the inbox, the documents, the audit trail, and a clock that doesn't stop.

The 30-day clock is always visible. So is everything else.

The product

A workspace for the work that actually happens.

Redactr Pro handles the full DSAR case lifecycle – from the initial request through gathering, reviewing, redacting, and sending the response. Built for teams, designed for people who'd rather be doing their actual job.

Case management, end to end

Each DSAR is a case. Per-case email inbox, document gathering, review workflow, audit trail. The clock is always visible.

Bring your own storage

Connect the systems you already use. Sensitive data stays where you keep it. We don't add another silo.

Agent suggestions, human decisions

Agents help surface candidates for redaction. You review and approve. Nothing leaves Redactr Pro without a human signing off.

A portal for the data subject

The person making the request gets a proper place to track their DSAR and receive the response. No more PDFs over email.

Roles for real teams

DPOs, privacy managers, reviewers, approvers. Permissions that match how DSAR work actually gets divided up.

Audit trail, by default

Every action logged. Every decision recorded. When the ICO asks how a response was produced, you can show them.

Frequently asked

A few questions, answered.

What is a DSAR?

A Data Subject Access Request is the right – under UK GDPR – for someone to ask what personal data an organisation holds about them. It applies to anyone who handles personal data, from a school to a 500-person business.

How long do I have to respond to a DSAR?

Thirty days from the date the request is received. The clock can be extended by up to two months for complex requests, but you have to tell the requester within the original 30 days.

What does “full-depth redaction” mean?

Sensitive data is permanently removed from the document. Not covered with a black box, not annotated, not hidden behind a layer. Once redacted, the original data is gone. The same engine powers the Redactr API in production today.

When can I use Redactr Pro?

Redactr Pro is currently in private beta with a small group of design partners. Join the mailing list and we'll let you know when we open up more widely.

Mailing list

When Redactr Pro launches, you'll hear from us.

We're working with a small group of design partners ahead of launch. Leave your email and we'll keep you in the loop, no more than once a month.