Security

How CountWatch keeps your counts, keys and alerts safe, and how to report a problem.

What we keep

Counts and the labels you send with them, the alerts they raise, and where alerts go. Counts are kept for 90 days. We never store request bodies, page content or customer records. The privacy notice lists everything.

Keys and access

• API keys and the webhook URLs you make for sending counts are stored only as one-way hashes. We show each one once; nobody can read it back, not even us.
• A write key only sends counts. An admin key manages the account. Name each key, and revoke it in Settings at any time.
• Agents connect over MCP and sign in with your e-mail; they never hold a key. Disconnect an agent in Settings.

Signing in

Sign-in is a link sent to your e-mail: no password to steal or reuse. Two cookies keep you signed in, both secure and not readable by scripts.

Alerts you can trust

Webhook alerts are signed (Standard Webhooks, HMAC-SHA256) with a secret made for each destination, so your receiver can check that an alert came from CountWatch. Slack and PagerDuty get alerts only when you add them.

Where it runs

CountWatch runs on Cloudflare. Your account's data is stored in Cloudflare's EU jurisdiction.

Your control

Export everything in Settings. The owner can erase the account and all its data at once.

Report a problem

Found a security issue? Write to hello@countwatch.com. Please give us time to fix it before you tell others.