Methodology
How PrivacySignalMonitor checks visible website privacy signals.
PrivacySignalMonitor performs technical monitoring of public website signals. It is designed to help teams notice changes over time, not to provide legal advice, compliance certification, or consent management.
What is monitored
Visible technical signals, captured repeatedly.
The monitoring workflow focuses on signals that can be observed from public website output and compared across scans. Reports are intended as operational review cues.
Report logic
Reports show evidence, review cues, and changes.
A report can summarize the current scan, detected visible signals, third-party vendors, script hosts, visible cookies, selected pages, findings, severity, confidence, and previous-scan changes. The report is meant to support internal technical review after site updates, releases, plugin changes, tag changes, or vendor changes.
Boundaries
What the scan does not do.
- The scan does not provide legal advice or determine legal compliance.
- The scan does not replace a CMP or manage consent choices.
- The scan does not certify GDPR, CCPA, CPRA, ePrivacy, or other privacy-law compliance.
- Some signals may vary by geography, user state, browser state, scripts, blocking, timing, or website configuration.
- Secondary page checks are intentionally lightweight and same-domain only.
Use methodology pages with scan evidence, not as legal proof.
PrivacySignalMonitor helps teams organize technical monitoring evidence. Legal interpretation, policy drafting, compliance decisions, and consent configuration should be handled separately by qualified professionals or the tools responsible for those workflows.