# GDPR monitoring that speaks up only when it matters.

URL: https://privacyboard.io/features/gdpr-compliance-monitoring

Privacyboard keeps checking what your privacy records depend on: your website, opened in a real browser; your code on GitHub, at each push; the apps your team signs in to with Google Workspace, every day; your vendors’ breaches, agreements, subprocessors and Data Privacy Framework status; and your legal deadlines. A tool that appears on your site, in your code or in your Workspace, or leaves it, comes as a change ready to approve in one click; anything else arrives in one email with a link to fix it. On the 1st of each month, a summary says what was checked.

- **Website**: Checked in a real browser every week, every day on Business
- **Code**: Every push that changes a dependency file, on Pro with GitHub
- **Google Workspace**: Apps people sign in to with Google, checked every day on Pro
- **Vendors**: Breaches and exploited vulnerabilities daily, agreements and DPF status weekly
- **Deadlines**: Request replies and incident notifications reminded on every plan
- **Plan**: Pro and Business; deadline reminders and vendor alerts in the app on Free

## What is GDPR compliance monitoring?

GDPR compliance is not a document written once. Article 5(2) asks you to be able to show that you comply at any time, and what you recorded depends on things that change without warning: a marketing tag added to your website, a vendor that updates its subprocessors or lets its certification lapse, a request whose one-month deadline comes closer.

Compliance monitoring means checking those things on a schedule and acting on what changed. Privacyboard runs the checks for you and stays quiet when nothing changed, so an email from it always means there is something to look at.

## How it works

1. **Add your website and vendors**: Your website comes from your privacy center or cookie banner, and the vendors in your list are watched from the day you add them.
2. **Approve what changed**: A new tool on your site or in your code arrives as a change ready to approve on your Overview, everything it touches listed. A vendor’s changed agreement, a lapsed certification or a deadline coming up arrives once, with a link to the page where you deal with it.
3. **Read the monthly summary**: On the 1st of each month, a summary says what was checked and what changed, even when nothing did. The Overview shows the same, and the status report PDF shows how what needs your attention moved.

## What is included

- **Your code, at each push**: With GitHub connected on Pro, a push that adds an SDK to a dependency file proposes its vendor, and one that removes it proposes the removal. Read-only, dependency files only.
- **Your website, in a real browser**: Your home page is opened untouched, after “Reject all” and after “Accept all”. A tool that loads before the choice or a new cookie is reported once, with the fix.
- **Vendor breaches and vulnerabilities**: Public breach reports and actively exploited vulnerabilities are matched to your vendors every day and checked by a person. One click turns an alert into a drafted incident.
- **Agreements and subprocessors**: Each week, the processing agreement page and subprocessor list of known vendors are read again. When the text changes, you are told what changed.
- **Data Privacy Framework status**: US vendors your transfers rely on are checked against the official list every week. When a certification lapses, you are told at once.
- **Deadlines and reviews**: Request replies and the 72-hour breach notification are reminded the day they come up. Documents to validate again and vendor and DPIA reviews come in one email on Mondays.
- **A monthly summary**: What was checked, what changed and how what needs your attention moved, by email on the 1st and on the Overview, with a status report PDF one click away.

## Why it has to keep running

- **GDPR, Article 5(2)**: Accountability: the controller must be able to demonstrate compliance, so its records have to stay true over time.
- **GDPR, Article 24(1)**: The measures a controller takes must be reviewed and updated where necessary.
- **GDPR, Article 28(1)**: Only processors that provide sufficient guarantees may be used, which is worth checking again when they change.
- **ePrivacy Directive, Article 5(3)**: Trackers that are not strictly necessary need consent first, including those added to a website after its banner was set up.

The checks report what they find; they are not an audit or a certification, and the website check covers your home page. You decide what to do with each finding.

## Frequently asked questions

### How often is my website checked?

Every week on Pro and every day on Business, in a real browser. You can also run the check yourself at any time from Cookies → Scan your site.

### Will I get a lot of emails?

No. A website finding is sent once and not again within 30 days. Reminders other than legal deadlines are grouped in one email on Monday mornings, and the summary comes on the 1st of the month.

### Who checks the vendor alerts?

Changes to agreement pages and subprocessor lists, and breach and vulnerability reports, are checked by a person at Privacyboard before customers hear about them, so a false match does not reach you.

### What does the Free plan include?

Reminders of request deadlines and incident notifications, the website check when you run it yourself, and vendor alerts shown in the app. The automatic checks, the other reminders and the monthly summary come with Pro and Business.

### Who receives the emails?

Owners and admins, unless they chose otherwise in Settings → My account. Each person picks deadline reminders, the Monday digest and the monthly summary separately.

## Related

- [Cookie banner](https://privacyboard.io/features/cookie-consent-banner)
- [Subprocessor list](https://privacyboard.io/features/subprocessor-and-vendor-list)
- [MCP connector for your AI](https://privacyboard.io/features/mcp-connector)
