HeatCheck

Privacy Policy

Effective July 2026. This is a draft policy for the pre-launch site and will be finalized before general availability.

Who we are

HeatCheck is a lead-heat scoring product operated as an independent product powered by Waldo. HeatCheck reaches Waldo only over its API and is hosted independently.

Controller and processor

For the contacts you score, you are the data controller and HeatCheck is a processor acting on your instructions. We process your customers’ and prospects’ engagement data to compute a heat score on your behalf. For your own account and users, HeatCheck is the controller.

What we process

Publicly observable engagement signals (such as LinkedIn post engagement), webinar registration and attendance, gated-content submissions, and page visits by known contacts, resolved to the contact records in your CRM. We compute a score, a tier and a per-signal audit trail from these.

The 90-day signal window

Signals are held on a rolling 90-day window for the purpose of scoring. Signals older than the window are aged out of the active score.

First-party cookies

Where HeatCheck contributes to page-visit scoring, it relies on first-party analytics data associated with known contacts. This is not strictly-necessary-only cookie usage, and it is disclosed here so your own cookie notice can reflect it.

Processors we use

HubSpot (the CRM we read from and write to), the Waldo API (the platform HeatCheck runs on), and your connected webinar platform. Each is used only to deliver the scoring service.

Your rights

Because HeatCheck acts as a processor for the contacts you score, data-subject requests are handled through you as the controller. For your own account data, contact us and we will action requests as controller.

Security

HeatCheck reaches Waldo only over the API, keeping it isolated from Waldo infrastructure. See the security page for our data-handling posture.

Contact

Questions about this policy can be sent to privacy@getheatcheck.fyi.