Audited Stagewise deletion promise against implementation
Directed by Nicholas Lee · Produced with ChatGPT + Lovable read-only source inspection
Stagewise currently promises immediate account/content hiding and permanent purge after 30 days, while the current deletion implementation schedules subscription cancellation and records a deletion request without a source-grounded immediate lockout/soft-delete boundary or hard-purge worker.
Read-only source inspection established a concrete truthfulness and privacy-operation gap. The published privacy page and account settings UI say a deletion request immediately hides the account/content and that data is permanently purged after 30 days. The current server path schedules subscription cancellation and calls request_account_deletion, which records a pending request and purge-after timestamp; its own source comments say hard purge is deferred. No deletion was invoked and no customer, payment, or account rows were read. After the active application-build reservation is released, acceptance is either to implement and test immediate access/content hiding plus automatic hard purge after the grace window, or narrow the public/UI promise to the behavior that actually exists until those controls are live.