An attaché who talks is no use to anybody.
This is the full version of what happens to what you type. It is written to be read rather than to be survived, and it says what is not done as plainly as what is.
What is collected
- Your email address, if you create an account. It is used to sign you in and to send the reminders and briefings you ask for. Nothing else.
- What you put in the app: tasks, lists, tags, notes, due dates, and the standing orders you write. This is the service; there is no version of it that does not hold your work.
- How you sign in: a password hash if you set one (PBKDF2, never the password itself), or a passkey public key. Passkeys are registered with attestation set to "none", which means the identity of your fingerprint reader or security key is never collected.
- On this marketing page only, privacy-first analytics, and only after you press Accept on the banner. Choosing "Essential only" means nothing is ever sent.
- A diagnostic report, if you turn one on: what device you have, which version of the app and system it runs, and how it was doing at the time. Never your tasks, notes, or email address. Off until you switch it on, and set out in full in the next section.
The app itself carries no analytics library, no advertising pixel and no session-replay recorder. That is a property of the code, not a promise about intent: there is nothing of that kind in it to switch on.
Diagnostic reports
When the app breaks, everything useful about why is on your device, where we cannot see it. A diagnostic report is how a crash gets fixed without you having to notice it, describe it, or write to us at all.
On the App Store version, this is off until you turn it on, in Settings under Diagnostics. Test builds installed through TestFlight always send one, because reporting problems is the whole purpose of a test build.
A report holds:
- Which device model and system version, and which version and build of the app.
- How the device was doing: free memory and disk space, whether it was overheating or in Low Power Mode, how long it had been awake, and your language and region setting.
- The identifier Apple gives this app for your device. It is not your Apple Account, it is not shared with other companies' apps, and deleting the app resets it.
- If the app crashed: the technical name of the failure and the list of function names it happened inside.
- A short trail of plain event labels, such as the app starting, the system warning it was low on memory, or a voice capture beginning.
What a report never holds: your tasks, notes, lists, tags, due dates, standing orders, email address, password, or passkey, and nothing you have typed or dictated. The event labels are chosen from a fixed list written into the app rather than generated from what is on screen, so a report has no way to pick up your content even by mistake.
Reports go to our own server and nowhere else. They are not sold, not shared, and not used to build a profile of you or to advertise anything.
What leaves for a model provider, and when
The AI features are the only thing that sends your content anywhere. When you use one, the task text that feature is working on is sent server-side to:
- Anthropic's API for the chat, Debrief proposals, briefings, the weekly review, goal decomposition and Smart Add's harder parsing.
- OpenAI's API for turning a voice recording into text, when you capture by talking.
Both are used through their business API terms rather than their consumer products. Your list, your reminders and your data never require a model: if you never touch an AI feature, nothing of yours is sent to one. Your email address is not sent with the content.
What is never done
- Your task content is never sold, rented, or handed to an advertiser.
- No advertising network, data broker, or tracking pixel is present in the app.
- The app never sends a message on your behalf. Outbound-communication tasks carry a draft you copy and send yourself, deliberately.
- A share link never carries more than the single thing it was made for. Dead Drop links and one-tap reminder actions each carry a signature over exactly one item and one action, and a tenancy test with a working positive control runs before every release.
The sandbox
The no-account sandbox mints a throwaway account whose address is at an unroutable domain, so nothing in the system can email a sandbox owner even by mistake. Sandboxes are disposable by design and are reaped. If you later sign in with a real address from that same session, the work you did is carried into your real account, once, and never between two real accounts.
Getting your data out, and getting rid of it
There is no one-click export yet. That is a real gap rather than a policy, and a data-export surface is the next thing being built. Until it lands, the free Model Context Protocol server can read everything in your account programmatically, which is a working if technical way out.
Deletion is by request and is done by hand. There is no self-serve delete button yet, so either route below works and both reach a person. Enter the address on your account and everything held for it goes. No retention argument will be made at you. A delete button is on the build list, and this paragraph will change when it lands.
By email: privacy@agentattache.com, from the address on the account. Or use the form, which needs no mail client:
Where it is kept, and children
The service runs on Cloudflare's platform, with the database and files stored there. Backups exist so an accident is recoverable.
Task Attaché is not directed at children under 13 and accounts are not knowingly created for them.
When this changes
The date at the top moves whenever this page does. A change that materially widens what is collected or where it goes will be announced to account holders by email before it takes effect, not discovered afterwards.