Privacy Policy

Account information

When you create an account we store your email address and a bcrypt hash of your password — we never store your password in plain text. We use your email to identify your account and, if you opt in, to send you change notifications.

Watch data

For each watch you create we store the page URL, the CSS selector you chose, your label, check interval, and the content snapshots captured during monitoring. These snapshots are the only way we can detect changes and show you before/after history. We store only the specific element you selected — not the full page, not your other open tabs, not your browsing history.

Change history

When a change is detected we record the previous and new content, the timestamp, and any acknowledgment notes you add when reviewing the change. This history is visible only to you (and your team, if you are on the Team plan).

Visual screenshots (Pro/Team)

If you enable the optional Visual snapshot feature on a watch, the extension captures a screenshot of the watched page whenever a change is detected and the page is open in your browser. The screenshot, a highlighted diff image, and a changed-pixel ratio are uploaded to and stored on our server. Screenshots are tied to your change history and are deleted when you delete the watch or its history. This feature is opt-in, off by default, and available on Pro and Team plans only.

Profile avatar

If you upload a profile photo it is stored on our server and displayed in the extension and dashboard. Uploading a photo is entirely optional.

Session tokens

We issue short-lived JWT access tokens (15-minute expiry) and longer-lived refresh tokens (30 days, stored as a bcrypt hash on our server). These tokens keep you signed in without requiring your password on every request.

Team data

If you create or join a team we store the team name, member email addresses, and member roles. Team members can see watches that have been explicitly shared with the team — personal watches remain private.

Notification settings

If you configure email notifications, Slack, Discord, or generic webhook delivery, we store those endpoint URLs or preferences so we can send you alerts. We do not sell or share these addresses with third parties.

Usage analytics

The extension sends a small number of anonymised usage events to help us understand how the product is used and where users hit limits. The full list of events we record is:

• sidepanel.opened — the extension panel was opened (no properties)
• watch.created — a watch was created (monitor mode, account tier)
• check.completed — a watch check ran (monitor mode, result, error type if any)
• watch.create_blocked — a watch could not be created due to the plan limit (tier, limit)
• upgrade.prompt_viewed — the upgrade screen was shown (context, trigger)

No page content, URLs, or personally identifying information is included in these events. Events are linked to your user ID if you are signed in, or recorded anonymously if you are not.

Billing information

Payments are processed by Stripe. We never see or store your credit card number, CVV, or full card details. We store only your Stripe customer ID and subscription status so we know which plan your account is on.