Encrypt locally
Titles, descriptions, dates, tags, notes, and other task content are encrypted on-device before the data is sent upstream.
Feature
Encrypt on your device first, so the server is no longer the place trust has to begin.
TapTidy Pro turns task content into ciphertext before it leaves your device. That changes the privacy model from "please trust our servers" to a harder technical boundary.
End-to-end encryption is part of TapTidy Pro.
Store ciphertext
The hosted service stores encrypted payloads and sync metadata, not readable task bodies. That sharply narrows what the server can inspect.
Decrypt on authorized devices
When your data reaches another approved device, it is decrypted there rather than rehydrated as plaintext on the server in the middle.
What changes
The main value is not the algorithm name. It is the boundary the model creates.
End-to-end encryption matters because it changes what has to be trusted operationally. It does not eliminate every security concern, but it does remove routine server-side visibility into task contents.
What TapTidy can still know
- Your account identity and subscription state
- Device registration and sync timing
- Operational metadata needed to run the service
What it cannot read under E2EE
- Task titles and descriptions
- Task notes and shared private payloads
- Due-date content, tags, and other task fields carried inside the encrypted payload
Plan fit
Where the stronger privacy posture begins.
The Free tier gives you the standard hosted experience. Pro is where the stronger task-content boundary starts.
| Capability | Free | Pro |
|---|---|---|
| End-to-end task encryption | Not included | Included |
| Private share with encrypted payloads | Not included | Included |
| Zero-telemetry defaults | Standard controls | Enabled by default |
Encryption FAQ
The questions that matter after the headline claim.
Most skepticism here is healthy. These are the practical boundaries people usually want explained in plain language.
TapTidy Pro includes end-to-end encryption for task content so it is encrypted on-device before upload.
TapTidy uses AES-256-GCM for task encryption in the current product messaging and implementation model.
No. TapTidy does not use your task content to train machine-learning models.
If the server does not need to read your tasks, it should not be the default place they stay readable.
TapTidy Pro is built for people who want that boundary to be stronger than a policy statement.
See Pro privacy features Security page covers the broader model around storage, telemetry, and trust boundaries.