I'm not very convinced to be honest.
Discussion
We're doing our best to deliver on our promises. Bugs happen. If you want to use us without an account you are free to do so. Or you are also free to use another service if you no longer trust us. We make mistakes. Period.
We are also ideating on a lot of other ways we can provably deliver ultimate privacy such as storing user chats encrypted on nostr relays or other some such ideas, but those are steeper engineering challenges that will take time.
If you have any other ideas on how we can architect things better we are all ears.
To further explain what we think happened... We believe there was a bug such that when a user returned to PPQ after a previous session, it appeared to the user that they were logged in, but in actuality their login token expired. However, because we store user convos both client and server side, the user was still seeing the client side version of their chats as if nothing was wrong. Then, if that user deleted a particular chat, it successfully deleted it client side, but because they were not logged in anymore, the delete action never made it to the server side and thats why it persisted thereafter.
So why did your old chat just spray onto your screen again in duplicate? When you logged in again, it tried to retrieve any chats on the server (which were not deleted because of the aforementioned issue) and when it did, a react hook fired too many times causing the duplication (another bug we've now hopefully fixed).
Hope this helps you understand the situation a bit more.