Reporting a security vulnerability to Thermonova

We build heat pumps, the controllers and internet gateways inside them, and the cloud services and apps that operate them. If you have found a security vulnerability in any of these, we want to hear from you, and this page explains how we handle your report.

Scope

In scope

  • Thermonova heat pumps and their controller software
  • The Thermonova IoT gateway (hardware and application)
  • The Thermonova Portal and apps (portal.thermonova.com, my.thermonova.com and their staging hosts)
  • The Thermonova cloud backend (backend.thermonova.com) and the analytics services
  • The documentation site (docs.thermonova.com)
  • Open source and third-party components integrated in the above (we report those upstream as well, see below)

Out of scope

  • Websites and services run by third parties for us, unless the vulnerability is in our own configuration or content
  • Physical attacks on installed equipment, social engineering of our staff or customers, and denial-of-service attacks (see "what not to do")
How to report

Choose the channel that suits you.
A person reads every one of them.

E-mail

security@thermonova.com. To encrypt your report, use our PGP key: https://portal.thermonova.com/.well-known/pgp-key.txt, fingerprint 5F03 F84C 907F 7A07 8BD9 E5EA 6482 46D8 70CB 2CBA.

Telephone

+45 6060 2060, working days 09:00 to 16:00 Copenhagen time.

Report Form

The report form in the Thermonova Portal.

Please tell us what product or service is affected, the version if you know it, what you observed and how to reproduce it, and whether you believe the vulnerability is already being exploited. Tell us how you would like to be contacted and whether you have a disclosure deadline of your own.

What we commit to

We acknowledge your report within 3 working days of receiving it.
We give you a triage verdict within 10 working days

Accepted, duplicate of a known issue, not a vulnerability, or out of scope

While your report is open we send you a status update at least every 14 days.
We credit you in our advisory if you wish.

Tell us the name to use, or that you prefer to stay anonymous.

Disclosure

We practise coordinated disclosure. Our aim is to fix accepted vulnerabilities within 90 days of the report and to publish an advisory when a fix or mitigation is available to users. If a fix takes longer, we agree a publication date with you rather than leave the report open indefinitely. We ask that you do not publish details before the agreed date.

Where the law requires it, we report actively exploited vulnerabilities and severe incidents to the authorities on their timelines (Regulation (EU) 2024/2847, Article 14). That reporting is independent of, and does not delay, our communication with you.

When a vulnerability is in a third-party or open source component we use, we report it to that component's maintainers and share any fix we develop with them.

Safe harbour

If you follow this policy, we consider your research authorised. We will not pursue or support legal action against you for good-faith security research that stays within the rules below, and we will not report you to law enforcement for it. If a third party takes action against you for research conducted under this policy, we will make it known that your research was authorised.

What not to do

  • Do not run denial-of-service tests or anything that degrades service for our customers.
  • Do not access, modify or delete data that is not yours. If you come across customer data, stop, note what you saw, and report it.
  • Do not attempt physical attacks on installed heat pumps or gateways, or social engineering of Thermonova staff, installers or customers.
  • Do not leave persistent access, backdoors or malware on any system.
  • Do not demand payment as a condition of reporting. We do not run a bug bounty programme.

Our details

Thermonova A/S, Nordvestvej 4, 9600 Aars, Denmark, CVR 38132369. This policy is governed by Danish law. Version 1, published 9 October 2026. Reviewed at least once a year. Our security.txt files (RFC 9116) at /.well-known/security.txt on each of our domains point to this page.