# Terms change watch

Sends a clause-by-clause redline when a vendor changes its terms or privacy policy.

Requires web search, through Exa. Requires web fetch. Runs on a schedule.

## Install

```sh
npx @parcha/agentrun template install github:Parcha-ai/agentrun-templates/templates/terms-change-watch@242f29da8317fbe51d0cce4628bdb5ab61d7ccc9 --trust
```

Or open `<your AgentRun address>/#/templates/install?src=github%3AParcha-ai%2Fagentrun-templates%2Ftemplates%2Fterms-change-watch%40242f29da8317fbe51d0cce4628bdb5ab61d7ccc9`. Pinned to commit 242f29da8317fbe51d0cce4628bdb5ab61d7ccc9.

## What it does

Watches the terms of service, privacy policies, DPAs and acceptable use policies of the vendors you rely on and sends a clause-by-clause redline when one changes. Each change quotes the old and new wording with its section number, gives the version date and the effective date apart, and says what to review with counsel. Typo fixes and renumbering are left out, and a vendor's "no material change" is reported as the vendor's claim.

- Skill `terms-watch`: Check vendors' legal pages (terms, privacy policies, DPAs, acceptable use policies, subprocessor lists) for clause-level changes since the last check. Read each page's version stamp, compare its clauses with the earlier text (your learned note, the last run, the vendor's version history, else an archive copy), keep substantive changes, quote old and new wording with clause numbers, keep version and effective dates apart, drop repeats, and keep a note of each page's key clauses for next time. Use for the scheduled check and for "did Slack change its DPA", "what changed in these terms".
- Rules: `LEGAL-TEXT.md`

## What starts it

- On a schedule: Mondays at 08:00 (UTC), unless you pick another time when you install it.
- By hand, any time: from the console, the API or the CLI.

## Inputs

| Name | Type | Required | What it is |
| --- | --- | --- | --- |
| `documents` | list of string | yes | URLs, or a vendor and document name, up to 30. The schedule passes your saved list; a run by hand can check others. Example: `https://ledgerline.example/legal/terms,Northdesk privacy policy`. |
| `care_about` | string, 0 to 300 characters | no | Ranks these themes first. Blank: changes to obligations, rights, liability, fees and termination first, then the soonest effective date. |
| `lookback_days` | integer, 1 to 90 | no | Blank: 7. |

### Setup, filled in once at install

| Name | Type | Required | What it is |
| --- | --- | --- | --- |
| `documents` | list of string | yes | The legal pages to watch, one per entry: a URL ("https://stripe.com/legal/ssa") or a vendor and document ("Slack privacy policy", "Notion DPA"). Up to 30. |
| `care_about` | string | no | Optional: the themes to rank first, in a few words ("liability caps, AI training on our data"). It changes the order only: every substantive change is still reported. |
| `lookback_days` | integer | no | The gap between runs, in days, used to pick an archive copy when a page has no earlier version on record (7 for the weekly default) Default: `7`. |
| `cron` | string, cron | no | When the check runs, as a cron line (minute hour day-of-month month day-of-week): Monday 08:00 unless you set it. Default: `0 8 * * 1`. |
| `timezone` | string, timezone | no | The IANA time zone the cron line is read in (Europe/Madrid, America/New\_York): UTC unless you set it. Default: `UTC`. |

## What it needs

- Harness: pi, claude-agent, codex
- Model: balanced tier, low effort
- Tools: read, web_search, web_fetch
- Computer: Wherever your AgentRun puts a new agent
- Keys: A model key
- Learning: on

## Sample output

Input:

```json
{
  "content": "Scheduled run, fired 2026-11-16T08:00:00Z (Monday). Check the legal pages below for changed clauses with your terms-watch skill.\n\nThe sites below are not reachable from this run. The pages that follow are what their URLs return today; use them in place of fetching. These terms are test data.\n\n--- https://ledgerline.example/legal/terms (fetched 2026-11-16) ---\n<div class=\"banner\">We've updated our Terms to clarify how we improve our services. These updates do not materially change your rights.</div>\n<h1>Ledgerline Terms of Service</h1>\n<p>Last updated: November 12, 2026. These updated Terms take effect on December 15, 2026.</p>\n<h2>3. Changes to these Terms</h2><p>3.4 We will give Customer at least thirty (30) days' notice of changes to these Terms.</p>\n<h2>4. Customer Data</h2><p>4.1 Customer owns all Customer Data.</p><p>4.3 Ledgerline may use Customer Data in de-identified form to train and improve machine learning models, unless Customer opts out under Section 4.4.</p><p>4.4 Customer may opt out of the use described in Section 4.3 by emailing privacy@ledgerline.example. The opt-out applies to Customer Data received after Ledgerline confirms it.</p>\n<h2>6. Support</h2><p>6.1 Customer will receive support by email on business days.</p>\n<h2>7. Taxes</h2><p>Fees exclude taxes. Customer pays all sales, use and value-added taxes on the Services.</p>\n<h2>8. Fees</h2><p>Customer pays the fees in the Order Form, annually in advance, within thirty (30) days of invoice.</p>\n<h2>9. Limitation of Liability</h2><p>9.1 Neither party is liable for indirect or consequential damages.</p><p>9.2 Each party's total liability under these Terms will not exceed the fees paid by Customer in the three (3) months preceding the claim.</p>\n<h2>12. Governing Law</h2><p>12.1 These Terms are governed by the laws of the State of Delaware.</p>\n<footer>© 2026 Ledgerline, Inc.</footer>\n\n--- https://web.archive.org/web/20261109/https://ledgerline.example/legal/terms (lands on https://web.archive.org/web/20261107153012/https://ledgerline.example/legal/terms) ---\n<h1>Ledgerline Terms of Service</h1>\n<p>Last updated: August 1, 2026.</p>\n<h2>3. Changes to these Terms</h2><p>3.4 We will give Customer at least thirty (30) days' notice of changes to these Terms.</p>\n<h2>4. Customer Data</h2><p>4.1 Customer owns all Customer Data.</p><p>4.3 Ledgerline will not use Customer Data to train machine learning models.</p>\n<h2>6. Support</h2><p>6.1 Customer will recieve support by email on business days.</p>\n<h2>7. Fees</h2><p>Customer pays the fees in the Order Form, annually in advance, within thirty (30) days of invoice.</p>\n<h2>8. Taxes</h2><p>Fees exclude taxes. Customer pays all sales, use and value-added taxes on the Services.</p>\n<h2>9. Limitation of Liability</h2><p>9.1 Neither party is liable for indirect or consequential damages.</p><p>9.2 Each party's total liability under these Terms will not exceed the fees paid by Customer in the twelve (12) months preceding the claim.</p>\n<h2>12. Governing Law</h2><p>12.1 These Terms are governed by the laws of the State of Delaware.</p>\n<footer>© 2026 Ledgerline, Inc.</footer>",
  "documents": [
    "https://ledgerline.example/legal/terms"
  ],
  "care_about": "liability caps and use of our data for AI training",
  "lookback_days": 7
}
```

Output:

**Terms changes** 2026-11-09 to 2026-11-16
Ledgerline reduces the mutual liability cap and replaces its AI-training prohibition with permission subject to a prospective opt-out.

- **Ledgerline terms, 9.2 Limitation of Liability: cap reduced** ([live](https://ledgerline.example/legal/terms), [before](https://web.archive.org/web/20261107153012/https://ledgerline.example/legal/terms))
  Before: "in the twelve (12) months preceding the claim." · After: "in the three (3) months preceding the claim."
  Version November 12, 2026 · Effective December 15, 2026.
  _Review recovery exposure and negotiated protection with counsel._

- **Ledgerline terms, 4.3 Customer Data, with added 4.4: AI training permitted unless opted out** ([live](https://ledgerline.example/legal/terms), [before](https://web.archive.org/web/20261107153012/https://ledgerline.example/legal/terms))
  Before: "4.3 Ledgerline will not use Customer Data to train machine learning models." · After: "4.3 Ledgerline may use Customer Data in de-identified form to train and improve machine learning models, unless Customer opts out under Section 4.4."
  Added 4.4 limits the opt-out: "The opt-out applies to Customer Data received after Ledgerline confirms it."
  Version November 12, 2026 · Effective December 15, 2026. Vendor says: "These updates do not materially change your rights."
  _Review opting out, confirmation timing and treatment of previously received data with counsel._

_Baseline: November 7 archive capture. Support typo and Fees/Taxes renumbering ignored. Unchanged pages: none; no-baseline pages: none; unreachable supplied texts: none._
_Not legal advice: review each change with counsel._

## Tested

Passes 4 of 4 eval cases on pi, 1 of 4 on Claude Code and 4 of 4 on Codex. Not yet tried on the live web.

4 eval cases: clause-redline, injection-in-terms, no-repeats, unchanged-and-unbaselined.

## Source

- Package: https://github.com/Parcha-ai/agentrun-templates/tree/242f29da8317fbe51d0cce4628bdb5ab61d7ccc9/templates/terms-change-watch
- Publisher: Parcha-ai
- Author: Parcha Labs
- Version: 0.1.0
- License: Apache-2.0
- Category: Compliance
- Page: https://marketplace.agentrun.ai/templates/terms-change-watch/
