시스템 아키텍처
Microsoft Presidio를 기반으로 구축된 우리의 아키텍처는 분석, 익명화 및 처리를 최대 신뢰성을 위해 전용 서비스로 분리합니다.
Full Documentation핵심 구성 요소
분석기 서비스
정규 표현식 패턴과 spaCy NLP를 사용하여 PII를 탐지합니다. 엔티티 위치, 유형 및 신뢰도 점수를 반환합니다.
익명화 서비스
선택한 변환 방법을 적용합니다. 교체, 삭제, 해시, 암호화 및 마스킹을 지원합니다.
웹 애플리케이션
실시간 처리를 위한 Next.js 프론트엔드. 모든 장치에 대한 반응형 디자인.
REST API
프로그램적 접근을 위한 RESTful 엔드포인트. JWT 인증. 속도 제한.
데이터 흐름
문서는 안전하고 감사 가능한 파이프라인을 통해 우리의 서비스로 흐릅니다.
클라이언트가 HTTPS를 통해 문서를 전송합니다
분석기 서비스가 PII 엔티티를 탐지합니다
결과가 위치 및 점수와 함께 반환됩니다
클라이언트가 익명화 방법을 선택합니다
익명화기가 변환을 적용합니다
익명화된 문서가 클라이언트에게 반환됩니다
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
- Common questions
- Glossary
- How tokens work
- Security posture
- Where we comply
- What we detect
- Case studies
- Release notes
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
- 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.