Example report structure

Privacy scan report example

A PrivacySignalMonitor report is designed to show visible website privacy signals, review cues, vendor evidence, script hosts, visible cookies, scanned pages, and changes between scans.

Start 14-day free trialSee the scan workflow

Technical monitoring only. Not legal advice, not a CMP, and not a compliance certification tool.

What this page covers

Many website privacy checks are one-time snapshots. A useful operational report should show what was visible, what changed, and what should be reviewed internally without claiming legal compliance.

Who this is for

This page is for teams that want to understand what a technical privacy signal report includes before using a recurring monitoring workflow.

Visible privacy signals monitored

Overall technical scan score and grade.
Severity and confidence labels for visible review cues.
Privacy policy link presence.
Cookie banner indicator status.
Detected tracker vendors and third-party script hosts.
Visible cookies after browser page load when available.
Pages scanned and secondary page evidence.
Previous scan comparison and change summary.

Common review cues

  • High review cue: no visible cookie banner indicator while third-party vendors are detected.
  • Medium review cue: privacy link signal changed between scans.
  • Vendor evidence: a new ads or analytics provider appears.
  • Script evidence: a third-party host appears after a release.
  • Cookie evidence: visible cookies after load differ from a previous scan.

Operational workflow

  1. 1Add the website or client site that should be monitored.
  2. 2Run a technical scan to capture visible privacy-related signals.
  3. 3Review privacy links, cookie banner indicators, scripts, vendors, cookies, and scanned pages.
  4. 4Compare the latest scan with the previous scan to identify changes.
  5. 5Use the report as an internal review cue after releases, plugin updates, vendor changes, or website redesigns.

Boundaries and limitations

PrivacySignalMonitor is a technical monitoring tool for visible website signals. It does not provide legal advice, does not certify compliance, does not replace a CMP, does not verify legal consent validity, and does not guarantee that a website satisfies GDPR, CCPA, CPRA, ePrivacy, or any other privacy regulation.

Frequently asked questions

Is the report a legal audit?

No. It is a technical report for visible website privacy signals and operational review.

What does the report help teams do?

It helps teams see what changed, identify visible review cues, and decide what needs internal follow-up.

Does the report certify compliance?

No. It does not certify compliance with any privacy law or standard.

Does the report include vendor evidence?

Yes. It can list detected vendor signals and third-party script hosts visible during the scan.

Does the report compare scans over time?

Yes. Saved scans allow the product to show scan-to-scan changes.

Can the report be used after website releases?

Yes. It is especially useful after releases, plugin updates, tag changes, redesigns, or vendor additions.