Website privacy and analytics
The public Hookway website and hosted builder offer optional analytics. Your self-hosted Hookway instance is separate and does not send these website events.
Updated October 31, 2026
Your choice comes first
Optional analytics stay off until you choose Allow. Decline keeps them off. We remember your preference in this browser’s local storage. You can change it at any time using Analytics preferences in the footer. Withdrawing permission stops collection and clears the website’s analytics persistence; it does not erase events already received.
What optional analytics collect
When enabled, PostHog receives page paths, a coarse page category, a referring website hostname, recognized campaign labels, and explicit actions such as opening the builder, copying the quick start, exporting a configuration, or opening GitHub. An anonymous browser identifier groups consented visits. We do not identify visitors by account or email.
We strip query strings and URL fragments from event URLs. We do not record sessions or automatically capture clicks, forms or exceptions. We do not send configurations, webhook bodies, API specifications, credentials, custom filenames or editor contents. An export action does not establish that a file was saved or Hookway was deployed.
Providers, storage and requests
The website serves its fonts locally. Vercel serves the website and may process network information, including IP addresses, in the course of hosting it. If you allow analytics, PostHog processes the permitted events and the network information required to receive them. The dedicated Hookway project uses PostHog Cloud’s free-plan event retention of one year. This limits queryable event history and is not a guarantee of deletion of all provider copies at that time. See PostHog’s event-retention documentation.
The hosted builder also stores your workspace locally in your browser so you can return to it. This is separate from optional analytics. Configuration validation and OpenAPI import normally run in the browser. If the browser validator is unavailable, the editor can try a validation endpoint on the same website origin with the submitted configuration. This is separate from PostHog. The self-hosted product has its own deployment settings.
For website privacy questions, use the project’s GitHub issues without posting personal or confidential information. Provider information: PostHog privacy, event retention and Vercel privacy.