SAR Redaction
Recommendations your reviewer can defend, line by line.
SART walks the SAR bundle one passage at a time and recommends release or redaction against a versioned exemption ruleset. Reasoning attached. Confidence attached. Override at any time.
"…spoke with Mr Patel at 14 Pinehurst on 12 March regarding the repair raised by the tenant…"
Illustrative — recommendations only. The reviewer applies the statutory test.
What's in the box
Six things every recommendation guarantees.
Per-passage decisions
Every paragraph or line is classified individually. No blanket redactions, no "redact the document."
Cited reasoning
Each recommendation carries the rule ID and a plain-English reason. Defensible by construction.
Versioned ruleset
MVP rules: TP-PII, NOT-REL, LPP, MGMT-NEG. New rules added under quarterly logic review with full changelog.
Reviewer-first UX
Recommendations are drafts. The named reviewer accepts, overrides, or escalates — and signs.
Override is a feature
Every override is captured with the reviewer's reason and contributes to rule-quality monitoring.
No auto-release
Bundles do not export without a signed reviewer record. The system cannot bypass the human.
MVP ruleset
Four exemptions, fully specified.
Each rule has a written specification, examples, and known edge cases — versioned and changelogged. New rules don't ship until they pass adversarial review.
| Rule ID | Name | Applies to |
|---|---|---|
| TP-PII | Third-party personal data | Names, contact details and identifiable references for anyone who is not the data subject. |
| NOT-REL | Not relevant | Material outside the scope statement agreed at intake — neither released nor concealed; logged as out-of-scope. |
| LPP | Legal professional privilege | Communications between the housing association and its legal advisors in a legal context. |
| MGMT-NEG | Management negotiations | Internal management deliberations whose disclosure would prejudice candour or ongoing negotiation. |