Anonymising SaaS Contracts and Data-Processing Addenda – UK GDPR-compliant anonymisation per UK GDPR Art. 28

A SaaS contract bundles subscription terms with a data-processing addendum (DPA) that identifies the customer's data-protection lead, system administrators, and authorised sub-processors. anonym.legal pseudonymises these personal identifiers across the master agreement and DPA simultaneously, allowing legal and procurement teams to evaluate data-processing obligations, pricing, and uptime commitments without exposing individual contact details.

When this applies

This task applies when a SaaS agreement and its attached DPA are shared with external advisers — data-protection counsel, procurement consultants, or board members — who need to assess compliance with UK GDPR Art. 28 processor obligations without access to the named individuals' contact data.

  1. Upload the SaaS agreement and DPA (and any order forms) to anonym.legal.
  2. The engine identifies named individuals in subscription headers, DPA controller and processor signatory sections, notification clauses, and sub-processor lists.
  3. Each natural person is pseudonymised consistently across all uploaded documents.
  4. Data-processing obligations, sub-processor categories, SLA metrics, pricing tiers, and termination rights remain in clear text.
  5. A mapping table is produced with UK/EU data residency.
  6. The pseudonymised set is released for review; originals are restored before execution.

What you provide

  • SaaS Master Agreement
  • Data-Processing Addendum (DPA)
  • Order form(s) naming account contacts
  • Sub-processor list if attached

Limitations & cautions

  • The tool does not assess whether the DPA's sub-processor list meets the adequacy requirements of UK GDPR Art. 28(2) — obtain data-protection legal advice.
  • Email addresses embedded in notice clauses are pseudonymised; ensure replacements are tracked for re-identification before execution.

FAQ

Will pseudonymising the DPA affect its compliance with UK GDPR Art. 28?

The pseudonymised DPA is for internal review only. The executed version must contain the real legal names and contact details to be effective as a data-processing agreement. Re-identify using the mapping key before signing.

Are email addresses in notice clauses pseudonymised?

Yes. Email addresses are detected as personal data under UK GDPR and pseudonymised with consistent placeholder addresses (e.g. representative1@partyA.example) so the notice-mechanism structure remains clear.

Can I process a SaaS contract that has been amended multiple times?

Yes. Upload all amendment documents in the same batch. The engine tracks named individuals across the original agreement and all amendments, applying consistent pseudonyms throughout.

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.