Pulse review queue, PII, and expected-behavior whitelist
Pulse scans are public, but visitor email, IP hash, and referrer are never exposed. A review queue catches unexpected findings before they show as failures.
Quick answer#
Pulse scan scores and issues are public. The visitor's email, IP hash, referrer, and user agent are private — only the scan owner and backend can see them.
What's public vs private#
Expected-behavior whitelist#
Where to find it in Lemwatch#
/pulse — scan URL. Admins see the review queue at /admin/pulse-review.
FAQ#
Can I make a Pulse scan private?#
No — Pulse is a public tool. For private monitoring, claim the site into your dashboard.
How long are scans kept?#
Scored data indefinitely; PII fields auto-purge on a rolling window.
Related#
Related Articles
What is Lemwatch Pulse?
Pulse is a free public health scanner — anyone can drop in a URL and get a graded uptime, performance, security, and SEO snapshot in seconds.
How to read your Pulse scan report
The Pulse report grades four pillars (uptime, performance, security, SEO), each with drill-downs. Grades are A–F using the same weights as the paid product.
How to claim and share a Pulse scan
Claim a Pulse scan to convert it into a monitored site in your Lemwatch dashboard. Share the public scan URL with a client to prove a problem exists.
What is the Answers Hub?
The Answers Hub is a public Q&A library that mirrors the questions people ask about monitoring, uptime, and site health.