Privacy Policy
Kurz gesagt
- Your content is end-to-end encrypted. We can’t read it.
- We don’t sell data, show ads or train AI on your content.
- We keep only the metadata needed to run the service.
- Text you send to AI is processed in transit, never logged or stored.
- No third-party trackers or analytics on our sites and apps.
- Delete your account and your encrypted data goes with it.
1. Who we are
Timbler (“we”, “us”) runs the apps and services described in this policy. Timbler is not a registered legal entity. Questions about privacy: privacy@timbler.org.
2. What we process
| Data | Examples | Visible to us |
|---|---|---|
| Your content | Notes, files and file names, documents, chats, AI memory, Vault, mail cache, Coworker tasks | No — end-to-end encrypted |
| Sync metadata | Opaque ids, sizes, versions, timestamps, structure of encrypted nodes | Yes |
| Account data | Email, name, sign-in events, security settings, organizations | Yes |
| AI requests | Text and files you send to a model | In transit only |
| AI usage facts | Service, model, token counts, time | Yes |
| Payments | Payments you make, processed by Stripe | Yes |
| Technical logs | IP address, user agent, request status — without content | Yes, short-term |
We never receive your encryption keys. Your account key is created on your device; we store only wrapped copies that we cannot open.
3. Features that need plaintext
A few features cannot work on encrypted data. Each runs only on your action or under a grant you approve, in memory, without logs or storage of content:
- AI requests — the text you send goes through our AI gateway to the model provider you chose.
- Office import and export in Magic Office — conversion in a transit service with no disk and no network.
- Code sandbox in AI Chat — a disposable container with no network.
- Connecting GitHub or GitLab — the OAuth token passes once through our server.
- Mail sync — our mail worker talks to your provider and immediately seals messages to your key.
- Agents — Coworker and Code agents access data only under time-limited grants.
Details: Security.
4. Why we process data (legal bases)
- To provide the service you signed up for — account, storage, sync.
- To keep the service secure and prevent abuse.
- To meet legal obligations.
Under the UK GDPR (Art. 6) we rely on: performance of a contract — running the service you signed up for; legitimate interests — security and abuse prevention; legal obligation — where the law requires us to keep or disclose data. We don’t rely on consent for anything that the service needs to work, and we don’t process data for advertising.
5. AI model providers
When you use AI, your request is sent to the provider of the model you selected (or that the smart router picked). Timbler connects directly to Anthropic, OpenAI, Google and DeepSeek. An organization can connect its own provider instead; then its requests go there. Where each provider processes requests and how long it retains them is governed by that provider’s own terms and privacy policy; Timbler does not add its own copy — our gateway doesn’t log or store the text.
6. Subprocessors
We use a small number of service providers: Hetzner (Finland, EU) for hosting, object storage and email delivery, and Stripe for payments. They receive only encrypted content or the account and payment data they need. See Subprocessors.
7. Retention
- Trash: 30 days, then permanently deleted.
- Versions: the last 100 versions for up to 30 days, unless you choose to keep one forever.
- Background AI answers: up to 1 hour, sealed to a one-time key of your device.
- Mail cache: headers of all messages and bodies of the last 90 days, sealed to your mailbox key.
- Account deletion: your account and data are deleted immediately; encrypted copies in backups expire within 3 months.
8. Your rights
You can access, export, correct and delete your data, and object to processing. Because your content is encrypted, export happens in your apps, on your device. For anything else, contact us at privacy@timbler.org.
If you are in the UK, your rights come from the UK GDPR and the Data Protection Act 2018, and you can complain to the Information Commissioner’s Office (ico.org.uk). If you are in the EU/EEA, you have the same rights under the GDPR and can complain to the data protection authority of your country. Please contact us first — we’ll try to fix it.
9. Cookies
We use only strictly necessary cookies for sign-in sessions. Encryption keys are never stored in cookies. No advertising or analytics cookies. See the Cookie Policy.
10. Children
Timbler is not intended for anyone under 18. We don’t knowingly collect data from children; if you believe a child has created an account, contact us and we’ll delete it.
11. Changes
We’ll announce material changes on this page and by email before they take effect. Previous versions stay available on request.