Why integration keys are never sent to your browser

A core principle of HIIE's integration layer is that the keys powering your connections stay on the server. The browser never receives them — only masked hints are ever shown.

What this covers

This applies across the board:

• The Composio key that powers your connections is resolved server-side and never reaches the browser, in every key mode (BYO, dedicated project, or shared).
• Your BYO Composio and OpenRouter keys in the Credentials vault are encrypted at rest and never returned to the browser; you see only a masked hint after saving.
• The Environment tab shows BYO and dedicated-project keys as masked hints only.
• During a connection, the request goes to a server-side route so the Composio key is used without being exposed to the client.

How it's protected

Keys are stored encrypted at rest (AES-GCM) and read only on the server. No resolved key is sent to the browser or written to logs. This keeps your credentials out of client-side code, browser memory, and network traffic that the page could read.

An important nuance

This design keeps keys off the client, but it is not zero-knowledge or end-to-end encryption. HIIE's servers can decrypt and use your keys to perform the actions you authorize — that's how Camelia executes integration actions on your behalf. The guarantee is that the key never leaves the server, not that the operator cannot use it.

What you should do

Because raw keys are shown only once (or never), keep your own copy of any BYO key you may need elsewhere, and rotate dedicated project keys from the Environment tab when appropriate.