Privacy Policy

Last updated: November 16, 2026

This Privacy Policy explains what information CertWatch, operated by ZeroFault Labs LLC ("ZeroFault Labs," "we," "us," or "our"), collects when you use certwatch.sh (the "Service"), and how we use, share, and protect it.

1. Information we collect

We collect the following categories of information:

  • Account information: the email address you sign up with, your hashed password, and account-level alert settings (alert email, the Slack workspace and channel you connect with the bot token Slack issues for them, generic webhook URL). We store the bot token encrypted, use it only to post to and read your workspace for CertWatch alerts, and ask Slack to revoke it when you disconnect, or when your account is purged after its deletion grace period. Reconnecting replaces the stored token without revoking the old one.
  • Endpoint data: the hostnames and ports you configure for monitoring, and the check history we generate for them — timestamps, certificate issuer/subject/expiry, chain validity, and any error messages from a check.
  • Billing data: if you're on a paid plan, our payment processor, Stripe, collects and stores your payment method and billing details. We don't receive or store full card numbers ourselves — see Stripe's own privacy policy for how they handle this data.
  • Usage and technical data: standard request data such as IP address, user agent, and timestamps for requests to our API and public tools (e.g. the certificate checker), collected for rate-limiting, abuse prevention, and debugging.
  • Support messages: when you use Support in the app, what you write, the answers you choose, your alert email, and your account ID and plan. When you email us, your message and your email address.
  • Cookieless product analytics: on certwatch.sh and app.certwatch.sh, our pages send PostHog a page view when you open a page or move to another, a page leave when you leave, and the product events described below, from every visitor, without cookies and without storing an identifier on your device. Rejecting optional analytics cookies leaves them running. Each carries the page address and path, with record IDs and every query value other than campaign tags removed, the campaign tags, the referring site without its page address, the previous page's path, how long you spent on it, and how far you scrolled it, your browser and its version, operating system and its version, device type, screen and window size, and your browser's user-agent string. We do not send monitored hostnames, ports, certificate subjects or SANs, email addresses, webhook URLs, account IDs, or check error text. When you click a link to another site, we send an event with only that site's address, such as https://github.com, never the page on it; when you click a link to a downloadable file, we send one with the file's address, with record IDs and every query value other than campaign tags removed; when you open a page that does not exist, we send one with the path you asked for, cleaned the same way. PostHog derives an anonymous identifier that changes every day from your IP address and that user-agent string, and does not store your IP address; these events carry no location other than the country Cloudflare answers. Each page load asks our Cloudflare service for your browser's country, which the page's events carry once it answers (an event sent before the answer, or after a failed lookup, carries none); the page keeps the country only in memory, and stores in your browser's session storage, until you close the tab, only whether that country requires consent for analytics cookies. When you arrive from a link with campaign tags (utm_source, utm_medium, and utm_campaign), the page also stores those tags in your browser's session storage, until you close the tab, so our signup links on later pages of the same visit still carry them.
  • Analytics with cookies: if you accept optional analytics cookies, from your next page load PostHog sets a cookie on certwatch.sh, shared with app.certwatch.sh, that holds an anonymous identifier, some session information, and the first page and referrer of your visit (with record IDs and every query value other than campaign tags removed from the page address, and the referrer reduced to the referring site), so your visits across pages, both sites, and days count as one visitor. A small companion cookie records which properties the first one holds. The same events are then sent, without the user-agent string, with that identifier and a session identifier. For these events PostHog derives an approximate location from your IP address (city, postal code, latitude and longitude, accuracy radius, time zone, subdivision, country, and continent) and then discards the IP address without storing it. Outside the European Economic Area, the UK, Switzerland, and other countries whose law requires consent for analytics cookies, analytics cookies are on by default: PostHog sets this cookie from the first page on which our Cloudflare service answers your country within a second of the page loading, or, when it answers later, from your next page load on that site in the same browser tab, unless you choose Opt-out in the cookie notice shown there in place of the prompt. In those countries, and while your country is unknown or not yet answered, PostHog sets it only after you accept. While you are signed in on a browser with this cookie and Product analytics is on in Settings, the cookie's identifier is your account's pseudonymous account ID (described under server-side product events below): from your sign-in, or from the next page of the app you open when you were already signed in, that browser's earlier events, with the first page and referrer as stored above, join your account's events. Signing out, or turning off Product analytics on that browser, gives it a new anonymous identifier at once; when your session ends, another account signs in, or Product analytics is turned off elsewhere, it gets one at the next page of the app you open there.
  • Server-side product events: our servers send PostHog product events for your account: when you sign up, verify your email, add an endpoint or a domain, connect Slack, send a test alert that goes through, or schedule your account's deletion; when a subscription starts or ends; and when an endpoint's or a domain's first check completes. Each carries the plan name, the CertWatch environment that sent it, the CertWatch release version, and a pseudonymous account ID, a keyed hash of your account ID that only we can link back to your account, and no visitor IP address. The signup event also carries the campaign tags (utm_source, utm_medium, and utm_campaign) in the signup page's address, where the signup links on every page of certwatch.sh pass them along. Each event also sets these account properties: your plan, the day you signed up, how many endpoints and domains you monitor, which alert channel types you have set up (email, Slack, webhook), and the day you were last active (a subscription change our payment processor makes without you, such as a renewal failing, leaves that day as it was). Deleting a monitor or changing an alert channel sends them on their own. They are counts and categories, never a hostname, an email address, a Slack channel, or a webhook URL. They are sent without a consent step, whether or not you accept optional analytics cookies. You can turn off Product analytics on the Account tab of Settings; after that your account sends none.
  • Plausible page analytics: on certwatch.sh and app.certwatch.sh we use Plausible to count page views, without cookies and regardless of your cookie choice. It receives the page path, the referring site, your browser, operating system, and device type, and a country derived from your IP address; it does not store your IP address or build a profile of you. We remove query strings (other than campaign tags such as utm_source) and the IDs in record page paths before the data leaves your browser.

