Technology and protection boundaries
Supported text is checked for sensitive information and masked before model processing. Responses are restored using the corresponding mapping to preserve useful context.
Standard API access uses HTTPS. Changing the endpoint and API key does not enable end-to-end encryption or strict remote attestation.
Text protection applies to currently supported message content. Detection depends on model capabilities and configuration and cannot guarantee identification of every sensitive detail.
Confirm image, vision and file protection separately. Text masking does not imply that every attachment is protected.
Enhanced client access and trusted environment verification depend on the actual deployment and supported client protocol. The alpha attestation flow is not a strict production attestation guarantee.
WARNING
These are product boundaries, not legal certification, a model identity guarantee or a promise of zero data leakage. See the User Service Agreement for data handling and retention.