Relay security model

Standalone credentials

AnchorShell Relay — Self-Hosted encrypts provider credentials at rest with AES-256-GCM and a local environment master key. The admin token and encryption master key have separate purposes and must remain separate.

Hosted request identity

AnchorShell Platform authenticates hosted callers and signs short-lived Relay context containing the organization UUID, user UUID, product key, and permission strings. Hosted Relay rejects missing, expired, tampered, wrong-product, or insufficient context before provider routing begins.

The signed context must not contain prompts, response bodies, provider keys, browser cookies, or raw external API keys.

Request data

Operational metadata is recorded for queueing, route selection, status, timing, tokens, and configured cost. Request, upstream-request, and response body storage is controlled by an explicit self-hosted Relay setting and defaults off. This is a configuration fact, not a universal contractual non-retention guarantee.

Reporting

Use the public security page and security.txt contact. Do not send secrets, credentials, or sensitive model payloads in an initial vulnerability report.

AnchorShell does not currently claim a public certification, penetration-test program, or bug bounty.