A useful privacy feature should come with a clear explanation of its limits.
| Planned V1 safeguards | Important limitations |
| Recognition and masking of certain personal identifiersUsing a Presidio-based approach. | Unusual identifiers, indirect clues, or contextual information may be missed. |
| Secrets scanning and gateway checksBefore model or tool requests leave the workspace. | Trade secrets, proprietary strategies, and unpublished ideas may not look like recognizable credentials. |
| Policy-based routingTo approved external AI providers. | Approved providers may still process transformed prompt content under their applicable terms. |
| Encrypted storage and conversation controlsIn the proposed architecture. | Exact retention periods, deletion behavior, exceptions, and availability require confirmation. |
Masking is not the same as complete anonymity. Nor does a commitment not to train on customer data necessarily mean that a provider retains no information. More advanced concepts such as semantic trade-secret detection, reversible token vaults, self-hosted private inference, and confidential computing should not be assumed to be available.
If you are handling regulated, contractual, or client-confidential material, check that AI use is authorized before sharing it. Privacy safeguards support responsible decisions; they do not replace them.