What if a company just told you?

Here is what each product does with your data today, including what it doesn't do. We hold no compliance certifications yet, so we don't claim any.

Paddock

New artifacts can be opened by anyone with the link, with no sign-in. Agents publishing through MCP get that default, and you can change it per artifact in the web app or from the command line.
Thoughts are always private.
Session logs are encrypted in storage, but Paddock can decrypt them to serve them to you. This is not end-to-end encryption.
Installing the Claude Code plugin uploads qualifying sessions automatically. You can turn log upload off.
HTML you publish runs its own scripts inside a sandboxed frame.

The gates check that a design can be tested, and that private text stays private. They never judge the science.
The privacy gates catch likely restatements, but they are not a guarantee. A reworded note can get past an exact text match.
You still form the theory and decide on the next round. Research tests ideas. It does not come up with them.
Research publishes through Paddock and signs in through Chaio Identity, so it needs both.

Values are encrypted at rest with AES-256-GCM, using a master key that is held apart from the database. A copy of the database alone yields ciphertext for values.
This is server-side encryption, not end-to-end or zero-knowledge. The service decrypts a value when it is read.
Names, providers, descriptions and audit rows are stored as plain text.
A read scope covers every secret. There are no per-secret permissions yet.
A program you give a secret to can read it. Vault keeps secrets out of your code and chats, but it can't hide them from the program using them.