AES-256 end-to-end
Same encryption standard used for classified government data and online banking. Tasks are encrypted on your device before any data leaves it.
Most "encrypted" todo apps use server-side encryption: the company holds the keys and can decrypt your data when convenient. Zero-Friction Tasks uses true end-to-end encryption. The encryption key never leaves your devices.
AMBER-DELTA-7734. It never goes to the server.Same encryption standard used for classified government data and online banking. Tasks are encrypted on your device before any data leaves it.
Zero-knowledge architecture: the encryption key is derived from your sync code, which never leaves your devices. The server only sees ciphertext.
No key escrow. No "we can reset your password" — because there is no password. If you lose the sync code AND every device, even we cannot recover the data.
Both directions of the wire are encrypted. The Supabase row holding your task is encrypted ciphertext, not a TLS-protected plaintext blob.
Task text, list names, pin status, custom organization data — everything is encrypted. Only routing metadata (e.g. which sync code a blob belongs to) is plaintext.
The encryption layer is a documented surface in the open REST API at /api/v1/docs. You can verify the model by reading the spec — not just trust a marketing claim.
| App | Encryption model | Can the operator read your tasks? |
|---|---|---|
| Zero-Friction Tasks | AES-256 end-to-end, zero-knowledge | No — physically cannot |
| Todoist | Server-side encryption (in transit + at rest) | Yes — operator holds keys |
| Microsoft To Do | Server-side encryption | Yes — operator holds keys |
| Notion (tasks DB) | Server-side encryption | Yes — operator holds keys |
| Apple Reminders | iCloud encryption (E2E with Advanced Data Protection) | Optional E2E (Advanced Data Protection) |
| Lunatask | End-to-end encryption | No |
Apple Reminders is end-to-end only with Advanced Data Protection enabled and works only across Apple devices. Lunatask is paid and macOS/iOS-focused. Zero-Friction Tasks is free, cross-platform, and end-to-end on every platform by default.
The sync code is the encryption key. If you lose it and have no remaining device with the app installed, the encrypted data on the server cannot be recovered — by design. Save the sync code in a password manager (1Password, Bitwarden) when you generate it.
We can be compelled to hand over data we hold. The data we hold is encrypted ciphertext. We do not hold the key, so we cannot produce readable content. This is the standard guarantee of zero-knowledge architecture.
Accounts create identity. Identity creates attack surface — phishing, password reset hijacks, OAuth token leaks. Removing the account removes the entire account-takeover threat class. The sync code is the only credential, and it stays on devices you control.
No measurable difference. AES-256 is a hardware-accelerated instruction on every modern CPU and mobile SoC. Encrypting a task takes microseconds.
Yes. Offline Mode disables cloud sync completely. Tasks stay only on the device they were created on. Use this when you want maximum isolation.
Open the Web App — generates a sync code, encrypts the first task, takes about 5 seconds. No signup, free forever.
Open Web AppOr read the full data-protection technical details.