Deletion combines identity, retention and session revocation. One user must not be able to delete another's account.
Evaluation approach
Verify the request appropriately and explain immediate deletion and justified retention. Check current platform requirements separately.
Application example
Deleted-account tokens must not initiate new API operations. Review local caches and notification registrations too.
Limits and considerations
Hiding the account screen does not delete server data or authority.
Work still running during deletion
Reassess transfers, notifications and open connections that may continue. Test that old keys cannot create new data for a deleted account.
Checks and decisions
- Verify requests
- Revoke sessions
- Explain retained records
Sources
The primary references above provide the technical basis. Example workflows and evaluation suggestions are this publication’s explanations, not independent test results for a particular product.