"Delete my account" should mean delete.
We pressed the real delete button, and watched what actually happened. It deleted less than it said.
If an app has a button that says delete your account, it should delete your account. Apple requires one, and so does basic decency. We had one. On August 14th we tested it properly, by pressing it through the real code path and watching what left the building, and found that it didn't do everything it said.
What it missed
The button cleared your account from the main database. But your uploaded files, meaning PDFs, photos, and thumbnails, were still sitting in storage, because the cloud storage was never told to delete them. Nine tables of per-account records were also left with rows behind.
And then it kept turning things up
Once we started looking, the same button had more problems:
- If a deletion failed partway through, it still reported success.
- The account's activity record survived a deletion that had finished.
- If you had signed in with Apple, the app never told Apple to cancel that connection. This was the last one, found on August 22nd.
Why this one is hard to catch
The button worked. It did something, it returned success, and nothing crashed. The only way to know it was incomplete was to press it and check what was still there afterward. Reading the code several times in a row didn't catch the missing Apple call. Running it did.
All of these are fixed in our code. I'm going to stay careful about the claim, though: I won't tell you deletion erases literally everything, everywhere, forever. Backups and other systems have their own schedules. What I can say is that we found these gaps ourselves, fixed them, and now test the real button.
Written October 21, 2026 from the build log, and dated to when this happened.