# The Artifact Machine Privacy & Consent Scanner (`artifact-machine/artifact-machine-privacy-consent-scanner`) Actor

Check cookie consent banners, GDPR/CCPA signals, and privacy policy presence.

- **URL**: https://apify.com/artifact-machine/artifact-machine-privacy-consent-scanner.md
- **Developed by:** [The Artifact Machine](https://apify.com/artifact-machine) (community)
- **Categories:** Marketing, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / privacy and consent scan report

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## The Artifact Machine Privacy & Consent Scanner

An HTTP-based artifact that checks every privacy and consent compliance signal on a page: cookie consent banners, GDPR/CCPA signals, tracking scripts, consent mode, and privacy policy presence.

Use this Actor before a site launch, privacy compliance audit, or competitive privacy assessment. It gives teams a structured privacy analysis with prioritized issues ranked by severity.

Pulled from The Artifact Machine: generated, tested, and cleaned up by a human.

### What It Checks

- **Cookie consent banner**: detection, consent management platform (CMP) identification
- **Consent dark patterns**: pre-checked optional cookies, missing reject button
- **Tracking scripts**: Google Analytics, GTM, Facebook Pixel, Hotjar, and 10+ other trackers
- **Google Consent Mode**: detection, v1 vs v2 signals, ad\_storage and analytics\_storage parameters
- **Privacy links**: privacy policy, cookie policy, terms of service, Do Not Sell / CCPA opt-out
- **Compliance signals**: GDPR, ePrivacy, CCPA indicators, GPC meta tag
- **Forms**: PII collection detection (email, phone, name fields)

### Best For

- privacy compliance audits
- pre-launch consent checks
- GDPR and CCPA readiness assessments
- competitive privacy benchmarking
- agency client compliance diagnostics

### Input

```json
{
  "url": "https://example.com"
}
```

### Output

The Actor writes one dataset item and an `OUTPUT` key-value record with:

- cookie consent banner analysis and CMP detection
- tracking script inventory and count
- privacy link presence (policy, terms, cookie, Do Not Sell)
- Google Consent Mode detection and version identification
- compliance score and composite privacy score
- prioritized issues with severity, impact, and how-to-fix guidance
- indicators of what requires a full browser for deeper analysis

### Limits

- This Actor analyzes a single page per run from HTTP HTML alone.
- It does not use a browser, so JavaScript-rendered consent banners and CMP scripts that inject content dynamically may not be detected reliably.
- Window-global checks (OneTrust, Cookiebot, CMP objects) require a browser and are skipped.
- Pre-checked checkbox detection is limited to HTML source analysis.
- Some sites may block automated requests differently from real browsers.

### Pricing

Use pay-per-event pricing based on completed scans rather than per issue. Suggested starting price: `$1.00` to `$2.00` per completed privacy scan after private runtime cost is measured.

# Actor input Schema

## `url` (type: `string`):

The full page URL to scan for privacy and consent signals.

## Actor input object example

```json
{
  "url": "https://example.com"
}
```

# Actor output Schema

## `results` (type: `string`):

Default dataset items. Each item contains the target URL, cookie consent signals, tracking script inventory, privacy links, compliance assessment, and flagged issues.

## `summary` (type: `string`):

The same single-run summary stored as the OUTPUT key-value record.

# 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 = {
    "url": "https://example.com"
};

// Run the Actor and wait for it to finish
const run = await client.actor("artifact-machine/artifact-machine-privacy-consent-scanner").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 = { "url": "https://example.com" }

# Run the Actor and wait for it to finish
run = client.actor("artifact-machine/artifact-machine-privacy-consent-scanner").call(run_input=run_input)

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

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

```

## CLI example

```bash
echo '{
  "url": "https://example.com"
}' |
apify call artifact-machine/artifact-machine-privacy-consent-scanner --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=artifact-machine/artifact-machine-privacy-consent-scanner",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/MNsfNJY3StPBbW7hc/builds/gHyA4TjESByk13Zl5/openapi.json