![\"Anonymization](\"https:\/\/www.arcadsoftware.com\/dot\/wp-content\/uploads\/2026\/05\/anonymisation-textes-non-structures-ia-intelligence-artificielle.png\")
<\/span><\/div><\/div><\/div>By Florian Pusello \u00b7 June 4, 2026<\/p>\n<\/div><\/div><\/div><\/div><\/div>
What if you could anonymize unstructured text as easily as a database?<\/strong> For years, anonymization meant structured data: tables, columns, clear field names \u2014 a familiar landscape where finding a name or a social security number came down to a simple lookup. Today, sensitive data lives somewhere else entirely. It's buried in your emails, your logs, your PDFs, your reports, your customer exchanges. And free text gives you nothing to work with: no columns, no types, no metadata. You're starting from scratch. This is where AI changes the game for DOT Anonymizer: anonymization rules written in plain language, semantic detection, and full PDF anonymization. Here's how it works.<\/strong><\/span><\/p>\n<\/div><\/div><\/div> Key takeaways<\/span><\/p>\n<\/div> Generate your anonymization rules with AI<\/strong> in plain language \u2014 no technical expertise required.<\/p>\n<\/div><\/li> Detect sensitive data in free text<\/strong> using LLMs trained for each business domain.<\/p>\n<\/div><\/li> Keep your data in-house<\/strong> with fully on-premise processing. No public cloud.<\/p>\n<\/div><\/li> PDF, metadata and OCR<\/strong> supported with preservation of the original layout.<\/p>\n<\/div><\/li><\/ul><\/div><\/div> We started by integrating AI into rule generation. Anonymization rules aren't a commodity. They're a corporate asset \u2014 built around your applications, your controls, your business logic. Not a universal standard. Your DNA.<\/span><\/p>\n So we let AI write them. A business user types: \"For this IBAN field, apply the checksum formula based on the country code.\" That's it. What used to take Groovy code, deep technical knowledge, and hours of work now takes a sentence. The LLM generates the complete rule, ready to run in DOT\u00a0Anonymizer<\/a>.<\/p>\n The impact is immediate. Business users stop waiting on developers. Consultants stop rewriting the same scripts. Functional teams focus on what they actually know \u2014 the business \u2014 and AI handles the rest.<\/p>\n<\/div> Anonymizing free text across varied formats and contexts required a powerful tool. Not magical, but powerful. And that tool is artificial intelligence.<\/p>\n Take a single email, a medical report, a doctor-to-patient letter<\/span><\/a>, an internal note. Each one is packed with sensitive data. But there's no first_name<\/i> column telling you what's a name and what's a diagnosis. The structure simply isn't there.<\/span><\/p>\n Our answer: Large Language Models (LLMs), with two jobs.<\/p>\n<\/div> Find the sensitive data<\/strong> \u2014 names, social security numbers, medical treatments, anything that matters.<\/p>\n<\/div><\/li> Classify what each piece is<\/strong> \u2014 first name? IBAN? internal code?<\/p>\n<\/div><\/li><\/ul> Detection runs on models trained per business domain: personal data, financial data, medical data, with more in the pipeline. Each domain gets its own algorithm, tuned to the data and the context it actually appears in.<\/p>\n When the first pass finishes, you're not stuck with what the model gave you. Refine it in plain language: anonymize a field it missed, restore a field it shouldn't have touched. The interaction is conversational, the result precise \u2014 and no technical skill needed to get there.<\/p>\n Once you're happy with a workflow, save it as a template. Run it in batch on similar documents through the API or CLI. Scale it across the organization. The whole pipeline becomes industrial.<\/p>\n And here's the critical part: the LLM detects, but your rules transform<\/strong>. ChatGPT doesn't decide what happens to your data. You do. Your rules, your business logic, your consistency.<\/p>\n That consistency matters more than people realize. If \"John Smith\" becomes \"Alex Brown\" in your customer database, he needs to be \"Alex Brown\" in the related medical letter, in the application logs, everywhere. Otherwise the anonymization leaks. Our approach closes that gap across every data source you have<\/strong>.<\/p>\n One last thing: none of this leaves your infrastructure. Our AI integrations run fully on-premise. Your sensitive data stays where it belongs.<\/p>\n<\/div><\/div><\/div> Anonymize your unstructured text with AI<\/p>\n<\/div> Let's talk about PDFs. Every company runs on them \u2014 for sharing, archiving, processing. And they're uniquely difficult to anonymize.<\/p>\n<\/div> Extracting and anonymizing the text? Manageable.<\/p>\n<\/div><\/li> Preserving the exact layout of the original document? That's the hard part.<\/p>\n<\/div><\/li><\/ul> PDFs aren't just files to read. They feed business applications, populate test environments, drive automated pipelines. Break the layout and you break the systems that depend on it.<\/p>\n So we set a high bar: anonymize the content, leave the document visually intact, down to the character. A one-page document processes in about ten seconds, which makes high-volume runs realistic.<\/p>\n The same care goes into metadata \u2014 the part everyone forgets. Author name, originating company, software version: any of these can betray a document that looked perfectly clean. Picture a confidential tender response where \"Authored by: Company X\" sits quietly in the file properties. DOT Anonymizer<\/a> catches that.<\/p>\n And for scanned PDFs<\/b>, we handle OCR too<\/b>. The terrain gets rougher \u2014 handwriting, character-recognition gaps, source-to-output mismatches \u2014 but the goal stays the same: a usable, secure document at the end of the pipeline.<\/p>\n<\/div> Anonymizing unstructured text isn't at odds with scale. It works with it.<\/p>\n For organizations dealing with massive document volumes, DOT Anonymizer<\/a> fits into your existing architecture. Validate the engine once, then run it in batch through the API or CLI<\/strong>. Wire it to your scheduler. Run overnight, on weekends, whenever your production environments are quiet.<\/p>\n Throughput depends on document type and volume, but the pattern is the same: large flows handled without disrupting anything in production.<\/p>\n<\/div> The next milestone is the Magic Button: upload a document, click once, get it back anonymized. No configuration, no setup. The system identifies the regulated fields itself \u2014 GDPR<\/a>, CNIL, whichever framework applies \u2014 anonymizes them, and drops the result back into your folder. Zero friction, fully automated.<\/p>\n Beyond that, we're working on several fronts at once:<\/p>\n<\/div> PDF and Office documents<\/strong>, end-to-end \u2014 metadata, OCR, layout fidelity.<\/p>\n<\/div><\/li> New formats and use cases<\/strong>, because sensitive data keeps showing up in new places.<\/p>\n<\/div><\/li> Custom prompts<\/strong>, so every organization can define what \"sensitive\" means in their own world \u2014 a confidential price, a unique spec, a proprietary field.<\/p>\n<\/div><\/li> MCP and API integration<\/strong>, so AI-driven anonymization slots into your existing pipelines without disruption.<\/p>\n<\/div><\/li><\/ul> At ARCAD, \"long term\" means a few months. On data privacy, every day counts.<\/p>\n<\/div><\/div><\/div><\/div><\/div> Switch to AI-driven anonymization<\/p>\n<\/div> Florian spent years working with data on the business side of major enterprises before joining ARCAD Software as a Solution Architect. He now helps clients deploy and scale anonymization across Business Intelligence, Data Science, and AI projects.<\/p>\n For any question about anonymization, contact our specialists.<\/a><\/p>\n<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div> Request a trial version or a session in our sandbox!<\/p>\n<\/div><\/div><\/div>1. AI as a rule generator<\/h2><\/div>
2. The challenge of unstructured text<\/h2><\/div>
3. PDFs: a category of their own<\/h2><\/div>
4. What about large volumes?<\/h2><\/div>
5. What's next for AI-driven anonymization?<\/h2><\/div>
![\"Florian](\"https:\/\/www.arcadsoftware.com\/dot\/wp-content\/uploads\/2026\/05\/florian-pusello-specialiste-anonymisation.png\")
<\/span><\/div><\/div><\/div>About the author<\/h2><\/div>
Florian Pusello<\/h3><\/div>
Anonymization Solution Specialist<\/h4><\/div>
TRIAL VERSION \/ DEMO<\/h2><\/div>
Trial Version<\/h3><\/div>
![\"Test](\"https:\/\/www.arcadsoftware.com\/dot\/wp-content\/uploads\/2025\/04\/contact-trial-version.png\")
Try it now!<\/h4><\/div>