Legal
Subprocessors
The providers HookWatch relies on to operate the service.
Last updated: 6 July 2026
What subprocessors are
A subprocessor is a third party that processes data on our behalf to help us run HookWatch — for example, a hosting provider. We list them here for transparency.
Self-managed infrastructure
HookWatch runs on self-managed infrastructure hosted with Hetzner. The list below reflects the
providers currently in use. Optional Trackdock analytics is loaded only after a visitor opts in;
see the Cookie Policy for the data involved.Current subprocessors
| Provider | Purpose | Location | Data processed | Status |
|---|---|---|---|---|
| Hetzner | Cloud hosting — runs the HookWatch application, API, and worker | Germany (EU) | All service data, in transit and at rest | In use |
| PostgreSQL (self-hosted on Hetzner) | Primary database for accounts, endpoints, and deliveries | Germany (EU) | Account, workspace, and webhook delivery data | In use |
| Google (Google Workspace) | Email hosting for the support/contact addresses | Global (US / EU) | Contents of emails you send us | In use |
| Trackdock (track.rundock.dev) | Optional product and marketing analytics, loaded only after visitor consent | Not yet confirmed | Analytics data: page URL, referrer, device/viewport, engagement, clicks, and opted-in events | In use — opt-in only |
Planned / future subprocessors
The following provider will be introduced as the product develops. It is not in use today, and this page will be updated before it processes your data.
| Provider | Purpose |
|---|---|
| Paddle | Payments / merchant of record — when paid plans launch |
Updates
We will update this list when we add, remove, or confirm a subprocessor, and reflect the change in the “Last updated” date above.
Contact
Questions about our subprocessors: privacy@hookwatch.dev. See also Legal Contact.