How many times have you manually redacted data—such as a PESEL number, account number, or customer’s last name—before forwarding a document? And how many times has someone in your organization pasted a section of a contract into ChatGPT to “quickly check” a single clause—without thinking about what happens to that data afterward?
This is a daily reality for most companies. And this is precisely the problem that the new integration—which we’ll be showcasing—solves on September 24, 2026, during the BTC Roadshow 2026 in Warsaw — the launch of eAuditor V10.2 with built-in support for Bluur AI, our AI-powered document anonymization engine.
What’s New in V10.2
Until now, anonymizing a document meant one of two things: tedious, manual work or using a separate tool that required logging in, uploading a file, and downloading the result. In V10.2, this step is eliminated—the anonymization feature is integrated directly into the eAuditor Employee Dashboard, in both the on-premise and Cloud versions.
How does this work in practice?
- Drag a document (TXT, PDF, DOC, or DOCX) into the anonymization window—or simply paste the text.
- You select a predefined anonymization scheme that has been set up by the administrator.
- In just a few seconds, you’ll download an anonymized version of the file.
No new app. No new login. No integration for the IT team to build.
Why does this matter, and why isn’t it just “another feature”?
Company documents are constantly circulating outside the organization: they end up with auditors, suppliers, law firms, software developers, and—increasingly—AI tools such as ChatGPT, Copilot, and Gemini. Each such transfer is a potential point of leakage for personal data or confidential information.
Let’s look at a few typical situations from our daily work:
The bug report is sent to the software vendor. An employee receives an error report → anonymizes it with a single click → forwards it, without the risk of customer data remaining in the logs.
HR wants to review the resume with the manager. The resume is uploaded to the system → it is anonymized → the manager evaluates the candidate’s skills, not their sensitive personal information, during the early stages of the recruitment process.
Someone wants to ask the AI to analyze a contract. The document is anonymized → only then is it sent to an external AI tool. Sensitive data never leaves the organization in a form that can be linked to a specific individual.
The marketing department prepares training materials based on actual client documentation. Instead of creating fictional examples from scratch, it anonymizes real documents and uses them securely in presentations or webinars.
This isn’t a list of theoretical scenarios—it’s the day-to-day reality for IT, HR, legal, sales, customer service, and production departments; however, in most companies today, this process is manual, inconsistent, or nonexistent.
Who will benefit the most?
- IT and Help Desk — anonymization of logs, reports, and tickets before they are forwarded to the manufacturer’s support team or published in the knowledge base.
- HR and Personnel — securely share resumes, contracts, and employee evaluations without having to manually remove PESEL numbers and account numbers.
- Legal Department — anonymizing contracts and correspondence before forwarding them to an outside law firm.
- Sales and Marketing — preparing proposals, testimonials, and case studies without disclosing customer data.
- Management — securely sharing documents with consultants, investors, and law firms.
- Public Administration — Publication of Decisions and Responses in Compliance with Personal Data Protection Requirements.
In short: every department that regularly sends documents outside the organization gains a single, standardized, and controlled tool instead of a haphazard and unregulated process.
What about NIS2, ISO 27001, KSC, and DORA?
None of these regulations explicitly state, “Implement AI anonymization”—but they all follow the same logic: the less sensitive data circulates outside the organization, the lower the risk and the less severe the consequences of an incident. Anonymization is one of the simplest and most effective ways to implement this principle.
- NIS2 requires the implementation of technical and organizational measures to mitigate information security risks—including those related to supply chain security. Anonymizing documents shared with suppliers and partners directly meets this requirement.
- ISO/IEC 27001 — this integration supports the controls in Annex A regarding the classification of information and the secure sharing of data with external parties, which is an element of implementing the data minimization policy.
- The National Cybersecurity System (KSC/UKSC2) — for critical and important entities, it mitigates the risk of information disclosure when collaborating with suppliers and service providers, which is particularly important ahead of the upcoming compliance deadline.
- DORA — helps financial institutions securely share documentation with ICT providers and manage third-party risks.
In other words: it’s a tool that supports the implementation of these requirements in day-to-day work—not a magical compliance checkbox, but a concrete, measurable component of the information security policy.
Why in the Employee Dashboard, specifically, and not as a separate app?
This is probably the most important question to ask when looking at this integration—and that’s exactly why we believe this solution will actually work, rather than becoming just another feature that no one remembers.
- The employee isn’t learning anything new. The feature is right where it’s already used every day—submitting tickets, checking access, and using remote support.
- IT isn’t building another integration. No SSO, no API to integrate the two systems, no additional implementation costs.
- Security is consistent. Permissions for anonymization are granted in the same place as all other access permissions in eAuditor—a single IAM model, not two.
- The administrator—not an employee—sets the rules. Anonymization schemes are defined once, centrally—so the entire organization applies the same rules, rather than relying on each user’s individual judgment.
- The document never leaves the controlled environment before it is anonymized—it does not end up in some random, free tool found through a search engine.
It is also the first solution on the Polish market to combine an ITSM/ITAM system with built-in, AI-based document anonymization accessible from the employee dashboard—none of its major competitors currently offer this feature.
Check it out live
We will showcase the integration of eAuditor V10.2 with Bluur AI for the first time on September 24, 2026, at the BTC Roadshow 2026 in Warsaw. If you manage IT, information security, or compliance in your organization and are wondering how to practically reduce the risk of data breaches while safely using AI—this event is for you.