Anonymising Statements of Work for External Review – UK GDPR-compliant anonymisation per UK GDPR Art. 5(1)(c)

A statement of work (SOW) issued under an MSA specifies the project scope, named delivery team members, and client-side points of contact for a discrete engagement. anonym.legal pseudonymises those named individuals while preserving the full commercial substance of the SOW — deliverables, pricing, acceptance criteria, and project schedule — so the document can be shared for audit, benchmarking, or management reporting without personal-data disclosure.

When this applies

This task applies when an SOW is reviewed by internal audit, external consultants benchmarking project costs, or management teams assessing programme delivery, and those reviewers have no legitimate need to know the identities of the named delivery personnel or client contacts.

  1. Upload the SOW (and any change requests that amend it).
  2. The engine identifies all named individuals: project managers, delivery leads, client-side sponsors, and named approvers.
  3. Each individual is pseudonymised consistently across the SOW and any amendments.
  4. Deliverables, pricing, timeline, acceptance tests, and change-control procedures remain in clear text.
  5. A mapping table is produced with UK/EU data residency.
  6. Release the pseudonymised SOW for review; restore originals before execution.

What you provide

  • Statement of Work
  • Change requests or amendments naming individuals
  • Project schedule or Gantt chart if it contains named resources

Limitations & cautions

  • Project schedules in proprietary formats (e.g. .mpp) require export to PDF or XLSX before upload.
  • The tool pseudonymises personal data but does not assess whether the SOW's acceptance criteria are commercially adequate.

FAQ

Is a Statement of Work treated differently from a services schedule?

Functionally they are very similar. An SOW is typically issued per engagement under a master contract, while a services schedule may be a standing exhibit. Both workflows are the same in anonym.legal — upload and process in a batch with the parent agreement.

Can I pseudonymise an SOW before it is countersigned?

Yes. The pseudonymised version is suitable for pre-signature review. Re-identify before countersigning so the executed version bears the correct legal names.

Does the tool handle SOWs with embedded approval-matrix tables?

Yes. Named approvers in table cells are detected and pseudonymised; approval-level descriptions and thresholds are preserved.

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 servers live in Falkenstein, Germany.

We use Hetzner. They hold 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.