PrivacyUpdated 22 September 2026
What we hold, and the large thing we do not.
Most of this policy is ordinary. One part is not, and it is the reason the product exists: we never run a language model, so the prompts your agent sends and the reasoning it does never arrive here. There is nowhere in this system to put them.
Written by the person who built this, from what the code does, and not reviewed by a lawyer. It is accurate rather than authoritative: if you need a policy your own counsel has read, this is not yet that document, and saying so is better than implying otherwise.
What never reaches us
Your prompts, your agent's conversation, and your model provider key. The agent runs on your machine and talks to your provider directly; what arrives here is the result it chose to write down, over MCP, as structured records. This is a property of the architecture rather than a promise about our conduct, which is the only kind of privacy claim worth reading. The exception is hosted mode, where you deliberately give us a provider key so the agent loop can run here; if you have not done that, it does not apply to you.
What we do hold
Your email address, and the workspace you fill: the people and organisations you research, the sources and dates behind each claim, your own profile, your drafts and their earlier versions, files you upload, and a log of what changed and when. Your password is held by Supabase Auth and never reaches our code. Agent credentials are stored as a hash plus the first few characters, so a token cannot be read back out of the database, only checked against.
Notifications, only if you set them up
Turning on email digests stores an address. Turning on browser push stores the subscription your browser issues, which is a URL at your browser vendor plus two keys. Connecting Telegram stores a chat id. Subscribing a calendar creates a feed token, which is a bearer token: anyone holding that URL can read those dates without signing in, which is how calendar subscriptions work everywhere. Revoke it from settings and the old URL stops answering.
Who else touches it
Supabase holds the database, the accounts and the uploaded files, in their eu-west-1 region. A hosting provider runs the application. If you configure email, your SMTP provider carries those messages; if you connect Telegram, Telegram does. Browser push goes through your browser vendor's service. That is the complete list, and it is short because there is nothing else in it.
No analytics, no tracking, no advertising
There is no analytics script on this site or in the application, no third-party tag, no advertising network and no session recorder. This is checkable rather than asserted: open the network tab and count the hosts. We have never sold or shared workspace data, and the business model has no version where that would help.
Getting it back, and getting rid of it
Ask and we will export your workspace, or delete it. Deleting a workspace removes its rows and its files rather than flagging them hidden. Some things survive in backups for a short period, because a backup you can edit is not a backup.