Heartbeat
heartbeat.chat · Customer communities · checked 2026-09-03
Rank 5 of 18 in Customer communities, where the median is 35.5.
- 6 found
- 6 not found
- 0 not measured
We measured 12 of 12 criteria for Heartbeat on 2026-09-03. We found 6 with a source and did not find 6 at the addresses we checked. That is a transparency score of 52 out of 100, band D.
Overview
Transparency labelsaas-ranking.com
Heartbeat
- A
- B
- C
- D
- E
- F
Published commitments5 of 9 found
- foundData processing agreement×3
- not foundSubprocessor list×3
- not foundData location stated×3
- foundStatus page with history×2
- foundPublic pricing×2
- foundNotice before subprocessors change×2
- not foundCertifications named×1
- not foundUptime SLA with a figure×1
- foundNamed privacy contact×1
Measured behaviour1 of 3 found
- foundHTTPS enforced with HSTS×2
- not foundNo third-party tracking before consent×2
- not foundsecurity.txt (RFC 9116)×1
Checked 2026-09-03. Every line links the page we found it on. A cross means we found nothing at the addresses we checked, not that the vendor has no such document. A transparency score, not a product rating.
We do not issue badges: a badge is the first step towards a paid placement, and there is none here. The SVG is a document with the date in it, for your own files.
The label is the whole measurement in one object: every criterion with its weight, the band, and the date. Public transparency score, not a product or security rating.
Every line in it links the page we found the result on, or lists the addresses we checked. A cross means we found nothing there, not that Heartbeat has no such document.
Gaps, heaviest first
Subprocessor list
weight 3 of 3No subprocessor list found.
Checked 7 addresses on 2026-09-03.
Show the 7 addresses we checked
https://heartbeat.chat/legal/subprocessors– reached, no match (HTTP 404)https://heartbeat.chat/subprocessors– reached, no match (HTTP 404)https://heartbeat.chat/sub-processors– reached, no match (HTTP 404)https://heartbeat.chat/legal/sub-processors– reached, no match (HTTP 404)https://heartbeat.chat/trust/subprocessors– reached, no match (HTTP 404)https://heartbeat.chat/privacy/subprocessors– reached, no match (HTTP 404)https://heartbeat.chat/legal/subprocessor-list– reached, no match (HTTP 404)
Data location stated
weight 3 of 3No statement about data location found.
Checked 7 addresses on 2026-09-03.
Show the 7 addresses we checked
https://heartbeat.chat/security– reached, no match (HTTP 404)https://heartbeat.chat/trust– reached, no match (HTTP 404)https://heartbeat.chat/legal/privacy– reached, no match (HTTP 200)https://heartbeat.chat/privacy– reached, no match (HTTP 200)https://heartbeat.chat/privacy-policy– reached, no match (HTTP 200)https://heartbeat.chat/compliance– reached, no match (HTTP 404)https://heartbeat.chat/legal/privacy-policy– reached, no match (HTTP 404)
No third-party tracking before consent
weight 2 of 3No consent-free first load found.
Checked 1 address on 2026-09-03.
Show the 1 address we checked
https://heartbeat.chat/– third-party requests before any interaction: ad.doubleclick.net, analytics.twitter.com, api.hubapi.com, capi-automation.s3.us-east-2.amazonaws.com, cdn.simpleicons.org, connect.facebook.net, cta-service-cms2.hubspot.com, ekr.zdassets.com, fonts.googleapis.com, fonts.gstatic.com, forms.hscollectedforms.net, googleads.g.doubleclick.net, heartbeat8933.zendesk.com, ip.conceptualhq.com, js.hs-analytics.net, js.hs-banner.com, js.hs-scripts.com, js.hsadspixel.net, js.hscollectedforms.net, js.hubspot.com, perf-na1.hsforms.com, px.ads.linkedin.com, randomuser.me, region1.analytics.google.com, snap.licdn.com, static.ads-twitter.com, static.zdassets.com, stats.g.doubleclick.net, t.co, track.hubspot.com, www.clickcease.com, www.facebook.com, www.google.com, www.google.de, www.googleadservices.com, www.googletagmanager.com
Certifications named
weight 1 of 3No named certification found.
Checked 6 addresses on 2026-09-03.
Show the 6 addresses we checked
https://heartbeat.chat/security– reached, no match (HTTP 404)https://heartbeat.chat/trust– reached, no match (HTTP 404)https://heartbeat.chat/trust-center– reached, no match (HTTP 404)https://heartbeat.chat/compliance– reached, no match (HTTP 404)https://heartbeat.chat/legal/security– reached, no match (HTTP 404)https://trust.heartbeat.chat/– The name "trust.heartbeat.chat" could not be resolved.
Uptime SLA with a figure
weight 1 of 3No uptime figure found.
Checked 6 addresses on 2026-09-03.
Show the 6 addresses we checked
https://heartbeat.chat/legal/sla– reached, no match (HTTP 404)https://heartbeat.chat/sla– reached, no match (HTTP 404)https://heartbeat.chat/legal/service-level-agreement– reached, no match (HTTP 404)https://heartbeat.chat/trust/sla– reached, no match (HTTP 404)https://heartbeat.chat/uptime– reached, no match (HTTP 404)https://heartbeat.chat/legal/uptime-sla– reached, no match (HTTP 404)
security.txt (RFC 9116)
weight 1 of 3No security.txt found.
Checked 1 address on 2026-09-03.
Show the 1 address we checked
https://heartbeat.chat/.well-known/security.txt– reached, no match (HTTP 404)
Evidence
The full source lists sit behind these two groups, so that the answer above stays readable.
Published, with a source 6
Data processing agreement
weight 3 of 3Published and readable without a login.
Source: https://www.heartbeat.chat/legal/dpa · checked 2026-09-03
Status page with history
weight 2 of 3A public status page with incident history.
Source: https://status.heartbeat.chat/ · checked 2026-09-03
Public pricing
weight 2 of 3Actual numbers on a public page.
Source: https://www.heartbeat.chat/pricing · checked 2026-09-03
HTTPS enforced with HSTS
weight 2 of 3HTTP redirects to HTTPS and the HSTS header is set.
Source: https://heartbeat.chat/ · checked 2026-09-03
Notice before subprocessors change
weight 2 of 3The vendor commits publicly to giving notice before the list changes.
Source: https://www.heartbeat.chat/legal/dpa · checked 2026-09-03
Named privacy contact
weight 1 of 3A data protection officer or a dedicated privacy address is named.
Source: https://www.heartbeat.chat/legal/privacy · checked 2026-09-03
History
Not enough completed runs yet to draw a line. The next runs fill this in.