Today we are launching Redactic — a standalone product for redacting personally identifiable information from documents before they reach an AI model or leave your firm. Redactic is now live at redactic.eu as its own product with a separate brand, domain, and pricing.
We are sharing the why, the what, and the how below — and announcing the long-form blog series we are publishing alongside the launch.
Why we built Redactic
Over the last two years, we have seen the same scene play out inside law firms, accounting practices, payroll bureaus, HR teams, and notarial offices across Italy and the rest of Europe. Someone bans ChatGPT for client data. Three months later, the firm discovers that staff are still using it — from personal accounts, on their phones, at 11pm — because the official path is too slow or does not exist. Cyberhaven's 2023 analysis of ChatGPT use at its customer companies found that sensitive data made up 11% of what employees pasted into the tool. The sources, samples and dates behind this figure and the other widely quoted shadow AI statistics are set out in our audit of shadow AI statistics.
The fix is not stricter rules. Rules get routed around. The fix is making the official path faster than the shadow one, with a redaction layer between the team and the model. That is what Redactic is.
What Redactic does
Redactic redacts PII from documents — PDFs, Word, Excel, scanned images via OCR — before they are shared, archived, or fed to an LLM. Two modes are available from the same upload:
- Reversible (GDPR Art. 4(5) pseudonymisation): sensitive values are replaced with placeholders and the original-to-placeholder map is kept locally. Useful for AI workflows where you need to read the answer with the real names restored.
- Irreversible (Recital 26 anonymisation-style blackout): the sensitive region is permanently destroyed. Useful for sharing files with third parties and for court filings.
The detection cascade uses dictionary lookup on rosters you upload, national regex covering 17 country formats (Codice Fiscale, NIR, Steuer-ID, DNI/NIE, IBAN, EORI and more), a multilingual GLiNER model that catches person and organisation names the regex misses, and Tesseract OCR with the eng+ita+fra+deu+spa pack for scanned documents. The review console lets you accept or reject each detected span before the redaction is applied.
The architecture
Three things make Redactic different from a generic redaction tool.
No-trace by design. Documents are processed in memory and immediately discarded. Inputs are encrypted at rest in Redis with Fernet and a 120-second TTL; outputs use a 300-second TTL. The application has no database model for document content. We literally cannot read what you process.
EU-hosted everything. Compute lives on Hetzner Helsinki; metadata storage on Cloudflare R2 EU jurisdiction. The Secure Chat routes through OpenAI, Anthropic, Google, and Mistral on their EU endpoints under signed DPAs, with zero retention and no training on input. The full sub-processor list is public on the trust pages.
SHA-256 audit certificate per job. Every redaction produces a downloadable certificate with input hash, output hash, redaction counts per category, mode, and timestamp — but no content and no PII. The certificate is the artefact you produce to the supervisory authority, the insurance underwriter, or the client when they ask how a given output was generated.
Plans
Redactic has three plans, billed monthly:
- Solo — €19/month. One professional. 40 AI credits/month. Up to 4,000 pages/month of masking, 50 pages per document.
- Firm — €49/month. Up to 50 seats. 100 AI credits/month. 10,000 pages/month of masking, 100 pages per document. Includes the Secure AI Chat.
- Enterprise — custom. Tailored to volume. Includes everything above plus the Secure AI Chat at scale.
The Data Processing Agreement is signed at signup with click-wrap consent and a cryptographic snapshot of the consent state. The redaction certificate is downloadable from the dashboard for every completed job.
The blog series we are publishing alongside the launch
Redaction is a horizontal capability with vertical-specific operational consequences. Alongside the launch, we are publishing a six-article series that walks through each of the five professional verticals where the redaction layer matters most, anchored on a foundational pillar guide.
- The pillar guide — the underlying technology, the GDPR framework, the two redaction modes, an eight-point evaluation checklist.
- The shadow AI in HR cluster — covering CV screening, performance review drafting, exit interview synthesis, and the EU AI Act Annex III high-risk classification.
- The accountants and tax practices cluster — covering the GDPR + AMLD6 + professional secrecy stack and the multi-employee XLSX workflow.
- The legal practice cluster — covering contracts, court filings, e-discovery productions, M&A data rooms, and the Mata v Avianca precedent.
- The payroll bureau cluster — covering the dual-role processor relationship, multi-tenant blast radius, and tenant-scoped redaction.
- The notarial practice cluster — covering the dual controller/processor role, multi-decade archival retention, the SHA-256 certificate as legal-grade evidence, and the Hague Apostille cross-border infrastructure.
Each article is published in English, Italian, French, German, and Spanish, with sources cited from the underlying legislation and case law. Read whichever ones map to your practice.
What is next
The product is live now. The Solo and Firm plans are self-serve at redactic.eu; Enterprise contracts go through the standard commercial process. The full sub-processor list, DPA, and trust pages are public. If you want to see Redactic on a sample document, the landing includes a live demo on a sample contract.
We will keep building. The roadmap includes batch processing for high-volume firms, reusable redaction templates for repeat document types, and tighter integration with the eIDAS qualified-signature stack for the notarial use case. The fundamentals — no-trace, EU-only, signed DPA, cryptographic certificate — are not on the roadmap because they are already shipped and they are not negotiable.
If you have questions about how Redactic fits into your firm's compliance architecture, the trust pages have most of the answers. If you have a specific use case the FAQ does not cover, get in touch.