Privacy Policy

SiteChime (“we”, “our”, “us”) provides a webpage change-monitoring service. This page describes what information we collect, why we collect it, and how we handle it.

• Account information. Your email address and authentication identifiers used to sign you in.
• Watches you create. URLs you ask us to monitor, the section selectors you choose, and the schedule on which we check them.
• Snapshots of monitored content. The text content of pages you watch, stored so we can compare versions and show you what changed.
• Billing details. When you subscribe, our payment processor (Stripe) collects payment information directly. We store only a customer reference and subscription status.
• Operational logs. Basic request and error logs needed to keep the service running.

• Run the checks you have configured and send you alerts when changes are detected.
• Provide you with the diff and history of pages you watch.
• Process payments and manage your subscription.
• Diagnose and fix problems with the service.

• We do not sell your personal information.
• We do not ask for the passwords of sites you monitor. Pages behind a login are watched via our browser extension, which uses your existing browser session on your own machine.
• We do not share watch contents with third parties except as needed to deliver the service (for example, our email provider sends your alert emails, and webhook URLs you configure receive alert payloads when changes are detected).

Browser-mode watches use the SiteChime Chrome extension to capture the section you picked from inside your own browser session. To tell the difference between a real page change and a signed-out view (so we can show a “Sign in required” prompt instead of sending a misleading change alert), each capture is accompanied by a small page-context sidecar: the page title, the page URL, a top-of-document HTML excerpt, and a short body-text excerpt. How we handle this sidecar:

• It is used only for sign-in / signed-out detection. It is never used to compute or display the diff between captures.
• It is not persisted. The sidecar is read in memory during the check, used to classify the result, and then discarded with the rest of the in-flight job.
• The HTML and text excerpts are capped before they leave your browser (roughly 40 KB of HTML and 8 KB of text per capture).
• The page title, the HTML excerpt and the text excerpt arenever written to our server logs.
• The URL is logged only in a redacted form— origin and path only, capped to roughly 200 characters. Query strings and URL fragments are stripped, so OAuth state, session tokens and other sensitive query parameters do not appear in our logs.

We use a small number of third-party services to operate SiteChime, including authentication and database hosting (Supabase), payment processing (Stripe), email delivery (Resend), and any third-party endpoint URLs you configure for webhook delivery (Slack, Discord, Zapier, etc.). These providers process data on our behalf under their own privacy terms.

• You can delete a watch at any time from your dashboard, which removes the associated snapshots and history.
• You can cancel your subscription at any time from the billing portal.
• You can request deletion of your account and associated data by contacting us.

Questions about this policy? Reach us at hello@sitechime.com.