Anonymising One-Way (Unilateral) NDAs for Third-Party Sharing – UK GDPR-compliant anonymisation per UK GDPR Art. 4(1)

A one-way non-disclosure agreement discloses confidential information in one direction, but still identifies the disclosing party's authorised signatories and the recipient's contact personnel throughout its recitals and execution block. anonym.legal pseudonymises these individuals so advisers or procurement teams can evaluate the commercial terms without processing unnecessary personal data.

When this applies

This task applies when the receiving party or its advisers need to review or benchmark a unilateral NDA against standard market terms, but the disclosing party's personnel details are not relevant to that review.

  1. Upload the one-way NDA to anonym.legal; the engine preserves clause structure and formatting.
  2. Named natural persons — signatories, authorised representatives, and any contact persons in schedules — are identified across all 285+ entity types.
  3. The disclosing party's personnel receive distinct pseudonyms separate from the receiving party's personnel, maintaining the asymmetric structure of the agreement.
  4. All confidentiality scope language, carve-outs, term, and remedies provisions remain in clear text.
  5. A secure mapping table is produced with UK/EU data residency.
  6. The pseudonymised version is released for review; the original is restored via the mapping key before execution.

What you provide

  • One-way NDA document (signed or draft)
  • Identification of which party is the disclosing party (to guide pseudonym labelling)
  • Any attached schedules naming additional contacts

Limitations & cautions

  • The tool does not assess whether the confidentiality scope is adequate or overly broad — seek legal advice on substantive terms.
  • If the agreement references individuals by role only (e.g. 'the Disclosing Party's CEO'), those references are not automatically pseudonymised unless they appear alongside a name.

FAQ

Can I share the pseudonymised NDA with overseas advisers?

The pseudonymised copy no longer contains personal data within the meaning of UK GDPR Art. 4(1), so transfer restrictions that apply to personal data do not apply to it. However, confirm with your legal counsel that the pseudonymisation meets the relevant standard for your specific context.

What happens if the NDA names a company contact in a schedule?

Contacts named in schedules are detected and pseudonymised consistently with their appearances in the main body, so the pseudonym is the same throughout the entire document.

How does anonym.legal distinguish the two parties' personnel?

The engine uses contextual cues — party labels, signature-block headings, and recital definitions — to assign personnel to the correct party group and applies distinct pseudonym prefixes accordingly.

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.