This policy explains what PageWatch stores so we can monitor pages, compare changes, send alerts, and operate your account.
Last updated: May 2026
We store account details such as email address, authentication identifiers, workspace membership, roles, plan information, billing identifiers, usage limits, and support notes needed to operate PageWatch.
Authentication is handled through Supabase Auth and billing is handled through Stripe.
When you add a monitor, we may store the URL, monitor name, target mode, CSS selectors, selected visual regions, check interval, status, last checked time, next scheduled check, and related workspace information.
When checks run, we may store hashes, extracted text, HTML snippets, page metadata, status codes, screenshots when enabled, check logs, and error details.
If a change is detected, we may store before/after snapshots, change events, diff information, severity, category, AI summaries, confidence, business impact, and suggested actions.
AI analysis is intended to run when a meaningful change is detected. If a page hash has not changed, PageWatch should not generate an AI summary for that check.
If you configure email, Slack, Discord, Telegram, browser push, webhooks, RSS feeds, or API keys, we store the connection settings and delivery logs required to send alerts.
Alert payloads may include monitored URL, change title, summary, severity, category, evidence links, and selected diff details.
We may collect usage and diagnostic information such as page visits, referrers, country-level location from hosting headers, browser/device information, errors, performance metrics, check volume, alert delivery, and feature usage.
This helps us improve reliability, detect abuse, understand market demand, and make the product faster and safer.
Retention depends on your plan, account status, and system configuration. You can delete monitors, alert destinations, API keys, and workspaces where supported.
Some logs may be retained for security, billing, abuse prevention, debugging, legal compliance, or backup purposes.
You are responsible for monitoring only pages you are legally allowed to monitor and for avoiding sensitive, private, restricted, or unlawful content.
If you export data through RSS, API, webhooks, or third-party alert channels, you are responsible for protecting access to those destinations.
Questions about privacy or data handling can be sent to the support email listed on our website.