By · Last updated 2026-05-09

Back to BlogGDPR & Compliance

DPO Vendor Checklist for GDPR Article 28

GDPR Article 35 requires DPIAs for high-risk processing. ISO 27001 certification reduces security questionnaire time by 73%.

May 9, 20269 minute read
DPO GDPR vendor assessmentGDPR Article 28 checklistDPIA anonymization toolISO 27001 procurementdata processor evaluation

Why DPOs Need to Vet Anonymization Tools

GDPR requires a Data Protection Impact Assessment (DPIA) for high-risk work. Large-scale PII processing is high risk. An anonymization tool is a data processor. It falls under the processor rules. You need to assess it before going live.

Two things are required. Processors need to offer "sufficient guarantees" for security. All processing needs to be governed by a written contract. As a DPO, record the tool's security controls, its sub-processors, where it hosts your files, how it handles breaches, and the data processing agreement (DPA).

ISO 27001 certification cuts the work. BSI found certified firms reduce time on security questionnaires by 73%. Gartner found ISO 27001 is required in 78% of Fortune 500 bids. A certified tool lets you cite the cert. You do not need to check each control by hand. Uncertified tools require more manual review.

See our compliance overview and security page to learn how we meet these rules.

Seven Things to Check

Use this list for any anonymization tool or supplier.

1. Data processing agreement. Is a GDPR-compliant DPA in place? It needs to cover: processing only on your orders, duty of care, security steps, control of sub-processors, help with rights requests, disposal or return of files, and audit rights.

2. Security records. Are the security steps written down? ISO 27001 certified suppliers can point to their cert and their Statement of Applicability. That satisfies the requirement.

3. Sub-processor list. Does the tool use sub-processors? Are they named? You need prior notice of any change. Cloud hosts, CDNs, and OCR tools all count. Missing names are a common gap.

4. Where files are hosted. Is your data hosted in the EU? EU hosting is easiest for EU-based firms. Zero-knowledge tools are also fine — no files leave your device at all. US-based suppliers need Standard Contractual Clauses (SCCs).

5. Breach notice. How fast will the supplier tell you about a breach? The law requires notice to your regulator within 72 hours. Your supplier needs to warn you first. Check the DPA confirms this.

6. Supplier DPIA. Has the supplier done their own DPIA? Can you read it? No DPIA means a gap in your own records. This is a frequent issue.

7. Erasure and portability. Can the supplier handle erasure and portability requests? Zero-knowledge tools store no files, so erasure may not apply. The DPIA needs to say so.

A good supplier gives you four items: ISO 27001 cert, EU hosting proof, their DPIA, and a signed DPA. Those four items fill every gap in your own DPIA. Your regulator will be satisfied.

Read our DPO FAQ for common questions about supplier checks.

Sources

Ready to protect your data?

Start anonymizing PII with 285+ entity types across 48 languages.

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.

Related reading

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.