Privacy & security · Updated November 4, 2026
Your list belongs to you.
Tao works on your Mac without an account. Optional accounts, sync and paid hosting are being prepared; public sign-in and payments are not available yet. This page distinguishes the app you can use today from those optional services.
On your Mac
Your tasks and projects live in a local SQLite database, with local backups. Capturing, editing and exporting your list work offline. Turning off sync leaves your local list in place. Deleting a cloud account does not delete copies on your Macs or their backups.
When you use your own model key, Tao sends the context needed for your request to your selected model service. That service has its own privacy and retention rules. Your model key is a device credential, not a task field uploaded by sync.
What an optional account stores
Sign in with Apple establishes your account. Tao does not request your name or email for this flow. The account service verifies Apple's identity token and keeps an account identifier derived from Apple's user identifier, a list of authorized devices, credential hashes, plan status and usage counters. Sign-in tokens are not kept as task data.
If you enable sync, the service stores your synced tasks, projects, comments, settings and change history. Paid hosting can also store attachments and the context and results of jobs you explicitly hand to Tao. Free sync never starts paid AI work while your Mac sleeps.
Your account has its own boundary
Each account's sync data and hosted jobs have private storage. The server selects that storage from your authenticated credential. Putting someone else's account ID in a request cannot select their data. Device revocation disables that device's credential and closes its subscriptions; it cannot erase data the device already downloaded.
Connections use TLS. The account service encrypts task content, attachments, hosted-job state and saved Workflow results before storing them, using separate account keys protected by a server wrapping key. This protects a storage export or backup obtained without the server secrets. Account IDs, sizes, counters, device IDs, subscription references and action metadata remain visible to the service.
The limits of server encryption
There is no operator, support, debug or list-all endpoint for reading customers' tasks. Export and deletion require that account's own credential. The account service does not log task content or credentials.
Task data is not end-to-end encrypted. The running service can decrypt it. Someone who controls deployed server code, inspects running requests, or obtains both storage and server secrets could read it. Cloudflare runs the infrastructure and can process network metadata such as IP addresses and request timing.
End-to-end encryption would keep decryption keys only on your devices, removing that server capability. Hosted AI would then need a separate, explicit way for you to share the context it needs. Tao does not claim that protection today.
When you ask Tao to work in the cloud
Paid hosted AI uses the service's model credential, so you would not need your own key. Context necessary for a job goes to the configured model provider through OpenRouter; a job may read public web pages you supplied. Those providers process the requests under their own policies. Server encryption does not hide a request from the model that answers it.
Stripe Checkout is being wired in test mode only. It receives an account reference and the chosen subscription price, not task content. Payment details would be entered with Stripe. The current integration rejects live keys and live payment events; it cannot charge you real money.
Export, deletion and retention
Your Mac can export your local data. The account service also supports authenticated export of synced records and their versions, an attachment inventory and a separate hosted-job export. Export remains available if you downgrade or reach a storage limit.
Account deletion removes synced content, attachments, credentials and hosted-job state, destroys their wrapped encryption keys and prevents old devices from recreating the deleted account. A small deletion fence and a bounded log of privileged actions remain. That log contains times, device identifiers, fixed action names, counts and sizes, not task words. Sync change history and deletion markers otherwise remain for the account's lifetime so an offline device cannot resurrect deleted tasks.
Deletion is logical erasure. It is not a promise of instant physical removal from Cloudflare's recovery backups. Encrypted Workflow history can remain for its configured retention after the account's key is destroyed. External model requests and any payment records are also subject to those providers' retention rules.
This website
This site has no advertising trackers or third-party analytics scripts. The home page saves your theme choice in your browser. Download hosting necessarily receives ordinary connection information. Visiting the site does not upload your local tasks.