Privacy and data

What the widget stores and sends, and what it doesn't.

The widget runs on your users' screens, so it collects as little as possible.

No cookies, no tracking

The widget sets no cookies and doesn't fingerprint visitors. It keeps a few values in the browser's local storage, under keys that start with whatsnew::

Key What it holds
whatsnew:visitor A random id, such as v_3f9a…, that identifies nobody
whatsnew:seen:pk_… When the visitor last opened the panel, to compute the unread badge
whatsnew:reactions:pk_… Which reactions this browser already gave, to show them as pressed

If local storage is blocked, the widget keeps these in memory for the page instead.

What it sends

  • Your feed is fetched from our CDN. The request carries no cookies or credentials.
  • Usage counts: when the panel opens, when an update has been viewed and when its link is followed. Our edge server turns them into daily totals per project and update; the visitor id and IP address are never stored.
  • Reactions a visitor gives to an update, with the random visitor id so each browser counts once. IP addresses are only used briefly to limit abuse, never stored.

Where it runs

The widget's script and your feed are served from Cloudflare's network. Your dashboard data is stored in our database. Your updates are public once published; everything else is private to your organization.