NautsAI software & research
Back to Bowden-PII

Bowden-PII / Guide 2 of 3 / 2 min read

How does Bowden-PII work?

Detect locally, replace consistently, and keep the original-value mapping under application control.

The reason

A useful request does not always need a real name.

Applications often send identifying details alongside the context a model actually needs. Reducing that exposure should happen before the request leaves the system.

Bowden detects supported identifiers and replaces them with consistent placeholders. The mapping stays separate. This reduces exposure, but context can still identify someone, so evaluation remains necessary.

48Nauts / Product guides

Detect supported identifiers

The deterministic runtime uses supported patterns and validators, including selected Swiss formats such as AHV/AVS and UID. The chosen policy determines the detection and replacement scope.

The website’s examples are prepared fictional inputs. They demonstrate the deterministic runtime and do not send your text to a live processing service.

Replace and separate

Detected values become typed placeholders. Repeated values keep the same placeholder within one call, while a separate mapping associates placeholders with their original values.

Only the reduced text needs to continue to the model. The mapping is sensitive and requires its own storage and access decisions.

  1. 01Local input
  2. 02Detection
  3. 03Reduced text + separate mapping

Restore only when appropriate

The application controls any restoration of original values. Decide where restoration is required and who is allowed to request it.

Evaluate missed detections, unnecessary replacements and the usefulness of the resulting text before placing the step in a production workflow.