In transit
Every public endpoint (app, API, sign-in, previews) is served over HTTPS with automatically renewed certificates.
Encryption and secrets
This page says what is protected and how, in plain terms, including what is still planned. We would rather you hear it from us than find it in a security review.
At a glance
Section titled “At a glance”Secrets in the application
Connector tokens and shared keys are encrypted by Lucy before they reach the database, with a key that is not stored in the database.
Secrets in our infrastructure
Platform secrets are stored encrypted in version control and only decrypted where they are used.
In transit
Section titled “In transit”- Public traffic is HTTPS. The app, the API, sign-in and published previews are reached over TLS, with certificates issued and renewed automatically.
- Sign-in uses OpenID Connect with PKCE. People authenticate at your identity provider, and Lucy never sees a password.
- Sign-out really signs out. When a person signs out, the access and refresh tokens are revoked at the identity service and dropped from the browser, so a stolen copy stops working.
- Services stay inside the platform. The model gateway, connector brokers and sandbox API are not reachable from the internet. They accept traffic only from the services that need them, enforced by network policy.
Secrets Lucy holds for you
Section titled “Secrets Lucy holds for you”| Secret | How it is protected |
|---|---|
| Connector tokens (Microsoft 365, Google Workspace, OAuth to your MCP servers) | Sealed with authenticated encryption before they are stored. The key is held outside the database. Each token is bound to your organisation, the person and the connector, so a sealed value cannot be replayed for someone else. |
| Shared keys for your own MCP servers | Sealed the same way. After you save one, Lucy shows only a short hint, never the value. |
| Your identity provider’s client secret | Handed to Lucy’s identity service when you save. Lucy itself never keeps or shows it. |
| Webhook tokens for agents | Stored as hashes, compared in constant time, never written to logs, and can be rotated. |
| Share and preview links | Signed, so they cannot be guessed or altered, and they stop working when the item is deleted or expires. |
Tokens never reach the model, the worker or a sandbox. They live in the connector brokers, which make the call on a person’s behalf and return only the result. See Isolation.
Secrets in our own infrastructure
Section titled “Secrets in our own infrastructure”Platform credentials (database passwords, signing keys, application secrets) are kept in version control encrypted, and are decrypted only inside the cluster that uses them. Nobody works from plaintext secret files.
Data at rest: where we are
Section titled “Data at rest: where we are”What we do today to limit what sits at rest:
- You decide how long data lives. Retention is set by you, the shortest setting wins, and a sandbox can keep nothing between sessions.
- Deletion is real. Expired data is removed by an hourly job, and removing a member deletes their data immediately.
- Saved sandbox workspaces hold files only. Not memory, processes or credentials.
Key management
Section titled “Key management”- Application encryption keys are held outside the database and are not available to the model, the sandbox or support tooling.
- Customer-managed keys are not offered yet. Tell us if you need them, so we can plan it.
What we are not claiming
Section titled “What we are not claiming”We do not claim a certification, a specific key length policy document or customer-managed keys today. See Compliance for where we stand on certifications.