Request data we process
When a temporary receiver gets a request, Checkhooks processes its method, URL, query parameters, headers, and body so the app can display the event and render your configured response template.
Legal · Privacy
Clear boundaries for temporary data.
This policy describes what Checkhooks processes, where temporary request data may exist, and how to test integrations without exposing sensitive information.
Privacy summary: use synthetic data, assume receiver URLs can be shared by anyone who has them, and do not rely on Checkhooks as permanent storage.
Temporary receiver storage
Receiver events and response settings are held in server memory for the active receiver. They are not designed as permanent records and may disappear after a restart, deployment, expiration, or infrastructure change.
Data in your browser
The temporary app stores only interface preferences such as your light or dark theme. The archived v2 workspace may store saved endpoints, templates, and request history in your browser’s local storage.
Outgoing destinations
When you send a checkhook, the destination you enter receives the request data you provide. That destination operates under its own privacy and security practices, which Checkhooks does not control.
Sharing and tracking
Checkhooks does not sell receiver payloads or use them for advertising. The current product does not require an account and does not intentionally build a profile from your test request content.
Secrets and security
Do not submit passwords, private keys, access tokens, regulated personal data, or production secrets. Use synthetic test data, scoped credentials, and receiver URLs you are comfortable treating as temporary shared secrets.
Back to homeEffective date: June 2026