Built so that we can't look.
Trust shouldn't depend on our good behaviour. Timbler is designed so that a full copy of our databases reveals nothing about what you write, store or say.
One account key. Many narrow subkeys.
Each app receives only the subkey it needs. Vault and items you mark “always ask” require a fresh unlock every time.
Where plaintext exists — and why.
Some features can’t work on ciphertext. Each exception is narrow, explicit and handled in memory only.
AI requests
The text you send to a model reaches it through our gateway.
Office import and export
Converting .docx, .xlsx and .pptx when you click Import or Export.
Code sandbox
Running model-written code over files of a chat, when the tool is enabled.
Connecting GitHub or GitLab
The OAuth exchange needs a server-side secret.
Mail sync
IMAP and SMTP need to talk to your provider.
Agents
Coworkers and Code agents act on your data.
How unlocking works
Your account key is a random 32-byte key created on your device. Timbler Account stores only wrapped copies of it — one per passkey, one for your encryption phrase and one for your recovery phrase. The account service cannot unwrap any of them.
The key is unwrapped only in Key Hub (keys.timbler.org), a separate origin with a strict content security
policy. Key Hub then hands each app just its own subkey. Apps keep that subkey on the device, so the UI doesn’t
lock you out every time you open a tab. An optional device lock protects it on shared machines.
- Keys are never derived from your sign-in password.
- Keys are never stored in cookies.
- Losing every passkey and both phrases means losing access to your data. We cannot recover it.
What our servers store
| Data | What we see |
|---|---|
| Notes, documents, files, chats, memory, Vault, mail cache | Encrypted blobs only |
| File, folder and note names | Encrypted |
| Sync metadata | Ids, sizes, versions, timestamps, folder structure as opaque nodes |
| Account | Email, sign-in events, security settings |
| AI | Usage facts: who, service, model, tokens, time |
Infrastructure
- Untrusted content runs elsewhere. File previews, HTML mail, chat widgets, the IDE sandbox and public Drive
links run on a separate registrable domain, never on a
timbler.orgsubdomain, without cookies and under a sandbox CSP. - Least privilege between services. Each service has its own minimal set of secrets; service-to-service tokens are short-lived and verified against published keys.
- Agents act under grants. Server-side agents get your data only through explicit, time-limited grants you approve. Instructions to machines are signed with your key.
- One cryptography package. All encryption formats and labels live in a single package that changes only with review and test vectors, and freezes at the first production release — later versions only extend it.
Report a vulnerability
Please report security issues to security@timbler.org. We’ll acknowledge within 3 days. Please give us reasonable time to fix an issue before disclosing it, and don’t access other people’s data while testing.
To encrypt your report, use our PGP key: pgp-key.txt, fingerprint 73F3 4849 4DC4 71FF 91D8 1986 4D94 D85E E713 1F95.
We have no external audits or bug bounty program yet.

Bring your work home.
One account for every app. Takes a minute and a passkey.