Vendor Change Watchdog FAQ

Last updated: March 24, 2026

What does this service monitor?

It monitors pages you choose, such as:

• privacy policies
• terms pages
• pricing pages
• support pages
• compliance pages
• policy update feeds

Who is this product for?

It is most useful for teams that depend on vendor promises remaining stable, especially:

• engineering teams tracking support or operational commitments
• operations or finance teams watching pricing and entitlements
• privacy, legal, procurement, or compliance teams reviewing policy language

Does it watch an entire website automatically?

No.

The service monitors the specific pages you add, plus any linked-document workflows you intentionally use, such as supported policy update index pages.

Will it tell me whether a vendor change is legally important?

No.

It helps surface likely-important changes faster, but human review is still required for legal, privacy, procurement, finance, or engineering decisions.

How does it decide what counts as a change?

The service stores snapshots, compares the newest one to the prior one, and runs a structured analyzer on qualifying diffs.

The goal is to reduce noisy page drift and surface changes worth human review.

What does a typical workflow look like?

A common workflow is:

1. validate and add a page
2. capture the baseline
3. let scheduled checks monitor it
4. review a qualifying change in the dashboard or change detail page
5. tune alerts if that page is too noisy or not sensitive enough

Is there a free plan?

Yes.

Current public plan shape:

• free: up to 3 monitored pages
• starter: up to 10 monitored pages
• pro: up to 25 monitored pages

See the public Plans page for the current plan summary.

Will I get an email for every change?

Not necessarily.

Alerts depend on your account and page-level settings, including:

• whether alerts are enabled
• minimum severity threshold
• page-specific destination email, if configured

Can I tune alerts for individual pages?

Yes.

You can tune:

• enabled or muted alerts
• minimum severity
• page-specific destination email
• account-level defaults for new pages

What if a page cannot be fetched reliably?

Use candidate validation before saving a new page.

If a site blocks or fails the fetch path, the app will show that during validation or later checks.

What kinds of pages work best?

The service is strongest on vendor pages with meaningful written commitments, such as:

• privacy policies
• pricing pages
• support or SLA pages
• terms, compliance, or policy documents

It is less useful on pages that are highly dynamic, heavily personalized, or intentionally block the fetch path.

Does the service store page content?

Yes.

It stores monitored snapshots and related change evidence so reviewers can inspect the before-and-after text.

Can I remove a monitored page later?

Yes.

Removing a monitored page currently removes the page and its related stored history for that account.

Is this an enterprise-grade status page?

No.

The public Status page explains the current operated-service posture, but this is not currently presented as a formal SLA or external incident-management system.

Does this replace legal or procurement review?

No.

It is a review accelerator, not a substitute for judgment. Human review is still required for privacy, legal, procurement, finance, compliance, or engineering decisions.

How do I contact someone about the service?

Use the public contact page or email:

• admin@teamadler.com