By George Curta · Last updated 2026-08-12
시작하기
Nextcloud에 Anonym Anonymizer와 Anonym Files를 설치하고, 백엔드 API URL을 설정한 다음, 통합 전용으로 발급된 토큰을 연결하여 바로 오늘부터 PII 가리기 작업을 안전하고 간편하게 시작해 보세요. 간단한 설정으로 몇 분이면 충분합니다.
두 앱 모두 설치
이 앱들은 아직 Nextcloud 앱 스토어에 게시되지 않았으므로 설치는 수동으로 진행합니다 — 일반적인 Nextcloud 앱 업데이트와 동일한 파일 교체 방식입니다.
- 1.GitHub releases 페이지에서 Anonym Anonymizer와 Anonym Files 앱 아카이브를 다운로드하세요.
- 2.각 아카이브를 Nextcloud 인스턴스의 apps/ 디렉터리에 압축 해제하여 해당 앱의 기존 파일을 교체하세요.
- 3.Nextcloud 관리자 권한으로 occ upgrade(또는 occ app:enable anonym_anonymizer / anonym_files)를 실행하여 Nextcloud가 새 앱을 인식하도록 하세요.
- 4.Nextcloud 관리자 앱 목록에서 두 앱을 모두 활성화하세요.
백엔드 API URL 구성
두 앱 모두 각 앱의 개인 설정에서 구성한 URL을 통해 anonym.legal의 API와 통신합니다. 환경에 맞는 올바른 호스트를 사용하세요:
https://anonymize.businessDEV: https://anonymize.business — 이 통합이 개발 전용인 동안 Nextcloud 앱의 기본값입니다.https://anonym.legal프로덕션: https://anonym.legal — 계정에서 통합이 정식 운영되면 이 호스트로 전환하세요.
런타임에서 검증되는 호스트 허용 목록(UrlGuard)이 다른 모든 호스트를 거부하므로, 구성된 URL은 이 두 가지 중 정확히 하나여야 합니다 — 요청이 거부되면 문제 해결 섹션을 확인하세요.
통합 전용 토큰 붙여넣기
anonym.legal 계정 설정에서 통합 전용 API 토큰을 생성한 후, 백엔드 API URL과 함께 앱의 개인 설정에 붙여넣으세요. 두 앱이 모두 설치되어 있으면 동일한 토큰 구성을 자동으로 공유합니다.
통합 전용 토큰은 콘텐츠를 분석하고 익명화할 수 있지만, 계정에서 복호화된 키 자료는 가져올 수 없습니다 — 전체 계정 API 토큰보다 의도적으로 더 제한되어 있어, Nextcloud 서버가 침해당하더라도 가역적 암호화 기록을 복호화하는 데 사용될 수 없습니다.
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, 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
- 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.