왜 AI가 아닌 정규 표현식인가요?
규제 준수를 위해서는 설명하고 재현할 수 있는 결과가 필요합니다. 우리의 결정론적 접근 방식은 바로 그것을 제공합니다—블랙 박스도, 놀라움도 없습니다.
상세 비교
We use the best tool for each job: deterministic regex patterns for structured data, and proven ML models for names and entities. Built on Microsoft Presidio.
| Entity Type | Detection Method | Examples |
|---|---|---|
| 구조화된 데이터 | 정규 표현식 패턴 | 이메일, 사회 보장 번호, 신용 카드, IBAN, 전화번호 |
| 이름 및 조직 | ML 모델 (spaCy, Stanza) | 인명, 회사 이름, 위치 |
| 48개 언어 | XLM-RoBERTa | 다국어 개체 인식 |
| 재현성 | 100% 재현 가능 | 같은 입력 = 매번 같은 출력 |
| 이름 감지 | 높은 정확도의 ML | 신뢰도 점수가 있는 검증된 NLP 모델 |
| 감사 가능성 | +완전한 감사 가능 | 모든 개체에 대한 위치, 유형, 신뢰도 |
패턴 매칭 작동 방식
각 엔티티 유형은 특정 형식과 일치하는 정교하게 제작된 정규 표현식 패턴을 가지고 있습니다.
이메일 주소
[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}표준 이메일 형식과 일치: local-part@domain.tld
신용 카드 번호
\b(?:4[0-9]{12}(?:[0-9]{3})?|5[1-5][0-9]{14}|...)\bVisa, Mastercard, Amex 및 Luhn 검증이 포함된 기타 카드 형식과 일치
독일 IBAN
DE[0-9]{2}\s?[0-9]{4}\s?[0-9]{4}\s?[0-9]{4}\s?[0-9]{4}\s?[0-9]{2}선택적 공백이 포함된 독일 IBAN 형식과 일치
준수를 위해 설계됨
감사자가 "왜 이것이 탐지되었나요?"라고 물을 때 명확한 답변이 필요합니다. 우리의 정규 표현식 기반 접근 방식이 바로 그것을 제공합니다.
- GDPR 제25조: 설명 가능한 처리로 설계된 프라이버시
- ISO 27001: 문서화된, 반복 가능한 프로세스
- 감사 추적: 모든 탐지는 특정 패턴에 추적될 수 있음
예시 감사 응답
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.