By George Curta · Last updated 2026-04-07
PII 익명화 솔루션
AI 보호, GDPR 준수, 브라우저 데이터 손실 방지 및 기업 GenAI 거버넌스를 위한 특별히 설계된 익명화 워크플로.
ChatGPT 데이터 보호
민감한 데이터가 ChatGPT 및 기타 AI 도우미로 유출되는 것을 방지합니다. PII를 자동으로 감지하고, 전송 전에 익명화하며, 응답을 비익명화합니다.
GDPR 익명화
인증된 익명화를 통해 GDPR 제4조(1) 요구 사항을 충족합니다. 285개 이상의 엔티티 유형, 48개 언어, 감사 준비 보고서.
AI 데이터 유출 방지
GenAI의 유출을 사전에 방지합니다. AI API, 로그 또는 제3자 서버에 도달하기 전에 브라우저 수준에서 PII를 가로챕니다.
브라우저 DLP
브라우저에서 직접 데이터 손실 방지. 프록시나 에이전트 없이 SaaS 앱, AI 도구 및 웹 양식에 붙여넣은 데이터를 보호합니다.
GenAI DLP
AI 스택으로 흐르는 데이터를 관리합니다. 모든 GenAI 워크플로에서 PII를 감지, 수정 및 감사합니다 — LLM API, RAG 파이프라인 등.
hub.solutions.vibeCodingSafety.title
hub.solutions.vibeCodingSafety.description
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.