Skip to content

Set up Presidio (Docker / hosted by evanto)

Admin

CompanyWizard’s PII detection uses Presidio, an external service that is not shipped with the product. You run it yourself (Docker) or have it run dedicated by evanto (Managed operation, tier L). What the PII shield does functionally is explained in The PII shield.

Setup: Presidio as an external service (Docker or Managed operation by evanto) is connected via an endpoint; the PII pipeline calls it before every model handoff. Setup: Presidio as an external service (Docker or Managed operation by evanto) is connected via an endpoint; the PII pipeline calls it before every model handoff.

Start Presidio as a Docker container in your environment or run your Site instance in Managed operation: from tier L evanto runs Presidio dedicated per customer. A ready-made Compose setup (minimal quickstart and multilingual de+en build) is provided in Self-host Presidio (Docker Compose). → Data sovereignty

Enter the address of the analyzer endpoint — statically via PiiScanner:PresidioEndpoint (Environment variables) or dynamically in Administration → System settings, where you can also adjust the threshold, entity types, and languages and test the connection.

With detection switched on, the PII pipeline calls Presidio before every model handoff, pseudonymizes detected data, and re-identifies it in the response — within your instance.

When Presidio is unreachable, CompanyWizard operates gracefully degraded: chat keeps running, but detection then falls back to simple pattern matching only — email addresses, phone numbers, IBANs, credit card numbers and IP addresses; not names or postal addresses. The status in the chat then shows “PII Shield Degraded”. Therefore monitor the Presidio health status; where pseudonymization is mandatory, operation without a reachable Presidio should be prevented. With PiiScanner:Enabled = false you can deliberately switch detection off (inputs run unmasked).

  • Admin-only. The endpoint/parameters are maintained in Administration.
  • External: no local PII engine in the app; Presidio must be running.
  • Web vs. Desktop: same logic; Presidio must be separately reachable in both cases.