Anonymising Supplier Contracts for Procurement Review – UK GDPR-compliant anonymisation per UK GDPR Art. 5(1)(c)

Supplier contracts name account managers, delivery contacts, and authorised signatories on both sides, and often include SLA schedules identifying named escalation contacts. anonym.legal pseudonymises these individuals — preserving pricing, SLA metrics, payment terms, and termination rights — so procurement teams and external auditors can benchmark supplier terms without processing unnecessary personal data.

When this applies

This task applies when a supplier contract is reviewed by procurement consultants, internal audit, or management teams assessing spend efficiency, and those reviewers have no legitimate need to know the identities of the named contact personnel on either side.

  1. Upload the supplier contract and any SLA or key-performance-indicator schedule.
  2. The engine identifies named contacts, escalation managers, and authorised signatories across the agreement and schedules.
  3. Each individual is pseudonymised consistently; SLA metrics, pricing, and escalation-process descriptions are preserved.
  4. A mapping table is produced with UK/EU data residency.
  5. Release the pseudonymised version for procurement review; restore originals before execution.

What you provide

  • Supplier contract
  • SLA or KPI schedule (if separate)
  • Escalation-contact annex (if applicable)

Limitations & cautions

  • The adequacy of SLA metrics and remedies is a commercial judgement not provided by this tool.
  • Multi-supplier framework agreements naming individual supplier contacts should be processed as a batch to ensure cross-document consistency.

FAQ

Can I process a framework agreement covering multiple suppliers?

Yes. Upload all call-off contracts and the framework agreement in a single batch. The engine tracks individuals across all documents and applies consistent pseudonyms.

Are named escalation contacts in SLA schedules pseudonymised?

Yes. Named individuals in escalation-contact columns and tables are detected and pseudonymised; role descriptions and response-time SLAs are preserved.

Does the tool handle supplier contracts with embedded personal-data processing clauses?

Yes. Any DPA or data-processing addendum attached to the supplier contract is processed in the same batch. See the SaaS Contract workflow for DPA-specific guidance.

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.