Answer
If details are taken out before sending, does that mean nothing leaves?
No, and anyone who tells you otherwise is overselling it. Replacing identifiers before routing reduces what leaves unnecessarily and makes that reduction automatic rather than dependent on someone remembering. It does not promise zero, and detection is not exhaustive.
What the step does
Supported identifiers that the detector finds are swapped for placeholders before anything is routed to a provider. The mapping back to the real values is kept separately, under the firm's control, and the response is restored locally.
The value is that it is part of the task. A person doing it by hand does it well on a Tuesday morning and skips it on a Friday afternoon.
Where it stops
Detection is not exhaustive. It finds the classes of identifier it supports, in the forms it recognises. Documents are messy and language is inventive, and a claim of completeness would fall apart the first time somebody tested it properly.
The rest of the document still goes. If the substance of a matter is sensitive independently of the names in it, taking the names out does not solve that, and the honest answer is to think about whether that job belongs in an external tool at all.
Why we say this out loud
It would be easy to write a headline about protecting client identifiers and let people assume it meant nothing leaves. Plenty of products do.
The claim we can defend is narrower and more useful: it reduces exposure, it makes the reduction consistent, and it does not promise zero.
FlowClave is a software workflow. This is not legal, privacy or compliance advice, and it does not make a firm compliant with anything. Your firm remains responsible for its own obligations.