The Waffle website (waffle.baby) uses PostHog to understand which parts of the page people see and whether they click the download button. This data is anonymous and aggregated. No cookies are used for tracking individual visitors.
Waffle.app includes optional, opt-in usage analytics powered by PostHog. When you first launch Waffle, you are asked whether you'd like to share anonymous usage data. If you decline, no analytics data is ever sent. You can change this at any time in Preferences.
If you opt in, we collect anonymous events like session count and feature usage. We do not collect terminal content, commands, file paths, or any personal data.
Hardly anyone opts into the analytics above — totally fair — but we need a rough sense of how Waffle is doing to make it better. So two small pieces of anonymous data are sent automatically: one for crashes, one to know how many people are using it.
Waffle uses Sentry to collect crash reports and count active users. Sentry receives an anonymous, randomly generated identifier, crash data (stack traces, device info), and a session heartbeat. It does not include terminal content, commands, or personal data.
On launch, Waffle also pings a Cloudflare Worker with an anonymous ID (a random UUID stored in ~/.waffle/install_id), the app version, and your macOS version. The ping fires every time you launch the app; the server only stores one row per install per day. No terminal content, no commands, no personal data.
We do not sell, share, or transfer your data to any third party. PostHog processes analytics data on our behalf under their privacy policy. Sentry processes crash reports on our behalf under their privacy policy. Cloudflare hosts the launch-ping Worker and database on our behalf under their privacy policy.
Questions? Reach out on Twitter/X (@ollee).
Last updated: May 2026