AnnounceKit

Overview

AnnounceKit is a product changelog and in-app notification widget used by SaaS companies to communicate new features, updates, and announcements to their users. The widget embeds directly within a web application's interface, typically as a badge on a navigation item or help button, and expands to show a feed of recent product updates. Website operators use AnnounceKit to reduce churn by keeping users informed about improvements.

What This Script Does

AnnounceKit loads a JavaScript widget from its CDN (cdn.announcekit.app) that renders the changelog feed within the host application's interface. The script tracks which announcements each user has viewed, using a combination of a local storage entry or cookie to persist read/unread state across sessions. This tracking serves the functional purpose of showing an unread badge count and marking items as seen. AnnounceKit's scripts also send engagement metrics back to AnnounceKit's servers — recording which announcements were opened, how long they were viewed, and whether users clicked through to linked resources. If the host application passes user identification data (such as a user ID or email) to the AnnounceKit widget through its initialization API, AnnounceKit can associate engagement metrics with specific users, enabling per-user analytics in the AnnounceKit dashboard. Without explicit user identification, tracking is based on anonymous device-level identifiers.

Consent & Compliance

AnnounceKit's consent classification depends on implementation depth. At its most basic — persisting read/unread state locally — it functions as a purely functional widget that serves the user's own experience. When engagement metrics are reported back to AnnounceKit's servers, particularly when linked to identified users, it crosses into analytics territory. Under GDPR and the ePrivacy Directive, the local storage or cookie used to persist read state may qualify as a functional cookie if its sole purpose is to serve the user's experience (remembering what they've seen). The reporting of engagement metrics to a third-party server requires either a legitimate interests assessment or consent. Under CCPA/CPRA, engagement data associated with identified users constitutes personal information. AnnounceKit is typically hosted in the EU or with EU data handling options; operators should verify their account's data residency settings. Consent category: functional.

Should You Block This Without Consent?

Conditional. If AnnounceKit is implemented with only anonymous read-state persistence (no user identification passed to the widget), it can be treated as functional and loaded without explicit consent. If user identifiers are passed and engagement is tracked at the individual level, analytics consent should be obtained. Operators should review what data their AnnounceKit initialization code transmits.