Privacy
Where your decisions actually go
Short version: they stay in your browser. There is no account, no database, and no copy of your decisions on any server we run. Here is the long version, including the parts that are less flattering.
What stays on your device
Everything you type, every analysis you run, and every entry in your journal is stored in your browser's localStorage. It never gets written to a server we control, because there is no server-side database in this product at all.
Clearing your browser data deletes all of it permanently. There is no backup and no way for us to restore it, because we never had a copy. If you want one, use Export JSON on the journal page.
What leaves your device, and where it goes
Running an analysis sends the text you wrote to OpenAI, which is the model provider behind it. There is no way to produce an analysis without doing this. What you send is subject to OpenAI's API data policies, and at the time of writing they do not train on data submitted through the API.
Some decisions also trigger a web search step, run through the same OpenAI API, to ground the analysis in current information. When that happens the results page says so.
Nothing else you type is transmitted anywhere. We do not send it to ourselves, and there is no endpoint that would receive it if we tried.
Shared links
When you share an analysis, the entire analysis is encoded into the link itself, after the #. Browsers never send that part of a URL to a server, so the content of a shared link is not stored anywhere and does not reach us.
That also means anyone holding the link can read it, and you cannot revoke it once it is out. Treat a shared link like a document you emailed: it exists now, wherever it was sent.
On-device protection, described honestly
Journal and memory contents are obfuscated before being written to localStorage, using a key generated per browser. This means the contents are not sitting in plain readable English in developer tools, in a profile backup, or in whatever a browser extension happens to read.
This is not encryption.The key is stored in the same browser as the data it scrambles, so anyone who can run code on this site, or who has access to your browser profile, can reverse it. Real encryption would require a passphrase you type every session, and that is not what this product does. We are telling you this rather than calling it "encrypted" and letting you assume more than is true.
If you are working through something you would not want anyone with access to your computer to read, use a private window and close it when you are done.
Analytics
The site runs Vercel Analytics and Vercel Speed Insights. These record which pages get visited and how fast they load. They do not use cookies, do not build a profile of you across sites, and never see the text of your decisions.
There is no other tracking. No advertising pixels, no session recording, no third-party scripts.
Accounts and email
There are none. You cannot sign up, and there is no mailing list, because there is nowhere to store an address.
Questions
If something here is unclear or looks wrong, get in touch.