Our legal basis for analytics:

  • Consent for analytics with cookies in the European Economic Area, the UK, Switzerland, and other countries whose law requires consent for analytics cookies, which you give by accepting optional analytics cookies and can withdraw as section 6 describes. There PostHog sets its cookie only after you accept.
  • Legitimate interest for cookieless product analytics, the server-side product events, Plausible page analytics, and, outside those countries, analytics with cookies until you opt out in the cookie notice: our interest in understanding how the Service is used so we can improve it. You can object by emailing support@certwatch.sh, for the server-side product events by turning off Product analytics in Settings, or, for analytics with cookies, by choosing Opt-out in the cookie notice. Cookieless browser events and Plausible page views are not linked to you, so we cannot single out yours; to stop them, block us.i.posthog.com and plausible.io in your browser. Blocking them does not stop the server-side product events, which only the Settings switch stops.

2. How we use this information

  • To provide the Service — running checks against the endpoints you configure and delivering alerts.
  • To operate your account — authentication, plan enforcement, and billing.
  • To communicate with you — service emails (alerts, billing receipts, account notices) and, if you contact us, support.
  • To maintain and improve the Service — debugging, abuse prevention, and rate-limiting.
  • To comply with legal obligations.

We don't sell your personal information, and we don't use your monitored hostnames or check history for advertising.

3. Third-party processors

We use the following third-party services to operate CertWatch, each of which processes a subset of the data above on our behalf:

  • Stripe — payment processing and subscription billing.
  • Postmark — transactional email delivery (alerts, account emails, support messages).
  • Google — the Gmail inbox that receives and stores support messages, and where we reply from.
  • Slack — a private channel of ours that every support message is forwarded to, so we see it.
  • Fly.io — application hosting and database infrastructure.
  • Grafana Labs — Grafana Cloud, in the United States, for our server logs, which include IP addresses, and metrics.
  • PostHog — product analytics, on PostHog's US cloud. Our pages send it page views, page leaves, and explicit events from every visitor without cookies, and with its cookie after you accept optional analytics cookies, or by default, unless you opt out in the cookie notice, outside the European Economic Area, the UK, Switzerland, and other countries whose law requires consent for analytics cookies; autocapture and session replay are disabled. PostHog stores no IP address: events sent with its cookie carry an approximate location derived from it, and cookieless events carry only the country Cloudflare answers. Separately, our servers send PostHog the server-side product events described in section 1 for each account that has not turned them off, without a consent step; they carry the plan name, the CertWatch environment that sent them, the CertWatch release version, a pseudonymous account ID, and the account properties and campaign tags section 1 lists, and no visitor IP address.
  • Plausible — cookieless, aggregate page analytics on certwatch.sh and app.certwatch.sh, loaded from plausible.io. It is not gated by the cookie prompt because it sets no cookies and stores no IP address; see section 1 for what it receives.
  • Cloudflare — DNS for certwatch.sh, hosting for our documentation site, docs.certwatch.sh, and region.certwatch.sh, which answers your browser's country from your IP address on each page load, without logging the request or storing your IP address.

