Security
What we do with your keys, and what we cannot do.
You are about to hand a tool the keys to your systems. That deserves a straight answer, so here is one in plain words.
Your keys are locked before they are stored
Every password, token and key is scrambled the moment you save it. The code that unlocks it lives in the running service and never in the database, so a copy of the database is a pile of nonsense to whoever holds it. Once saved, a secret is never shown again. You see dots. So does everyone else, administrators included.
It signs in as you, so it sees only what you see
Worclaude uses the account you connect with. A table you cannot query and a page you cannot open stay closed to it as well. There is no shortcut around your own permissions, which also means you can test what it can reach by asking whether you can reach it.
A database source can look, never touch
Database sources are read only. No question, however it is worded, can change or delete your data. Give it an account with read rights and it has everything it needs.
Your documents are copied only when you ask
Documentation is imported once so it can be searched quickly. Databases and trackers are never copied. They are read at the moment you ask and nothing is kept. When you disconnect a source, our copy of its content goes with it, in the same breath.
Sharing a chat is not sharing a source
People you invite to a chat can read it and suggest questions. They cannot use your sources, see your credentials, or ask anything of your systems on their own. If they want a source too, they send you a request and you decide. Take the access back whenever you like.
Your model key stays yours
Bring a key from Claude, Bedrock, OpenAI or a model you host, and your questions go to that provider under your own account. You pay them directly. We add nothing on top and we do not sit in the middle of that relationship.
There is a record of what happened
Sign ins, source changes and every tool that ran are written to a log your administrators can read, kept for ninety days by default. Secrets are stripped out of it before it is written, so the log can be read in full without leaking anything.
Or run the whole thing yourself
Worclaude can run inside your own infrastructure. Then the database, the search index and the keys are all on machines you own, and nothing crosses your boundary at all.
Something here you need in writing, or a question this page did not answer? Ask us