Explicit browser consent
The site asks for browser notification permission only after you press the enable button. Recommendations from another connected gaming site are a separate preference and are disabled by default.
Data stored for delivery
The system stores the browser push endpoint and its encryption keys in encrypted application fields. It also stores your selected projects, topics, frequency, quiet hours, locale, and timezone offset. User-agent text is not retained; only a one-way hash is used for abuse and reliability diagnostics.
Analytics definitions
Accepted means the browser push service accepted the request. Received means the service worker processed it. Shown means the browser accepted the display request. Clicked and closed are recorded from the notification interaction. These stages are reported separately because “sent” does not prove that a person received or saw a message.
Retention and minimization
The application does not currently run automatic age-based cleanup for notification records. Unsubscribing stops future delivery but does not delete the stored subscription record. Expired and unsubscribed subscription records, campaign records, delivery records, and interaction events remain stored until an approved retention process is in place. No fixed retention period is currently configured. Analytics screens do not display raw push endpoints or encryption keys.
The retention period and deletion process are awaiting publication review. This page describes current application behavior and is not a substitute for a reviewed privacy policy.
Your control
You can change sites, topics, frequency, quiet hours, and cross-site recommendations from the notification center. Disabling marks the server-side subscription inactive and asks the browser to unsubscribe; it does not erase the stored record.