1. Operator
WebhookKit is operated by:
Dariusz Zbyrad
Email: [email protected]
2. The Service
WebhookKit is a tool for creating temporary webhook endpoints and inspecting HTTP requests sent to them.
Anonymous and Developer are currently provided free of charge. Pro is a planned paid subscription and cannot yet be purchased.
You can use WebhookKit anonymously or create an account by signing in with Google or GitHub. After correction activation, the active endpoint limits are 1 per anonymous session and 5 per signed-in account. Existing excess endpoints and expiry dates are preserved; active owned endpoints can still be renewed. Before activation the selected policy remains in effect; see Usage limits. On sign-in, eligible active endpoints from your anonymous browser session are linked to your account up to the available account limit; any remaining endpoints stay anonymous.
Webhook endpoints are temporary and expire after the period indicated by the service. Guest endpoints start with 24 hours; after plan-policy activation, new account-owned endpoints start with 7 days. Existing endpoints keep their original expiry.
Signing in does not extend endpoint lifetime. A signed-in owner can explicitly extend an active, unexpired endpoint without changing its receiving URL; see the current extension window in Usage limits. Extensions do not accumulate days and do not change request retention. Expiry stops ingestion and access but does not immediately delete the endpoint record or captured requests.
WebhookKit is not intended to be used as permanent data storage. Planned Pro endpoints are intended to remain active for the duration of an active Pro subscription, subject to security, abuse-prevention, legal and service availability provisions.
3. Technical Requirements
To use WebhookKit you need:
- an internet connection;
- a current web browser to use the web interface; and
- an HTTP-capable application or service if you want to send requests to a webhook endpoint.
4. Your Responsibilities
You are responsible for how you use WebhookKit and for the data sent to your webhook endpoints.
You must:
- have the right to send and process any data submitted to WebhookKit;
- comply with applicable laws;
- protect your Google or GitHub account, signed-in sessions, endpoint management credentials and other access tokens provided to you;
- avoid intentionally submitting confidential information, credentials or other sensitive data unless this is necessary and you are authorized to do so.
You must not use WebhookKit to:
- submit, store or transmit unlawful content;
- violate the rights of others;
- attack, disrupt, overload or interfere with WebhookKit or other systems;
- bypass security, rate limits or abuse-prevention mechanisms;
- distribute malware or conduct other malicious activity.
5. Webhook Data
WebhookKit may capture the contents of HTTP requests sent to webhook endpoints, including request bodies, headers, query parameters and technical metadata.
This may include Authorization or Cookie headers, API keys and signatures. WebhookKit does not automatically remove secrets or personal data from these requests. You are responsible for ensuring that you are legally permitted to send such information to WebhookKit.
Deleting captured requests removes all their records from the active database, including previously hidden requests, while leaving the endpoint active. Deleting an endpoint disables its address and deletes its captured requests from the active database. Existing backups are separate. After correction activation, new admissions retain captures for 24 hours on Anonymous and 7 days on Developer, including on existing endpoints. Earlier admissions keep their original 30-day deadline. This is not a guarantee of access for the full retention period; endpoint expiry, lost access, count eviction or deletion can end it earlier. Cleanup normally runs hourly and can be delayed. After plan-policy activation, new endpoints keep only their newest 50 guest / 500 account requests, and earlier records may be deleted on capture. Older endpoints remain uncapped by count, including after claim. Daily incoming quotas count admitted arrivals before body read, including oversized bodies, disconnects and later failures; clearing history or deleting endpoints does not reset them. See Usage limits for current scope and UTC reset rules.
Do not treat a WebhookKit endpoint as a secure location for long-term storage of secrets or confidential information.
6. Availability and Data Loss
WebhookKit is provided on an as available basis.
We do not guarantee that the service will be uninterrupted, error-free or permanently available.
Temporary endpoints, captured requests or other data may become unavailable or be deleted.
You should not rely on WebhookKit as the only copy of information that you need to retain.
7. Security and Abuse Prevention
We may limit, suspend or block access to WebhookKit where reasonably necessary to:
- protect the service or its users;
- prevent abuse or attacks;
- enforce these Terms; or
- comply with legal obligations.
Request-size and traffic limits also apply. Automated security mechanisms may require additional verification or temporarily prevent creation of endpoints.
8. Ending Your Use of the Service
You may stop using WebhookKit at any time.
For anonymous use, no separate cancellation procedure is required.
You can delete your account in Account → Security by confirming your email address. This deletes your profile and sign-in provider association from the active application database, signs out all devices and disables your endpoints. Captured requests remain without an account association until their original assigned capture deadline (24 hours or 7 days under the corrected policy; 30 days for earlier admissions), as described in the Privacy Policy. Claim, renewal and deletion never reset capture deadlines. Their contents are not anonymized. Previously created backups are separate from the active database. Signing in again does not restore the deleted account’s endpoints or requests. This does not delete your Google or GitHub account or remove permissions in that provider’s account settings.
We may discontinue or change the free service or individual features. Where reasonably possible, material changes affecting normal use will be communicated through the service.
8A. Future Pro subscriptions
When launched, Pro is intended to cost $5 USD per month, charged in advance as a monthly recurring subscription with automatic renewal and no free trial. It is intended for individuals and businesses internationally, subject to availability. Pro limits and features shown on Pricing are planned; they are not current entitlements.
You will be able to cancel at any time. Cancellation prevents future renewals; Pro access normally continues until the end of the paid billing period. Cancellation alone is not a refund request. When the paid period ends, the account returns to Developer Free and remains available for creating new endpoints within Developer Free limits. Existing Pro endpoints will be deactivated and removed from the active workspace, rather than carried over as active free endpoints. Associated captures will be removed according to the established deletion and cleanup processes; existing backup-retention rules still apply. Access may end before physical cleanup finishes.
When a refund is approved, Pro access ends on approval. The account returns to Developer Free; existing endpoints are deactivated and removed, and associated request data follows the same deletion, cleanup and backup rules. The planned voluntary first-purchase guarantee and other refund terms are in the Refund Policy. Mandatory consumer rights remain unaffected.
The following order-processing provisions will apply to paid Pro purchases once Pro subscriptions launch:
Our order process is conducted by our online reseller Paddle.com. Paddle.com is the Merchant of Record for all our orders. Paddle provides all customer service inquiries and handles returns
Pro purchases are not currently available, and Paddle has not yet processed WebhookKit purchases. WebhookKit remains responsible for product-related technical support. See the Privacy Policy for planned data sharing.
9. Liability
WebhookKit is provided without guarantees regarding continuous availability, suitability for a particular purpose or preservation of captured data.
To the maximum extent permitted by applicable law, the operator is not responsible for indirect losses or losses resulting from:
- temporary unavailability of the service;
- loss of temporary webhook data;
- incorrect use of the service;
- disclosure or loss of endpoint credentials caused by the user; or
- data or requests submitted by users or third parties.
Nothing in these Terms excludes or limits liability where such exclusion or limitation is prohibited by law.
10. Privacy
Personal data and browser storage are handled as described in the Privacy Policy and Cookies and Browser Storage Policy.
11. Complaints and Contact
Questions, technical complaints or other concerns regarding WebhookKit can be sent to:
Please include enough information to identify the issue and allow us to investigate it.
Complaints will be reviewed and answered within a reasonable time.
12. Changes to These Terms
These Terms may be updated when the service, legal requirements or operating conditions change.
The current version will always be made available through WebhookKit.
Changes apply from the effective date stated in the updated Terms.
13. Applicable Law
These Terms are governed by Polish law.
If mandatory law applicable to you provides rights that cannot be excluded by these Terms, those rights remain unaffected.