Privacy and responsibilities
Confirm your deployment’s data boundary before sending sensitive information. Where the Proxy runs, which model provider it calls and what evidence it retains are separate decisions.
Content and evidence are different
Section titled “Content and evidence are different”The Proxy processes request and response content to apply configured controls. In Glacis Hosted deployments, that processing happens in Glacis-managed infrastructure. Allowed provider calls send content to the model provider you configure; that provider’s data practices need a separate review.
Signed evidence is not automatically a transcript archive. Check the active recording settings and the supported evidence export before assuming that an original prompt or response can be retrieved.
Avoid placing personal information, secrets or free-form transcript content in metadata labels. Labels may be retained as evidence even when the original content is not.
Agree the responsibilities
Section titled “Agree the responsibilities”| Area | What your team should confirm |
|---|---|
| Application routing | Which operations use the Proxy and how bypasses are identified. |
| Credentials | Who manages application and provider credentials, and how an exposure is handled. |
| Controls | Workload-specific evaluation, available models, actions and review responsibilities. |
| Evidence | Recording scope, access, storage, retention, retrieval and verification keys. |
| Operations | Availability, updates, recovery, support access and account closure arrangements. |
Glacis manages Glacis Hosted infrastructure. Self-hosted responsibilities depend on the agreed operating arrangement. A private network connection does not change the application’s authorization requirements or the location of Glacis Hosted processing.
Make assurance claims within scope
Section titled “Make assurance claims within scope”A control result or valid receipt does not certify a clinical outcome, regulatory compliance or an entire application. Confirm applicable agreements and workload acceptance with the responsible reviewers before using regulated data.
Use Deployment options to compare operating boundaries and Receipts and trust to understand what can be checked from an artifact.