What happens to your credentials
Encrypted per secret, never in a prompt, never visible to us.
On this page
When you connect software you hand over something sensitive. Here is exactly what happens to it.
Encrypted with a key of its own
Each secret is encrypted with its own key, and that key is encrypted with a master key. Rotating the master key does not require re-encrypting every secret, and compromising one does not expose the rest.
Never in a prompt
The model sees tool names, descriptions and argument schemas. It does not see connection details, hostnames, or anything you entered as a credential. The connector decrypts the secret at the moment of the call and holds it only for the duration.
This is not a matter of trusting one AI provider more than another. There is no version of "your database password went to a third party" that we are comfortable with.
Not visible to administrators
Nobody at Caterfli can read your credentials, including through the admin panel. Support can see that a connection exists and whether it is healthy. They cannot see what is in it.
What we ask you not to do
Do not paste credentials into any of these. We never need them, and none of them is built to hold one.
- a support ticket
- a chat message
- an agent's instructions
Sources and further reading
- Google Cloud: envelope encryption — docs.cloud.google.com
- OWASP Secrets Management Cheat Sheet — cheatsheetseries.owasp.org