Perjanjian Pemprosesan Data

Untuk pelanggan perusahaan yang memerlukan Perjanjian Pemprosesan Data (DPA) rasmi sebagai sebahagian daripada keperluan pematuhan GDPR mereka.

Apakah itu DPA?

Perjanjian Pemprosesan Data (DPA) ialah kontrak yang mengikat secara sah di antara pengawal data (anda) dan pemproses data (anonym.legal) yang mentadbir cara maklumat peribadi dikendalikan.

Di bawah Perkara 28 GDPR, organisasi mesti mempunyai DPA apabila melantik pemproses data pihak ketiga untuk mengendalikan maklumat peribadi bagi pihak mereka.

DPA Standard Kami Merangkumi

✓Perkara dan tempoh pemprosesan
✓Sifat dan tujuan pemprosesan
✓Jenis maklumat peribadi yang diproses
✓Kategori individu yang terjejas
✓Kewajipan dan hak pengawal data
✓Langkah keselamatan teknikal dan organisasi
✓Keperluan sub-pemproses
✓Prosedur pemberitahuan pelanggaran data

Minta Perjanjian Pemprosesan Data

Masukkan alamat e-mel anda dan kami akan menghantar pautan untuk mengisi butiran organisasi anda. Perjanjian yang telah ditandatangani anda akan tiba melalui e-mel sejurus selepas itu.

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, held by our hosting provider.
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 company HQ is in Saarbrücken, Germany. Our servers run in Hetzner's Falkenstein datacenter.

Hetzner holds 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

Automated checks run on every release.

Each surface gets its own sweep script and report.

Human reviewers spot-check the output each week.

We test detection against sample documents before each release.

A failing unit or integration run stops the release.

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.

Paid plans can buy top-up credits.

Credits reset at the end of each cycle.

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.