PostHog (on its US cloud) and Cloudflare process data in the United States, outside the European Economic Area, the UK, and Switzerland. Both are certified under the EU-U.S. Data Privacy Framework, its UK Extension, and the Swiss-U.S. Data Privacy Framework, which is the basis on which we transfer data to them.

If you connect Slack or configure a generic webhook alert destination, the alert payload (which includes your endpoint hostname and certificate status) is sent directly to that channel or URL — that delivery is between our servers and the destination you configured, and is subject to that destination's own handling of the data it receives. When someone acknowledges an alert from Slack, we store their Slack display name with the acknowledgement and in your account's History.

4. Data retention

Check history is retained according to your plan (30 days on Free, 90 days on Starter, 365 days on Pro), after which older records are deleted on a rolling basis. Account information is retained for as long as your account is active. If you delete your account, we delete your account and endpoint data within a reasonable period, except where we're required to retain billing records for legal or tax purposes. When we do, we also delete from PostHog the server-side product events sent under your account's pseudonymous ID. PostHog keeps analytics events for 1 year, the retention on our PostHog plan, after which they are deleted. Server logs are kept 14 days, after which they are deleted.

5. Data security

We use industry-standard measures to protect your data, including encrypted connections (TLS) for data in transit and hashed password storage. No method of transmission or storage is completely secure, and we can't guarantee absolute security.

6. Your choices and rights

You can access and update most of your account information directly from your account settings, including deleting endpoints and closing your account. Depending on where you live, you may have additional rights over your personal information — such as the right to request a copy of it or its deletion. Contact us at support@certwatch.sh to exercise these rights, and we'll respond within a reasonable time.

You can decline optional analytics cookies in the cookie prompt, or, outside the European Economic Area, the UK, Switzerland, and other countries whose law requires consent for analytics cookies, where analytics cookies are on by default, choose Opt-out in the cookie notice. Rejecting or opting out stops analytics with cookies at once, and leaves the cookieless product analytics, the server-side product events, and the cookieless Plausible page analytics described in sections 1 and 3 running. Turning off Product analytics in Settings stops the server-side product events for your account; those already sent are deleted with your account. The properties we attach to analytics events are an identifier (a pseudonymous account ID for the server-side product events; for browser events, the anonymous daily one PostHog derives, or, with its cookie, the one the cookie holds, which is your account's pseudonymous ID while that browser is joined to your account, plus a session identifier), the CertWatch environment that sent the event, the CertWatch release version, and, when relevant, a plan name or a certificate check result status (such as ok or expired). Server-side product events also set the account properties section 1 lists: your plan, the day you signed up, how many endpoints and domains you monitor, which alert channel types you have set up (email, Slack, webhook), and the day you were last active; the signup event also carries the campaign tags in the signup page's address. Browser events also carry the CertWatch site they came from, your country once Cloudflare answers it, the page address and path with record IDs and every query value other than campaign tags removed, the campaign tags, the referring site, and the browser details listed in section 1, the user-agent string with cookieless events only. The event for a click on a link to another site carries only that site's address, such as https://github.com, never the page on it; the event for a click on a downloadable file carries the file's address, cleaned the same way; the event for a page that does not exist carries the path you asked for, cleaned the same way. PostHog stores no IP address with any event: as section 1 describes, events sent with its cookie carry an approximate location derived from your IP address, and cookieless events carry only that country.

One choice covers both certwatch.sh and app.certwatch.sh. We remember it in a cookie named certwatch_consent, set on certwatch.sh and shared with its subdomains such as app.certwatch.sh, that holds only "accepted" or "declined" and lasts 12 months, after which we ask again. We also keep a copy of the choice in your browser's local storage on the site where you made it. To make the choice again, delete the certwatch_consent cookie in your browser's cookie settings and clear local storage for certwatch.sh and app.certwatch.sh. If you accepted analytics, or had them on by default, also delete the PostHog cookies, whose names start with ph_, and the same PostHog entries in local storage. When you reject or opt out, we stop analytics with cookies and remove PostHog's cookies and stored entries on the site where you do so at once, and any left on the other site are cleared the next time you open a page there while your choice is stored, so accepting later starts as a new visitor.

7. Children's privacy

CertWatch isn't directed at children under 16, and we don't knowingly collect personal information from them.

8. Changes to this policy

We may update this Privacy Policy from time to time. If we make a material change, we'll update the "Last updated" date above and, where practical, notify account holders by email.

9. Contact

Questions about this Privacy Policy can go to support@certwatch.sh.