Free · No sign-up · Nothing stored
See what your health-care website tells advertisers
For privacy, marketing and web teams at hospitals, clinics, behavioral-health and telehealth providers: find out which advertising and tracking services receive data from your site, and whether they learn what kind of care a visitor was looking for.
Starting…
We open the home page, a typical service page and the address you entered in up to five fresh browsers: no choice, after “Accept”, after “Reject”, with Global Privacy Control, and a direct visit to a service page. We never fill in forms.
What we check
- Before and after the cookie choiceNo choice, after “Accept”, after “Reject”, and with the Global Privacy Control signal.
- Who receives dataAdvertising, analytics, session-replay, call-tracking and chat services.
- What they learnPage addresses or titles that name a condition, procedure or medication.
How it works
- A fresh headless Chrome browser opens the site with no cookies. It only moves the mouse and scrolls; it does not click links or fill in forms.
- It records every request to known advertising, analytics, session-replay, call-tracking and chat-widget services (Meta, Google, Microsoft, TikTok, LinkedIn and about 70 others), and checks whether page addresses or titles that name a condition or treatment are sent along.
- If a cookie banner is shown, fresh browsers click “Accept” and then “Reject” and repeat the visit, so you can compare. Banner handling uses the open-source DuckDuckGo autoconsent rules.
- Another visit turns on Global Privacy Control, the opt-out signal sent by privacy-focused browsers.
- A separate fresh browser opens a service page directly, as a visitor arriving from an ad or a search result would. Some tools, such as call tracking, record only the page a visitor lands on first.
- Trackers hidden behind the site’s own subdomains (CNAME) are uncovered by checking DNS, using the open AdGuard list.
- Nothing is stored: the address and report are kept in memory for 10 minutes so this page can show them, then deleted. This page itself uses no trackers, cookies or third-party scripts.
The same engine is available as an open-source command-line tool (MIT licence) for checking your own site in CI.
Built by Denis Alekseev as an independent research project. Contact: research@healthpixelcheck.org