By George Curta · Last updated 2026-07-24
빠른 참조
지원 앱
- LibreOffice Writer (전체 텍스트 + 서식)
- LibreOffice Calc (셀 기반 처리)
- LibreOffice Impress (슬라이드 텍스트 개체)
요구 사항
- LibreOffice 3.0 이상
- Python 3 런타임
- 인터넷 연결 필요
- anonym.legal 계정 (무료 플랜 제공)
플랫폼
- Windows
- macOS
- Linux
언어
- PII 탐지를 위한 48개 언어
- 48개 UI 언어
- 267가지 이상의 개체 유형
- 자동 언어 탐지
보안
- 제로 지식 인증
- XChaCha20-Poly1305 키 래핑
- AES-256-GCM 암호화
- Argon2id 키 파생 (64MB, 3회 반복)
암호화 키
- ZK 래핑된 서버 스토리지
- 저장된 키에서 자동 로드
- 개체별 키 할당
- 로그아웃까지 세션 지속
기기 간 동기화
- 프리셋 자동 동기화
- 사용자 정의 개체 기기 간 동기화
- 암호화 키 (ZK 래핑)
- 5분 동기화 간격
익명화 방법
- 교체 — 유형화된 단위 (<PERSON_1>)
- 마스킹 — 부분 문자 마스킹 (****)
- 편집 — 영구 제거 ([REDACTED])
- 해싱 — SHA-256 단방향 해시
- 암호화 — AES-256-GCM 가역적
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 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
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
- Open the web app and try a sample file.
- Learn how credits get counted.
- See current plans and limits.
- Meet the team behind the product.
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.