Audit my account deletion flow end to end. Look at how deletion is triggered, what gets deleted, and what happens to related data. Fix or implement: deletion requires the user to re-enter their password or confirm via a fresh email link (so a stolen session alone can't destroy an account); the delete endpoint verifies ownership server-side; deletion actually removes or anonymizes the user's data (profile, content, files in storage, personal fields in order records) rather than just flipping a flag while keeping everything; third-party data is handled (cancel subscriptions before deleting so billing stops; note anything that legally must be retained, like transaction records, and anonymize the personal parts); and the user gets a clear confirmation of what was deleted. Do not change retention where there's a genuine legal or billing reason to keep records; anonymize instead and tell me what was retained and why. Do not break referential integrity: decide explicitly what happens to the user's content (delete, anonymize to "deleted user") and apply it consistently. Give me a deletion map: each data type, where it lives, and what happens to it. Then a verification walkthrough: create a test account with content and files, delete it, and confirm each piece is gone or anonymized.