Know where your events go.

Captured events

Openhook stores incoming bodies, headers (excluding browser Cookie headers), sender addresses, timestamps, and notes in its database on its hosting server. Free inboxes expire within seven days; periodic cleanup deletes expired inboxes and their events. Each free inbox accepts up to 1000 retained events. Hosted Pro, when available, retains individual events for 30 days and applies the account limits shown on the pricing page. Persistent inboxes expire 30 days after their last paid-through date. At capacity, new events receive an error; accepted events are not silently evicted.

Activity history

Openhook records accepted event receipts and state changes, including notes, response configuration, token rotation, provider subscriptions, deletion, and expiry. Records contain timestamps, inbox and event identifiers, action names, transport types, and limited metadata such as body sizes and hashes.

This minimal history remains after an inbox or payload is deleted or expires. It does not retain payload bodies, notes, provider credentials, private tokens, or signing secrets. A live inbox history is readable with its private token. Historical records remain in server storage for operational review.

On your device

Your theme preference, inbox bookmarks, and private management tokens are saved in browser local storage. Bookmarks are not synchronized. Hosted account owners can recover access on another device without synchronizing private tokens. Removing a bookmark leaves the inbox and its server events intact.

Private tokens

Anyone with an inbox management token can inspect or delete its events. Public capture addresses only accept events. The server stores hashes of management tokens. Provider API credentials are used only during registration and removal calls and are not saved. Optional signing secrets are stored with inbox settings to verify incoming webhook signatures. You can rotate tokens or permanently delete inboxes through MCP.

Optional hosted accounts and billing

Hosted accounts store your GitHub numeric identity and login name, hashed sessions and agent keys, inbox ownership, usage counts, and billing identifiers. GitHub sign-in tokens are discarded after reading your identity. Essential HTTP-only cookies hold browser sessions and temporary sign-in state. Polar processes checkout and billing details; Openhook stores customer and subscription identifiers and paid-order records, not card details. Financial records and minimal activity history may remain after payload deletion. Hosted account availability is shown on the pricing page.

Website analytics

Public pages use our self-hosted Umami analytics to measure visits, referring sites, browser/device categories, approximate countries and selected button clicks. Umami uses no analytics cookies. We strip URL queries, fragments and referrer paths and do not send account identities, inbox tokens or event content. Do Not Track and Global Privacy Control are respected. Analytics scripts do not load on account or inbox screens. The analytics server receives your IP address to process the request; page analytics are separate from captured webhook data.

Operational data

We measure aggregate request counts, errors, latency, tool usage, capture volume and storage capacity. Operational metrics contain no payloads, tokens, IP addresses or account identifiers. Marked test captures are counted separately; unmarked captures are not necessarily real customer activity. HTTP rate-limit counters are held in memory. Application HTTP access logging is disabled; hosting and network providers may maintain operational logs.