Privacy policy

What we collect

• Account data: name, email address, company name if you provide one, and billing details handled by our payment processor.
• Watch configuration: the monitors, sources, keywords, states, brands, domains, and filters you set up.
• Alert history: what we sent you and when, so you can search it and so we can improve relevance.
• Contact form submissions: the name, email, company, and message you send through the contact form, stored on our own servers so we can reply and keep a record.
• Usage data: basic technical logs (IP address, browser, timestamps) needed for security and troubleshooting.

What we monitor

We monitor public sources: government portals, registers, dockets, marketplace results, certificate logs, and similar. We do not access private accounts, login-walled third-party systems, or anything we are not authorized to read.

Login-walled sources

Some pages you want watched sit behind a login. We support those, but the rule is fixed: we never store your username, password, session cookie, or any other reusable credential for a system we do not control. That is how the product is built, not a promise in this policy.

For a login-walled source, the check runs from your side of the connection. You sign in as normal in your own browser, a small helper you install captures the page at that moment, and we receive only the change that resulted. If the capture runs on infrastructure you run, we never see the page at all, just the alert. You can revoke access by uninstalling the helper or removing the source from your account, and doing so stops all collection immediately.

What we hold for these sources is the smallest useful set: the source address, a fingerprint of the page so we can detect a change, the change itself so we can describe it in the alert, and the delivery details for your alerts. We do not build a copy of the underlying system, we do not retain historical page contents beyond what your plan requires, and we never use one customer's login-walled data for anyone else.

Some sites' terms forbid automated access even when you are an authorized user. Where that applies, it is your call as the account holder, and you are responsible for it. We will point you to an official API where one exists, because that is almost always the better answer.

How we use it

• To run your monitors and deliver alerts.
• To provide support and fix problems.
• To bill you for the service.
• To improve triage quality using aggregate, de-identified patterns.

What we never do

• We never sell, rent, or trade your personal data or watchlists.
• We never use your watchlists to give another customer an advantage.
• We never send your data to advertisers.
• We never store your login credentials. Not encrypted, not temporarily, not for a "better experience." If a feature would require us to hold one, we will not build it that way.
• We never require you to email us a password, and we will never ask you to paste credentials into chat, a form, or a support ticket.

Cookies and analytics

This site uses Umami, an open-source analytics tool that we run ourselves on our own server. It sets no cookies, stores no personal identifiers, and does not track you across other sites. What we see is aggregate: page views, referrers, country, device type, and which forms or buttons were used. There is no third-party advertising tracker here, and no analytics data is shared with or sold to anyone. The application may use a session cookie for authentication once you are a customer.

Sharing

We share data with processors who help us operate: hosting, email delivery, payment processing, error monitoring, and our self-hosted notification service which alerts us when a form is submitted. Each is bound by contract to use it only for that purpose. We disclose data to authorities only when legally required, and we will tell you when we are allowed to.

Retention

Account data is kept while your account is active and for a short period after, for legal and accounting reasons. Alert history is kept according to your plan. You can request deletion at any time.

Your rights

Depending on where you live, you may have rights to access, correct, export, or delete your personal data, and to object to certain processing. Email hello@clerkwatch.com and we will handle it, usually within a few days.

Where our data lives

We run our own infrastructure rather than reselling your data to a third party. Our email delivery runs through Resend, and our analytics is self-hosted Umami, which sets no cookies and stores no personal identifiers. The named processors that handle your data are listed in the data processing addendum you can request from us, and we will tell you before adding a new one that touches account data.

Security

Encryption in transit and at rest, least-privilege access, and audit logging. If a breach ever affects your data, we will notify you directly and promptly, not bury it in a status page.

Contact

Questions, deletion requests, or anything else: hello@clerkwatch.com.