Learn
Understand how Chrysaor works.
Chrysaor is designed to make privacy, storage, security, and everyday use understandable. Explore the architecture behind the service, how a workspace is created, where your information goes, how to get help, and where to see service status.
Privacy architecture
Understand where your content lives, where encryption happens, and what Chrysaor services can and cannot access.
Read this section ↓How it works
Follow the path from account creation to workspace setup, storage, synchronization, and everyday use.
Read this section ↓Help center
Find practical information about setup, recovery, storage, exports, privacy, and support.
Read this section ↓Status
See the systems Chrysaor monitors and the current service status.
Read this section ↓Privacy architecture
A design you can inspect, not a slogan.
Here’s where Mail, Calendar, Docs, and Notes content can exist, and what happens in each place.
Your device
- Readable Mail, Calendar, Docs, and Notes content exists here.
- Encryption keys are generated on the device.
- Content is encrypted before it leaves the device.
- Content is decrypted for reading only on an authorized device.
- Keys are not designed to be sent to Chrysaor’s backend.
Your storage
- Synchronization is optional.
- When enabled, only encrypted objects are sent to the storage location you choose.
- Options include a user-controlled WebDAV server, self-hosted storage, or a connected encrypted provider.
- You can see which storage location is connected at any time.
Chrysaor services
- Short-lived email verification.
- Essential abuse protection.
- Security operations and events.
- Operational data, kept separate from readable workspace content.
In short: your device handles readable content and encryption. Your chosen storage holds encrypted objects only, when you turn sync on. Chrysaor services are scoped to verification, abuse protection, and security operations — not to reading your workspace. We don’t say “we store nothing,” and we don’t use “end-to-end encrypted,” “zero-access,” or “no logs” until the implementation and a security review actually support those exact claims.
How it works
From your current inbox to a private workspace.
Four stages, in plain terms — no jargon, no hidden defaults.
Verify
Chrysaor begins with an email address you already have. A short-lived verification code confirms it’s yours. Verifying it is not the same as subscribing to a mailing list.
Secure
A device key is generated on your device and used to enable decryption there, ideally through a passkey. Where a recovery alternative exists, its limits are explained honestly rather than glossed over.
Choose
This device only keeps content local. Connect my storage links WebDAV, self-hosted, or a supported encrypted provider — only adapters that actually exist are ever offered. Explore with sample content uses clearly labeled fictional data.
Work
Mail, Calendar, Docs, and Notes come together in one workspace, with contextual actions between them that you always confirm before anything is created.
A message can become:
Each of these is a user-initiated action with an editable confirmation first — nothing crosses between Mail, Calendar, Docs, and Notes on its own.
Help center
How can we help?
Setting up your account
Email verification, device keys, and passkeys, plus what recovery options are available and how they’re configured.
Account recovery
Recovery options depend on what you configured. If a device key is lost with no recovery method set up, encrypted content tied to it may not be recoverable.
Choosing and changing storage
Use this device only, or connect WebDAV, self-hosted storage, or a supported encrypted provider. See and disconnect what’s connected from Settings.
Exporting your content
Exports are generated locally where applicable, for Mail, Calendar, Docs, and Notes. We only describe export formats that actually exist today.
Privacy basics
Your device handles readable content. If sync is on, encrypted content goes to storage you choose. Chrysaor services are scoped to verification and essential abuse protection.
Read the privacy architecture →Getting support
For account or product questions, reach us directly. For a security issue, use the responsible-disclosure contact on the Security page instead.
Contact support →No articles match that search. Try a different term, or contact support.
Status
Service status.
A transparent view of the systems Chrysaor depends on.
Incident history
No incidents have been recorded. Once a real monitoring system is connected, this area becomes the historical incident log.