# Privacy Policy & Terms of Service Change Monitor: Diff (`transparent_meteorite/privacy-policy-change-monitor`) Actor

From $11 per 1K policies checked. Find out what changed in a vendor privacy policy or terms of service: added and removed sentences, change percent and the date it last changed, compared with the Wayback Machine or your last run. No API key, no proxy.

- **URL**: https://apify.com/transparent_meteorite/privacy-policy-change-monitor.md
- **Developed by:** [Detroit Web Agent - Open Data](https://apify.com/transparent_meteorite) (community)
- **Categories:** Automation, Business
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $6.62 / 1,000 policy checkeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Privacy Policy & Terms of Service Change Monitor: Diff

Find out what changed in a vendor's privacy policy or terms of service. Give the Actor a list of domains (or direct policy URLs) and it finds each privacy policy and terms page, reads the current text and compares it with an archived Wayback Machine copy from a year ago, or with what it saw on your last run. You get one row per document with the added sentences, the removed sentences, how much of the text changed and the date the current wording first appeared.

Typical jobs: vendor risk and third-party reviews, compliance and legal watch lists, checking which SaaS tools quietly changed how they use your data, and alerting a team before a terms update takes effect. No API key, no browser and no proxy are needed.

### Run in 30 seconds

1. Open the **Input** tab. The prefilled list of 16 well-known vendors is a ready-to-run test.
2. Click **Start**. A first dataset with about 30 policy rows is ready in a few minutes.
3. Open the **Policy changes** table in the Output tab, or download the dataset as JSON, CSV, Excel or HTML.
4. Replace the list with your own vendors. Set **Compare with** to "My previous run" and schedule the Actor to be told only about new changes.

### What you get

For every domain the Actor looks for the privacy policy, terms of service and (optionally) cookie policy, first through the footer links of the homepage and then through the usual addresses such as /privacy, /legal/terms and /terms-of-service. Each page is converted to clean text (navigation, footer and scripts removed) and split into sentences. The diff is sentence based, so a reordered paragraph or a punctuation fix is not reported as a change.

| Feature | Detail |
|---|---|
| Documents | Privacy policy, terms of service, cookie policy |
| Input | Domains such as stripe.com, or direct policy page URLs |
| Baseline | Wayback Machine copy from N days ago (default 365), or your previous run |
| Diff | Added and removed sentences, counts and change percent |
| Last changed | Date of the first archived snapshot that matches the current text |
| Threshold | A document counts as changed from 3 changed sentences (adjustable) |
| Bad pages | Not found, blocked and too short pages return a status and are free |
| Keys and limits | No account, no API key, no proxy |

### Pricing

| | |
|---|---|
| Price per 1,000 policies checked (Free plan) | $11.00 |
| Start fee | $0.00005 per run |
| Plan discounts | Bronze $10.20, Silver $8.64, Gold and above $6.62 per 1,000 |
| Charged for | only documents that were read and compared (status `ok`) |
| Not charged | pages not found, blocked, too short or failed |

### Input

- **Websites or policy URLs**: domains or direct policy page URLs, one per line.
- **Documents to check**: privacy, terms and cookies (default privacy and terms).
- **Compare with**: `wayback` (archived copy) or `lastRun` (what this Actor saw last time; the first run falls back to Wayback).
- **Baseline age (days)**: which archived copy to use for the Wayback comparison.
- **Changed threshold (sentences)**: minimum changed sentences to mark a document as changed.
- **Find the last-changed date**: search the archive for when the current text first appeared.
- **Max characters of changed text**: limit per row for added and removed text.
- **Max documents**: cap for the run.

### Example input

```json
{
  "urls": ["stripe.com", "slack.com", "https://github.com/site/terms"],
  "docTypes": ["privacy", "terms"],
  "compareTo": "wayback",
  "compareDaysAgo": 365,
  "maxItems": 100
}
```

### Output sample

```json
{
  "url": "https://stripe.com/privacy",
  "site": "stripe.com",
  "docType": "privacy",
  "status": "ok",
  "changed": true,
  "addedText": "We may use service providers to help us process your data. ...",
  "removedText": "We keep personal data for as long as ...",
  "addedCount": 14,
  "removedCount": 9,
  "changePercent": 8.4,
  "lastChanged": "2026-03-12",
  "baselineSource": "wayback",
  "baselineDate": "2025-11-02",
  "title": "Stripe Privacy Policy",
  "wordCount": 9120,
  "textHash": "4f0c9e1a7b",
  "checkedAt": "2026-11-10T20:00:00.000Z",
  "note": null
}
```

### Output fields

Every row has these fields. Rows that are not read keep the same keys with empty values and a `note`.

| Field | Type | Description |
|---|---|---|
| `url` | string | Address of the privacy policy, terms or cookie policy page that was checked |
| `site` | string | Domain the page belongs to, for example stripe.com |
| `docType` | string | Document type: privacy, terms or cookies |
| `status` | string | ok when the page was read and compared; not_found, blocked, too_short or error rows are returned free of charge |
| `changed` | boolean | true when at least the minimum number of sentences were added or removed since the baseline |
| `addedText` | string | Sentences that are in the current policy but not in the baseline copy, one per line |
| `removedText` | string | Sentences that were in the baseline copy but are gone from the current policy, one per line |
| `addedCount` | integer | Number of added sentences |
| `removedCount` | integer | Number of removed sentences |
| `changePercent` | number | Share of the policy text that differs from the baseline, in percent |
| `lastChanged` | string | Date (YYYY-MM-DD) of the first Wayback Machine snapshot that matches the current text: the policy has read the same since then |
| `baselineSource` | string | What the current text was compared with: wayback (archived copy), lastRun (your previous run) or none |
| `baselineDate` | string | Date of the baseline copy (YYYY-MM-DD) |
| `title` | string | Page title of the policy |
| `wordCount` | integer | Number of words in the current policy text |
| `textHash` | string | Hash of the normalized policy text: store it to detect a change without keeping the text |
| `checkedAt` | string | ISO timestamp of the run that produced the row |
| `note` | string | Explains a row that is not ok or a baseline caveat, for example that the oldest archived copy was used |

### Use cases

- Vendor risk management: watch the privacy policy and terms of every SaaS vendor and get the exact sentences that changed.
- Compliance and legal teams: keep an evidence trail of when a policy changed and what it said before.
- Procurement and security reviews: check whether a supplier changed data sharing, retention or AI training wording.
- Agencies and consultants: send clients a monthly report of policy changes across their tool stack.
- Privacy researchers: measure how often and how much big platforms rewrite their policies.
- Product teams: track how competitors word data use, cancellation and refund terms.

### Run it from code

**API (returns the rows directly):**

```bash
curl -X POST "https://api.apify.com/v2/acts/transparent_meteorite~privacy-policy-change-monitor/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"urls":["stripe.com","slack.com"],"docTypes":["privacy"]}'
```

**Python:**

```python
from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("transparent_meteorite/privacy-policy-change-monitor").call(
    run_input={"urls": ["stripe.com", "slack.com", "zoom.us"], "docTypes": ["privacy", "terms"]}
)
for row in client.dataset(run["defaultDatasetId"]).iterate_items():
    if row["status"] == "ok" and row["changed"]:
        print(row["site"], row["docType"], row["lastChanged"], row["addedCount"], "added")
```

**MCP (Claude, Cursor and other agents):** add the Apify MCP server and enable this Actor.

```json
{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=transparent_meteorite/privacy-policy-change-monitor",
      "headers": { "Authorization": "Bearer YOUR_APIFY_TOKEN" }
    }
  }
}
```

Then ask your agent: "Did the privacy policy or terms of service of these vendors change this year?" and paste the list.

### Integrations and scheduling

| Tool | How to use it |
|---|---|
| n8n | Add the **Apify** node, choose **Run Actor**, set the Actor to `transparent_meteorite/privacy-policy-change-monitor`, pass `{"urls": ["={{ $json.domain }}"], "compareTo": "lastRun"}`, then add **Get Dataset Items** and an IF node on `changed` to alert only on real changes |
| Make and Zapier | Use the Apify app: Run Actor, then read the dataset items |
| Slack and email | Schedule weekly, set Compare with to My previous run, and send rows where `changed` is true |
| Google Sheets | Append the dataset rows to keep a policy change log |

Every run's dataset can also be downloaded as JSON, CSV, Excel, XML or HTML. For a monitor, schedule the Actor weekly or monthly and use the previous-run comparison.

### Search terms this Actor covers

privacy policy change monitor, terms of service change tracker, privacy policy diff, terms and conditions monitor, track privacy policy updates, vendor privacy policy monitoring, TOS change detection, compare privacy policy versions, privacy policy history Wayback Machine, policy change alert, third-party vendor policy review, when did the privacy policy change, cookie policy change monitor, legal document change tracker.

### Limits

- Pages that need JavaScript to show the text, or that block automated requests, return a status such as `too_short` or `blocked` and are free.
- The Wayback comparison needs an archived copy. When none exists the row says so in `note` and the next run with Compare with set to My previous run becomes the baseline.
- The diff reports sentence changes. It does not interpret whether a change is good or bad for you and is not legal advice.
- The Actor reads public pages at a polite pace and respects the archive's rate limit.

### FAQ

**Do I need an API key?** No. The Actor reads the public pages and the public Wayback Machine.

**How does it know the last-changed date?** It checks archived snapshots and finds the first one whose text matches the current policy. The policy has read the same since that date.

**Can I get only real changes?** Yes. Filter on `changed` equal to true. Raise the changed threshold to ignore small edits.

**How do I monitor over time?** Schedule the Actor and set Compare with to My previous run. Each run compares with the text stored by the previous run.

**What if a site has no standard policy address?** Pass the direct policy URL instead of the domain.

**Are the changes sentence exact?** Yes. addedText and removedText list the sentences, one per line.

### Related Actors

- [Domain Intelligence Lookup](https://apify.com/transparent_meteorite/domain-intelligence-lookup): registration, DNS and hosting facts for the vendors you monitor.
- [SSL Certificate & Subdomain Finder](https://apify.com/transparent_meteorite/ssl-certificate-subdomain-finder): map the subdomains and certificates of a vendor.
- [IPv4 & IPv6 Bulk IP Geolocation](https://apify.com/transparent_meteorite/ip-geolocation-bulk-lookup): locate the servers behind a vendor.

### Support

Found a bug or need a field? Open an issue on the Issues tab with the run URL and we will reply there.

### Changelog

- 0.1: first release. Privacy, terms and cookie policy diff against the Wayback Machine or the previous run, with the last-changed date.

# Actor input Schema

## `urls` (type: `array`):

Domains (stripe.com) or direct policy page URLs. For a domain the Actor finds the privacy policy and terms through the homepage footer links and common addresses.

## `docTypes` (type: `array`):

Which document types to find for each domain.

## `compareTo` (type: `string`):

wayback compares with an archived copy from the number of days below. lastRun compares with what this Actor saw the last time it ran (the first run falls back to Wayback).

## `compareDaysAgo` (type: `integer`):

For the Wayback comparison: use the archived copy closest to this many days ago.

## `minChangedSentences` (type: `integer`):

A document counts as changed when at least this many sentences were added or removed. Filters out typo fixes.

## `findLastChanged` (type: `boolean`):

Search the Wayback Machine for the date the current text first appeared. Turn off for faster runs.

## `maxTextChars` (type: `integer`):

Limit for addedText and removedText per row.

## `maxItems` (type: `integer`):

Upper limit of rows in this run. You are charged only for documents that were read and compared (status ok).

## Actor input object example

```json
{
  "urls": [
    "stripe.com",
    "github.com",
    "slack.com"
  ],
  "docTypes": [
    "privacy",
    "terms"
  ],
  "compareTo": "wayback",
  "compareDaysAgo": 365,
  "minChangedSentences": 1,
  "findLastChanged": false,
  "maxTextChars": 4000,
  "maxItems": 100
}
```

# Actor output Schema

## `changes` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "urls": [
        "stripe.com",
        "github.com",
        "slack.com"
    ],
    "docTypes": [
        "privacy",
        "terms"
    ],
    "minChangedSentences": 1,
    "findLastChanged": false,
    "maxItems": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("transparent_meteorite/privacy-policy-change-monitor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "urls": [
        "stripe.com",
        "github.com",
        "slack.com",
    ],
    "docTypes": [
        "privacy",
        "terms",
    ],
    "minChangedSentences": 1,
    "findLastChanged": False,
    "maxItems": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("transparent_meteorite/privacy-policy-change-monitor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "urls": [
    "stripe.com",
    "github.com",
    "slack.com"
  ],
  "docTypes": [
    "privacy",
    "terms"
  ],
  "minChangedSentences": 1,
  "findLastChanged": false,
  "maxItems": 100
}' |
apify call transparent_meteorite/privacy-policy-change-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,transparent_meteorite/privacy-policy-change-monitor"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/2OXrYTVaMdKoLQMdf/builds/wpkIaCQLRGOknHxXB/openapi.json
