Privacy & trust
Separate transport security, retention promises, operator access, and confidential execution.
In this chapter
Privacy is not one switch#
HTTPS protects a connection in transit. It does not prevent the receiving server from seeing plaintext. Hiding a buyer's wallet or email from a supplier does not hide personally identifying information the buyer types into the prompt. Paying with crypto does not make payments anonymous.
Conversation history is stored per account (auto-saved chats, exportable and hard-deletable from Profile). Accounts, key metadata, authentication state, waitlist data, and supplier applications are different kinds of information stored for their respective functions. There has not been an independent audit proving a blanket zero-retention service.
Intended privacy tiers#
| Tier | Intended protection | Limit |
|---|---|---|
| Standard provider access | Encrypted transport and disclosed provider policies. | The serving operator can process plaintext; retention terms apply. |
| Zero-retention supply | Controlled or vetted infrastructure with enforceable no-content-retention commitments. | Requires trust in operational controls and contracts; a checkbox is not proof. |
| Attested confidential execution | Verified hardware/runtime isolation with client encryption where supported. | Depends on supported hardware, attestation verification, and implementation security. |
Controls required as the service grows#
- Keep prompt bodies out of logs, analytics, traces, error reporting, and support exports by default.
- Keep financial usage metadata separate from conversation content.
- Publish subprocessors, regions, retention rules, and exceptions before accepting sensitive workloads.
- Do not send a buyer's account identifiers to suppliers unless necessary and disclosed.
- Make persistent knowledge/history features opt-in with isolation and deletion controls.
- Honor privacy requirements during selection and fallback; fail closed if no eligible provider exists.
- Keep prompts and responses off-chain. Even content hashes can leak or correlate information in some circumstances.
What users should do now#
Use non-sensitive test material until a model's data-handling path is explicitly documented and available. Do not paste passwords, private keys, secrets, regulated records, or other people's confidential data into a model simply because the interface displays a shield icon.
The eventual privacy notice and service terms need an operating entity, applicable jurisdictions, concrete retention periods, access/deletion processes, and provider agreements. This handbook describes technical boundaries; it is not a replacement for those documents.