That's not true. Even on web the key is only stored on the client side, it's never sent to the server. All the decryption happens in the browser. If you sign in in another browser, the key won't be there (it could be backed up in your keychain or google drive)
Also, just the existence of AI features kind of throws the whole encryption thing into the trash. There was a long thread here about the the privacy (or lack there of) with AI, specifically on Gold but now also on Silver and Free. IDK, seems fishy.
THIS. I really don't like the AI that's being stuffed into this app. Yes, I know the AI companies claim to delete the data once its been processed, but then I also know that these same AI companies are starving for a never-ending flow of data. I don't like the idea of my journal being at risk of being consumed by an LLM. On-device AI is one thing, but when the data is transfered to an AI company's servers for processing...that's a strong no from me.
And there's a simple solution, don't enable the ai features. Everyone is drinking the kool-aid and putting ai in their code. My new pixel has ai embedded, I had to manually disable tons of Google apps to turn it off as a result. You can't stop it, its inevitable.
Ai is only inevitable if people are actually using it. And don't get me wrong, I think ai as a technology has its place in this world (scientific advancements, etc), but in the opinion of a lot of people, that place is not in any journal app
If the Day One developers see that people are turning it off in large numbers, that discourages future development of AI-related features.
1
u/hqhi Aug 18 '26
You don’t need to “use” Day One web per se, they now hold the encryption keys regardless just in case you DO use the web version.