Almost every to-do app says your data is “encrypted”. That word covers very different promises. The useful question is not whether data is encrypted, but who holds the key — and therefore who can read your tasks.
The big picture
Encryption turns readable text into ciphertext that only someone with the key can turn back. Every model below uses strong algorithms such as AES-256. They differ in where the data is encrypted and who keeps the key.
A to-do list analogy
Imagine you post your to-do list to a storage company every night.
- In transit is a sealed envelope: nobody can read it on the way, but the company opens it on arrival.
- At rest is the company putting your list in its own safe. Burglars cannot read it; the company, which has the safe key, can.
- End-to-end is you locking the list in a box before posting it, and keeping the only key. The company stores a box it cannot open.
The four terms
Encryption in transit (TLS, the padlock in your browser) protects data between your device and the server. Practically every app has it.
Encryption at rest protects data on the provider’s disks. The provider holds the key and decrypts your tasks whenever it serves them, so at rest protects against a stolen drive, not against the provider. Todoist, TickTick and Notion all describe this model.
End-to-end encryption means data is encrypted on your device and only decrypted on your devices. The server stores ciphertext and never has the key.
Zero-knowledge is a marketing term for services whose servers cannot see your data. It usually describes end-to-end encryption, but it is looser. Wikipedia notes that, unlike end-to-end encryption, it “does not imply any specific threat model or security notion”, and a USENIX Security 2026 paper found attacks on “zero-knowledge” password managers when the server itself is malicious. That is why we use “end-to-end encrypted” as the main term and “zero-knowledge” only as an explanation.
| Model | Network attacker | Stolen server disk | The provider | Legal request to provider |
|---|---|---|---|---|
| In transit only | Protected | Readable | Readable | Readable data |
| In transit + at rest | Protected | Protected | Readable | Readable data |
| End-to-end | Protected | Protected | Protected | Ciphertext only |
Why it matters for a to-do list
Tasks are short, but they reveal a lot: “Call oncologist re: results”, “Invoice ACME for the layoffs project”, “Find a divorce lawyer”. A list shows your clients, your health, your money and your routine. With at-rest encryption, all of that is readable by the provider, its support staff and anyone who gets access through the provider.
How Kodimu does it
Kodimu, the app we build, uses end-to-end encryption that is always on. Your encryption password — separate from your login password — is stretched with PBKDF2-SHA-256 (600,000 iterations) into a key that wraps a random AES-256-GCM data key. Task text, project names and notes, ideas and pause comments are encrypted in your browser with that data key before upload. The server stores the wrapped key and ciphertext, never your password or the unwrapped key. The full design is in the security whitepaper.
Limitations
End-to-end encryption is not magic. Its limits apply to Kodimu as much as to anyone:
- Metadata stays visible. In Kodimu, due dates, priorities, stages, timestamps, focus timings and your email are not encrypted. The server can see that you finished a task at 9:40, not what the task said.
- Losing the password means losing the data. The provider cannot reset what it cannot read. In Kodimu, a downloadable recovery key is your only backup.
- Browser crypto trusts the code you load. A web app downloads its code on each visit, so a compromised server could ship code that leaks keys. Open-source clients, reproducible builds and independent audits reduce that risk; Kodimu’s client is closed source and not audited yet, so on this point you are trusting us.
- Your device matters. After you unlock, Kodimu keeps the data key in the browser’s local storage, and it stays there after you log out. Anyone with access to that browser profile could read it.
FAQ
- What is the difference between encryption at rest and end-to-end encryption?
- With encryption at rest, the provider encrypts data on its servers and keeps the key, so it can still read your data. With end-to-end encryption, data is encrypted on your device and the provider never has the key.
- What does zero-knowledge encryption mean?
- It describes a service whose servers cannot see your data, usually because of end-to-end encryption. The term is less precise than “end-to-end encrypted” and does not imply a specific threat model.
- Is AES-256 at rest the same as end-to-end encryption?
- No. AES-256 is an algorithm; it can be used in either model. What matters is whether the provider or only you holds the key.
- Does end-to-end encryption hide everything?
- No. Metadata such as timestamps, due dates and your email address is often unencrypted, so the provider can see patterns of use even if it cannot read content.
Sources
- Wikipedia — Zero-knowledge service — read 2026-10-21
- USENIX Security 2026 — Scarlata et al. (attacks on zero-knowledge password managers) — read 2026-10-21
- Todoist — Security — read 2026-10-21
- TickTick — Security — read 2026-10-21
- Notion — Security — read 2026-10-21
- Standard Notes — What is end-to-end encryption? — read 2026-10-21
- Splunk — Encryption explained: at rest, in transit and end-to-end — read 2026-10-21