Pseudonymising Services Schedules Attached to Commercial Contracts – UK GDPR-compliant anonymisation per UK GDPR Art. 5(1)(c)

A services schedule is a contractual exhibit attached to an MSA describing deliverables, timelines, and named key personnel — including project managers and client-side sponsors — often in staffing matrices or RACI charts. UK GDPR Art. 5(1)(c) requires data minimisation; sharing named personnel unnecessarily risks fines up to £17.5 million or 4% of global turnover. anonym.legal pseudonymises those individuals while preserving deliverables, timelines, and metrics.

When this applies

This task applies when a services schedule is reviewed independently of the main contract by programme-management teams, procurement consultants, or client-side technical reviewers who need to assess deliverables and timelines but have no need to know the identities of named service personnel. According to the Data Protection Act 2018, in force since 25 May 2018, sharing personal data with third parties without a lawful basis constitutes a breach even where the data is commercially ancillary.

  1. Upload the services schedule (and any RACI chart or staffing matrix).
  2. The engine identifies named project personnel — project managers, technical leads, client sponsors — in free-text paragraphs, tables, and matrix cells.
  3. Each individual is pseudonymised consistently; role labels (e.g. 'Project Manager') are preserved.
  4. Deliverable descriptions, milestones, acceptance criteria, and KPI thresholds remain in clear text.
  5. A mapping table is produced with UK/EU data residency.
  6. Release for review; restore originals before execution.

What you provide

  • Services schedule document
  • RACI chart or staffing matrix (if separate)
  • Resource plan naming individual consultants or employees

Limitations & cautions

  • The tool pseudonymises names in tables and matrix cells but may require a manual review of complex nested tables to confirm complete coverage.
  • The adequacy of deliverable specifications and KPI thresholds is a commercial judgement not provided by this tool.
  • Services schedules that reference 50 or more named personnel should be processed as a batch with the parent MSA to ensure entity consistency across all 50+ cases.

FAQ

Can I pseudonymise a services schedule that has been amended multiple times?

Yes. Upload the original and all amendments in a batch; individuals are tracked consistently across versions.

Does the tool handle RACI charts in spreadsheet format?

XLSX files are supported. Named individuals in RACI columns are detected and pseudonymised; role and responsibility columns are preserved.

What if a named individual appears in both the services schedule and the MSA body?

Upload both documents in the same batch so the engine assigns a consistent pseudonym across the entire document set.

Are there statutory obligations to retain named personnel records from services schedules?

The Limitation Act 1980 provides 6 years to bring simple contract claims; services schedules that name individuals involved in delivery should be retained — in identified form via the mapping key — for at least that period. According to the Modern Slavery Act 2015 s.54, larger businesses must also report on supply-chain transparency, which may reference named supplier personnel.

Commercial Contracts

About this page

We update this page when our platform or the law changes.

Read our founder note for how we work.

Each change shows up in the timestamp at the top.

We follow these rules

  • GDPR (EU 2016/679).
  • ISO/IEC 27001:2022.
  • NIS2 (EU 2022/2555).
  • HIPAA safe harbor under 45 CFR § 164.514(b)(2).

Our promise

We do not sell your data.

We do not train models on your text.

We store your files in Germany.

You can delete your account at any time.

You own your work.

Where we run

Our company HQ is in Saarbrücken, Germany. Our servers run in Hetzner's Falkenstein datacenter.

Hetzner holds ISO 27001 certification.

All data stays in the EU.

Backups run every day.

Need help?

Email support@anonym.legal.

We reply within one business day.

How we test

We run a full check suite on every release.

Each surface gets its own sweep script and report.

Human reviewers spot-check the output each week.

We track recall and precision on a labelled set.

Bad runs block the deploy.

What we never do

  • We never sell your information to third parties.
  • We never train models on what you upload.
  • We never keep your work after you delete it.
  • We never share keys with any outside firm.
  • We never run ads inside the product.

Plans in plain words

We sell credits, not seats.

One credit covers one short job.

Long jobs use a few credits each.

You can top up at any time.

Unused credits roll over each month.

Read the plans page for current rates.

Who built this

A small team of engineers and lawyers built this.

We ship from Europe and work in the open.

Our founder note spells out why we started.

Where to start

How the parts fit

A browser add-on cleans text inside Chrome.

A Word plug-in handles drafts in Office.

A small desktop tool works on whole folders.

An agent protocol link feeds large models safely.

All four share one core engine and one rule set.

Words from our team

We started this work after a lunch about cookies.

One friend kept getting odd ads on her phone.

We asked why a court file leaked through a draft.

We sketched the first build on a napkin that week.

By month three we had a tiny demo for a friend.

She used it on her first case the next day.

Common questions we hear

Can the tool read scanned PDFs? Yes, with OCR.

Does it work on long files? Yes, in small chunks.

Can I roll my own rule set? Yes, save it as a preset.

Does it run offline? The desktop build runs offline.

Do you keep my files? No, the cloud build wipes after each run.

Will it learn from my work? No, we never train on inputs.

A short tour of the workflow

Upload a file or paste a snippet of prose.

Pick the entities you want gone from the draft.

Choose a method: replace, mask, hash, encrypt, or redact.

Press run and watch the side panel show each hit.

Skim the result and tweak any rule that misfired.

Save the cleaned file or send it to a teammate.