SAR redaction software for schools

Why schools need a clearer SAR redaction workflow

A school subject access request can involve much more than a single PDF. Reviewers may need to collect behaviour records, safeguarding notes, SEND files, emails, parent correspondence, staff comments, meeting notes and exported mailbox material. The risk is not only missing personal data. The risk is losing track of the request, the authority checks, the reason for each redaction and the final disclosure quality check.

The ICO says individuals have a right to access and receive a copy of their personal data, that SARs may be made verbally or in writing, and that organisations should usually respond without undue delay and within one month. Schools also need to think carefully about requests made by parents, carers, solicitors or other representatives, especially where the data subject is a child.

RedactNinja was built around that practical workflow. It helps a reviewer start a case, record requester and data subject details, choose detection rules, review likely matches, add manual redactions, check hidden data and export a disclosure pack. It is not legal advice and it does not replace the DPO, but it gives the review work a more controlled structure.

How the RedactNinja school SAR workflow works

1. Start or import a case. Create a new SAR case or import an encrypted case file from earlier work.
2. Record case setup. Capture requester details, data subject details, received date, identity checks and authority checks. Record when you asked for clarification and when it arrived, and the deadline moves on by the paused days.
3. Add evidence. Select a PDF, image, supported native file, mailbox ZIP, MBOX, Purview style ZIP or supported converted mailbox output. Source files are read locally by the browser.
4. Choose detection rules. Enable built in UK PII rules, personal name detection, address detection, custom keywords and do not redact terms.
5. Scan and review. Review suggested matches, keep safe terms, page context and manual redactions, and give each redaction a reason. Select text to redact whole words, or apply a saved box template. For email evidence, keep or redact each suggestion email by email and decide which pictures to include. A second reviewer can mark each page or email as checked.
6. Export and check. Download redacted PDFs, mailbox PDF output where available, receipts, the redaction certificate, the schedule of redactions, audit files and the disclosure pack. Open the output and check it before disclosure.

Browser based redaction with no source file upload

Many SAR tools process documents on a server. That may be suitable for some organisations, but schools handling pupil, staff, safeguarding and SEND material often want to reduce the number of places where source files travel. RedactNinja takes a different approach: the marketing site is static, and the SAR workspace is designed to process selected files in the browser tab.

This does not remove every risk. The reviewer still needs a trusted device, an up to date browser, secure downloads, correct permissions and a local process for storing exported files. It does mean the app does not need a document upload API for source SAR material, which is a useful privacy position for early testing and school review workflows.

Microsoft Purview export review

Schools and trusts using Microsoft 365 may receive SAR evidence from Microsoft Purview eDiscovery. Microsoft documents export options that can include PST files, MSG files, native files, reports and review set exports. Microsoft also documents export reports such as item, location, settings and summary reports.

RedactNinja is not a replacement for Microsoft Purview. It sits after export as a local review aid. The SAR workspace can inventory Purview style ZIPs, process EML, MSG and MBOX evidence, extract supported native evidence text, and read emails, attachments and pictures from PST files without Outlook, including large PSTs processed folder by folder in batches. It warns when a protected or damaged file cannot be read. That makes the review path clearer for teams that are not full time eDiscovery specialists.

What reviewers still need to decide

Automatic detection is useful, but it cannot decide disclosure law or school context. A person still needs to review third party personal data, safeguarding context, confidential references, legal privilege, special category data and material that may be outside the scope of the request. For complex cases, the reviewer should involve the DPO, senior leader or legal adviser in line with the school or trust process.

• Check whether the requester has authority to act for the data subject.
• Record the response deadline and any lawful reason for pausing or extending time. Since 5 February 2026 the Data (Use and Access) Act 2025 sets out in UK GDPR that the clock stops while you wait for clarification you genuinely need, and that searches must be reasonable and proportionate.
• Check names, addresses, phone numbers, dates, pupil numbers and contextual identifiers.
• Review pages at full zoom after export and search the final PDF for key names.
• Check the redaction receipt, metadata cleaning result and safety check notes.
• Keep a note of why information was disclosed, redacted, withheld or escalated. The reason given for each redaction, and the schedule of redactions, can form part of that record.

Frequently asked questions