eAuditor V10.2 and Bluur AI: the document anonymisation every IT department has been dreaming of

Less risk, more control over data

Table of contents

Ordering contact

Introduction

How many times have you had to manually redact data such as a PESEL number, bank account number or a customer’s surname before forwarding a document? And how many times has someone in your organisation pasted a section of a contract into ChatGPT to ‘quickly check’ a single clause — without giving a second thought to what happens to that data afterwards?

This is everyday life for most companies. And it is precisely this problem that is solved by the newly integrated feature we’ll be unveiling on 24 September 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 anonymisation 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.

What does it look like in practice?

  1. Drag and drop a document (TXT, PDF, DOC, or DOCX) into the anonymization window — or simply paste the text.
  2. Select a ready-made anonymization template previously defined by the administrator.
  3. Within seconds, download the anonymized version of the file.

No new application. No new login. No IT integration to build.

Why this matters — and why it’s more than just “another feature”

Corporate documents constantly circulate outside an organization: they are shared with auditors, vendors, law firms, software providers, and increasingly with AI tools such as ChatGPT, Copilot, or Gemini. Every such transfer creates a potential point of exposure for personal data or confidential information.

Let’s look at a few common, everyday workplace scenarios:

A bug report needs to be sent to a software vendor. An employee receives the report → anonymizes it with a single click → forwards it safely, without the risk of customer data remaining in the logs.

HR wants to review a CV with a manager. The CV is uploaded to the system → anonymized → the manager evaluates the candidate’s skills rather than being exposed to sensitive personal information at an early stage of the recruitment process.

Someone wants to use 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 team wants to create training materials based on real customer documentation. Instead of creating fictional examples from scratch, they anonymize real documents and safely use them in presentations, webinars, or other materials.

These are not theoretical use cases — they are part of the everyday reality of IT, HR, legal, sales, customer service, and production teams. Yet in most companies today, this process is still manual, inconsistent, or simply does not exist.

Who Benefits the Most

  • IT and Help Desk — anonymizing logs, reports, and support tickets before sending them to a software vendor’s support team or publishing them in a knowledge base.
  • HR and Payroll — securely sharing CVs, contracts, and employee evaluations without manually removing national identification numbers, bank account details, and other sensitive information.
  • Legal — anonymizing contracts and legal documents before sharing them with external law firms.
  • Sales and Marketing — preparing proposals, references, and case studies without exposing customer data.
  • Executive Management — securely sharing documents with consultants, investors, and law firms.
  • Public Administration — publishing decisions and official responses in compliance with personal data protection requirements.

In short: any department that regularly shares documents outside the organization gains a single, consistent, and controlled tool instead of relying on individual judgment and ad hoc processes.

What about NIS2, ISO 27001, KSC, and DORA?

None of these regulations explicitly says, “implement AI-based anonymization” — but they all follow the same principle: the less sensitive data that circulates outside the organization, the lower the risk and the smaller the impact of a potential incident. Anonymization is one of the simplest and most effective ways to put this principle into practice.

  • NIS2 requires organizations to implement technical and organizational measures to reduce information security risks, including risks related to supply chain security. Anonymizing documents shared with vendors and business partners directly supports this requirement.
  • ISO/IEC 27001 — the integration supports Annex A controls related to information classification and the secure sharing of data with external parties, helping organizations implement data minimization policies.
  • Polish National Cybersecurity System (KSC/UKSC2) — for essential and important entities, it helps reduce the risk of information disclosure when working with vendors and service providers, which is particularly relevant in view of the upcoming compliance deadline.
  • DORA — in financial institutions, it supports the secure sharing of documentation with ICT service providers and helps manage third-party risk.

In other words, this is a tool that supports compliance with these requirements in day-to-day operations. It is not a magic compliance checkbox, but a concrete and measurable element of an organization’s information security policy.

Why Put It in the Employee Portal Instead of a Separate Application?

This is probably the most important question to ask when looking at this integration — and it is exactly why we believe this solution will actually be used rather than becoming just another feature that everyone forgets about.

  • Employees do not need to learn anything new. The feature is available where they already work every day — submitting tickets, checking access permissions, and using remote support.
  • IT does not need to build another integration. No additional SSO setup, no API integration between two separate systems, and no extra implementation cost.
  • Security remains consistent. Anonymization permissions are managed in the same place as all other access rights in eAuditor — one IAM model instead of two.
  • The administrator, not the employee, defines the rules. Anonymization templates are configured once and managed centrally, ensuring that the entire organization follows the same rules instead of relying on each user’s individual judgment.
  • The document never leaves the controlled environment before it is anonymized. It is not uploaded to a random free tool found through a web search.

It is also the first solution on the Polish market to combine an ITSM/ITAM platform with built-in, AI-powered document anonymization available directly from the employee portal — and currently, none of the major competitors offers this capability.

See it live

We will showcase the eAuditor V10.2 integration with Bluur AI for the first time on 24.09.2026 at BTC Roadshow 2026 in Warsaw.

If you are responsible for IT, information security, or compliance in your organization and are looking for practical ways to reduce the risk of data leakage while using AI securely, this event is for you.

2026-08-07T13:57:38+02:00