High RiskTracking RiskUpdated 2026-06-01

Website Tracking Risk

OCR guidance has clarified that standard marketing and analytics tools deployed on healthcare websites may capture PHI through URL parameters, form submissions, and behavioral data linked to health conditions. Organizations should review all tracking deployments on patient-facing web properties.

Watchlist Stats

Risk Score78/100
Live Vendors17
Risk LevelHigh

Who Should Review

Marketing directors, compliance officers, legal counsel, and web technology teams.

Why This Watchlist Matters

Marketing pixels on appointment pages may capture health-related intent as PHI.

Call tracking tools may record patient conversations without proper consent or BAA.

Website analytics tools can collect IP addresses correlated with health conditions.

Session replay and heatmap tools capture form field entries that may include PHI.

Vendor Table — 17 of 17 vendors

VendorCategoryBAA StatusApproval TierPHI RiskAI RiskLast Verified
HubSpot AIMarketing AutomationRestricted / Review Required2026-09-30
Dialpad HealthcarePhones & Call TrackingVerify DirectlyConditional / Verify BAAHighHigh2026-09-30
GoTo Connect HealthcarePhones & Call TrackingVerify DirectlyConditional / Verify BAAHighLow2026-09-30
RingCentral for HealthcarePhones & Call TrackingVerify DirectlyConditional / Verify BAAHighMedium2026-10-01
Mango VoicePhones & Call TrackingVerify DirectlyConditional / Verify BAAHighLow—
KlaviyoMarketing AutomationBAA Not FoundNot RecommendedHighHigh2026-09-30
HubSpot HealthcareMarketing AutomationBAA Not FoundNot RecommendedHighHigh2026-09-30
ActiveCampaign HealthcareMarketing AutomationVerify DirectlyConditional / Verify BAAHighMedium2026-09-15
Act-OnMarketing AutomationVerify DirectlyConditional / Verify BAAHighMedium2026-05-21
8x8 HealthcarePhones & Call TrackingVerify DirectlyConditional / Verify BAAHighHigh2026-09-30
Ruler AnalyticsAnalytics & TrackingVerify DirectlyRestricted / Review RequiredHighLow2026-05-22
Genesys Cloud CXPhones & Call TrackingVerify DirectlyApproved With RestrictionsHighHigh2026-05-22
Piwik PROAnalytics & TrackingVerify DirectlyApproved With RestrictionsMediumLow2026-05-22
CallTrackingMetricsPhones & Call TrackingVerify DirectlyApproved With RestrictionsHighMedium2026-05-22
Five9Phones & Call TrackingVerify DirectlyApproved With RestrictionsHighHigh2026-05-22
DemandforceMarketing AutomationVerify DirectlyConditional / Verify BAAHighLow2026-05-21
BirdeyeMarketing AutomationVerify DirectlyApproved With RestrictionsHighMedium2026-05-22

Recommended Actions

Verify BAA before PHI use

Contact the vendor to confirm current BAA terms and scope before processing any PHI.

Restrict PHI entry

Implement technical or administrative controls to prevent PHI from entering unapproved systems.

Require legal review

Engage legal counsel to review data processing agreements and contract terms.

Require security review

Conduct a security assessment before deployment in PHI-adjacent workflows.

Disable tracking where needed

Remove or reconfigure tracking pixels and analytics tools on pages where PHI may be present.

Document consent workflow

Establish and document patient or staff consent processes for relevant data collection.

Review configuration settings

Verify that vendor configuration meets HIPAA requirements for your specific deployment.

Train staff before approval

Provide governance and usage training before allowing staff access to the vendor platform.

Add to internal monitoring

Include this vendor in your organization's recurring vendor risk review cycle.

Governance Checklist

Identify PHI exposure paths for this vendor category

Confirm BAA availability with the vendor directly

Review vendor contract terms and data processing agreements

Review data retention and deletion settings

Review AI training data usage clauses

Review user access controls and audit logging

Document approved use cases and restrictions

Train staff on usage restrictions before deployment

Set a recurring review date based on risk classification

Subscribe to Vendor Alerts

Be notified of watchlist changes and risk updates.

No commitment required. Unsubscribe at any time.

Frequently Asked Questions

Not necessarily — but standard configurations of many analytics tools on healthcare websites may create HIPAA exposure. OCR has issued guidance on tracking technologies. Each deployment should be evaluated against your specific web properties and patient data flows.

Explore All VNDRIQ Watchlists

Monitor AI risk, BAA status, tracking exposure, and vendor governance across your technology stack.

VNDRIQ watchlists are based on available public information and internal review. Being on a watchlist does not mean a vendor is unsafe — it means active governance attention is recommended. This is not legal or compliance advice. Verify vendor BAA status and HIPAA program scope directly with each vendor.