Hearthly T3 Thermostat
Connected device · Hearthly Home Co. · HT-T3
- Device model
- HT-T3
- Publisher
- Hearthly Home Co.
- Platform
- Hearthly firmware
- Versions
- Firmware 2.7.0
- Scan date and region
- Aug 17, 2026 · EU (Ireland lab)
- Consent state
- Default setup; optional "Usage insights" on
- Scan method
- Lab device — authorized network capture
- Coverage
- Partial · methodology 0.9
Observed connections (3 endpoints, 3 companies)
Each row is a transmission observed in the tested session, the operator identified for that endpoint, and the information seen in requests. This table is the accessible equivalent of the data-sharing map.
| Observed endpoint | Identified operator | Role | Scenarios | Information observed |
|---|---|---|---|---|
api.orbitalcloud.exampleContents not readable | Orbital Cloud Declared | Content delivery and infrastructure |
| Network information only; contents unknown |
collect.tallymark.example | Tallymark Analytics Declared | Analytics and measurement |
| Usage & viewing, Sensitive context, Network |
cdn.nimbuscdn.example | Nimbus Edge Declared | Content delivery and infrastructure |
| Network |
Documented relationships
Ownership and business relationships come from public records. They do not show that data from this product moved between these companies.
Adreach Exchange → Tallymark Analytics
DeclaredDocumented business relationship
Source: Tallymark integrations page lists Adreach · May 14, 2026
Unknown Further sharing unknown
TrustIQ observes what leaves the product. What recipients do afterward, including onward sharing, is outside what this scan can see.
Open questions
Orbital Cloud
- Orbital Cloud hosts services for many customers. Which customer operates the contacted subdomain, and for what purpose, is not established.
Nimbus Edge
- Content delivery contact establishes where files were fetched from, not why. Purpose is attributed to the publisher, not to Nimbus Edge.