MSA redaction is the removal of party PII from a master services agreement. The liability caps in it are judged for reasonableness under UCTA 1977 s.3, where one business deals on the other's written standard terms. SGSA 1982 s.13 implies a duty to use reasonable care and skill in a business supply of services. Those terms are why the precedent is worth keeping, so anonym.plus leaves them untouched.
When this applies
An MSA governs a long supplier relationship and names people across every schedule. The framework is the value: scope, service levels, and the caps the s.11(1) reasonableness test judges. So you clear the names on your own machine and keep that framework word for word.
How anonym.plus handles it
- Load the file into anonym.plus on your device.
- The tool scans the body, schedules, and order forms.
- Party names, signatories, and contacts get flagged.
- Confirm the flags and keep the defined service terms.
- Swap them for steady role labels.
- Save the clean precedent on your machine.
What you need to provide
- The agreement plus schedules (PDF, DOCX, or mixed).
- An operator (Replace keeps the framework readable).
- Optional role map for [CUSTOMER] / [SUPPLIER] labels.
PII entity types detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Parties | ORGANIZATION | Globex Ltd → [CUSTOMER] |
| Parties | ORGANIZATION | Initech Ltd → [SUPPLIER] |
| Names | PERSON | signatory → [SIGNATORY] |
| Contact | EMAIL_ADDRESS | ops@globex.co.uk → [EMAIL] |
| Dates | DATE_TIME | effective date → [DATE] |
| Banking | IBAN_CODE | remit acct → [IBAN] |
Compliance achieved
- Keeps the liability caps that UCTA 1977 s.3 and its s.11(1) reasonableness test judge.
- Leaves the reasonable care and skill term implied by SGSA 1982 s.13 intact.
- Supports UK GDPR Recital 26 anonymisation for shareable precedents.
- Scans body, schedules, and order forms together.
- Local-only work — nothing is uploaded.
Anonymise master services agreements offline — see plans & start free →
Limitations & cautions
An MSA spans many linked schedules. Check that each one is included, since a missed order form can still name a party. Defined terms may carry a company name, so review the result before you share.
Frequently asked questions
Are the schedules cleaned too?
Yes. Point the tool at the whole bundle and the body, schedules, and order forms are scanned in one local pass. That matters because the personal data in an MSA usually sits in the schedules rather than the framework.
Can I keep the fee and liability terms?
Yes. Only IDs change, so the scope, fees, and caps stay word for word. Those caps are exactly what UCTA 1977 s.3 and the s.11(1) reasonableness test look at, so a precedent is worth little without them.
Will repeat parties map the same way?
Yes. A role map ties one company to one label across every linked schedule. Without it, the same supplier can end up with two different aliases in one bundle.