# GDPR Enforcement Tracker — Fines & Penalties (`jungle_synthesizer/gdpr-enforcement-tracker-fines-scraper`) Actor

Every GDPR fine and penalty recorded by the Enforcement Tracker, in one dataset: authority, amount, articles cited, sector, and the decision link, for every EU/EEA/UK enforcement action on record.

- **URL**: https://apify.com/jungle_synthesizer/gdpr-enforcement-tracker-fines-scraper.md
- **Developed by:** [BowTiedRaccoon](https://apify.com/jungle_synthesizer) (community)
- **Categories:** Business, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.80 / 1,000 record scrapeds

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

## GDPR Enforcement Tracker Fines Database Scraper

Scrape the complete case database from the [GDPR Enforcement Tracker](https://www.enforcementtracker.com/), the reference log of GDPR fines issued by EU, EEA, and UK data protection authorities since 2018. Returns one record per case — authority, fine amount, articles cited, sector, and the underlying decision link — for the entire ~3,300-case corpus in a single run.

***

### GDPR Enforcement Tracker Scraper Features

- Returns the **full case corpus** in one run — no pagination to configure, no date range to guess at.
- Extracts the fine amount in EUR where the authority disclosed one, and keeps the raw figure (or marks it unknown) for the cases that didn't.
- Captures every GDPR article cited in the decision, not just a headline violation category.
- Includes the authority, the sector classification, and the fined entity (controller or processor) on every row.
- Links back to both the source DPA decision and the case's own Enforcement Tracker page, so you can verify anything downstream.
- `maxItems` caps the run if you only need a sample — useful for testing before you pull the whole set.

***

### Who Uses GDPR Fine Data?

- **Privacy counsel** — benchmark a client's exposure against comparable fines by sector and article.
- **Cyber and E\&O underwriters** — price regulatory risk using actual enforcement history instead of headlines.
- **Privacy-tech vendors** — feed real enforcement cases into a risk-quantification or compliance product.
- **Compliance teams** — track which GDPR articles get enforced most, and against which industries.
- **Researchers and journalists** — analyze enforcement trends across authorities and member states over time.

***

### How GDPR Enforcement Tracker Scraper Works

1. The actor requests the Enforcement Tracker's case database page.
2. It reads the embedded case records straight off that page and maps each one to a clean, named field set.
3. Every case — fine amount, authority, articles, sector, source link — gets saved as one dataset row.
4. Set `maxItems` to cap how many cases come back; leave it at its default for the whole corpus.

***

### Input

```json
{
  "maxItems": 10
}
```

| Field      | Type    | Default | Description |
|------------|---------|---------|-------------|
| `maxItems` | Integer | 10      | Maximum number of cases to return. The full corpus is roughly 3,300 cases and arrives in a single request — raise this to pull everything. |

***

### GDPR Enforcement Tracker Scraper Output Fields

```json
{
  "etid": "ETid-1",
  "country": "Austria",
  "authority": "Austrian Data Protection Authority (dsb)",
  "fine_amount_eur": 4800,
  "fine_amount_raw": "4800",
  "decision_date": "2018-12-09",
  "controller_processor": "Betting place",
  "sector": "Industry and Commerce",
  "quoted_articles": ["Art. 13 GDPR"],
  "violation_type": "Insufficient fulfilment of information obligations",
  "source_url": "https://www.dsb.gv.at/documents/22758/116802/Straferkenntnis+DSB-D550.038+0003-DSB+2018.pdf",
  "detail_url": "https://www.enforcementtracker.com/ETid-1",
  "scraped_at": "2026-10-15T10:14:05.867Z"
}
```

| Field                  | Type            | Description |
|------------------------|-----------------|--------------|
| `etid`                 | String          | Stable case id from the tracker (`ETid-####`). |
| `country`              | String          | Country of the issuing data protection authority. |
| `authority`            | String          | The issuing DPA (CNIL, Garante, AEPD, ICO, dsb, and so on). |
| `fine_amount_eur`      | Number | null  | Fine amount in EUR, where the tracker has a figure on record. |
| `fine_amount_raw`      | String          | The fine amount as a string, or the literal `"unknown"` when no figure is on record — never silently dropped. |
| `decision_date`        | String          | Decision date as published — a full date, a year only, or `"Unknown"`. |
| `controller_processor` | String          | The fined entity (controller or processor). |
| `sector`               | String          | Industry or sector classification the tracker assigns. |
| `quoted_articles`      | Array\<String> | GDPR articles cited in the decision. |
| `violation_type`       | String          | The violation classification the tracker assigns. |
| `source_url`           | String          | The DPA decision or press release the tracker links, where available. |
| `detail_url`           | String          | The case's own page on the Enforcement Tracker. |
| `scraped_at`           | String          | ISO-8601 timestamp of when this record was scraped. |

***

### FAQ

#### How do I scrape GDPR fines from the Enforcement Tracker?

GDPR Enforcement Tracker Scraper needs no input beyond an optional `maxItems` cap. Run it, and it returns the case database as structured rows — fine amount, authority, articles cited, and the rest.

#### How much does this actor cost to run?

It's billed per record returned. Because the entire corpus arrives in one pull, pulling all ~3,300 cases costs about the same per record as pulling ten.

#### What data can I get from the GDPR Enforcement Tracker?

Every recorded case: the issuing authority, the country, the fine amount (where disclosed), the GDPR articles cited, the sector, the fined entity, the decision date, and links back to the original source and the tracker's own case page.

#### Can I filter by country or sector?

Every case already carries both a `country` and a `sector` field, so narrowing to the ones you want is a one-line step once the dataset lands — no extra run parameter needed.

#### Do I need an account or API key for the Enforcement Tracker?

No. GDPR Enforcement Tracker Scraper runs standalone — point it at Apify and it returns the case data directly.

***

### Need More Features?

Need a different field, a country/sector pre-filter, or something else entirely? [File an issue](https://console.apify.com/actors/issues) or get in touch.

### Why Use GDPR Enforcement Tracker Scraper?

- **Complete corpus, every run** — no pagination settings to tune, no risk of stopping halfway through the dataset.
- **Honest about gaps** — when the tracker has no disclosed fine amount, you get an explicit `"unknown"`, not a silently blank field pretending to be zero.
- **Source-linked** — every row carries both the original DPA decision link and the tracker's own case page, so downstream verification doesn't require a second lookup.

# Actor input Schema

## `sp_intended_usage` (type: `string`):

What will this data feed? E.g. lead lists, KYB checks, price tracking.

## `sp_improvement_suggestions` (type: `string`):

Provide any feedback or suggestions for improvements.

## `sp_contact` (type: `string`):

We'll personally help with your use case. No spam.

## `resumeCursor` (type: `string`):

Leave empty for a fresh crawl. To CONTINUE a previous run where it stopped — without paying again for records you already received — paste the `resumeCursor` value from that run's Output (the run's OUTPUT key). Resume promptly: the previous run's data expires with your account's retention window (free tier: your ~10 most recent runs).

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

Maximum number of cases to return (the full corpus is ~3,340 and arrives in one request)

## Actor input object example

```json
{
  "sp_contact": "Share your email here...",
  "maxItems": 10
}
```

# Actor output Schema

## `results` (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 = {
    "sp_contact": "Share your email here...",
    "maxItems": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("jungle_synthesizer/gdpr-enforcement-tracker-fines-scraper").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 = {
    "sp_contact": "Share your email here...",
    "maxItems": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("jungle_synthesizer/gdpr-enforcement-tracker-fines-scraper").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 '{
  "sp_contact": "Share your email here...",
  "maxItems": 10
}' |
apify call jungle_synthesizer/gdpr-enforcement-tracker-fines-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jungle_synthesizer/gdpr-enforcement-tracker-fines-scraper"
        }
    }
}
```

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/WYvygwoyk0HSlmGiK/builds/CoKu29WP5eRSwdLXH/openapi.json