Automatic Deletion of Unread Notifications Without User Consent

ArcBlock’s notification system appears to automatically delete unread notifications without user interaction or explicit consent. This behavior occurs even when the user has not viewed or dismissed the notification, leading to potential loss of critical alerts (e.g., transaction confirmations, security updates, or service alerts).

Steps to Reproduce Receive a Notification: Trigger an event that generates a notification (e.g., a blockchain transaction, app update, or service alert). Do Not Interact: Leave the notification unopened and unacknowledged. Wait for Deletion: Observe that the notification is automatically deleted from the notification center or app interface within a short timeframe (e.g., minutes to hours). Verify Deletion: Check the notification history or logs to confirm it was removed without user action. Expected Behavior Notifications should remain in the user’s interface until explicitly dismissed or archived. Users should have full control over notification retention, with options to: View the notification. Mark as read. Delete manually. Automatic deletion should only occur after user interaction (e.g., "Clear All" or "Dismiss"). Actual Behavior Notifications are deleted automatically without user interaction. No warning, confirmation, or recovery options are provided. Users may miss critical alerts due to premature deletion. Impact User Experience: Frustration from missed notifications and lack of control. Privacy/Security: Users may miss alerts about sensitive actions (e.g., unauthorized transactions, account changes). Compliance Risks: Violates data retention principles in privacy frameworks (e.g., GDPR’s "right to access" and "right to be informed").