Security and Data Handling
Energy data describes how a site actually runs. Before you hand it over, you are entitled to know where it will sit, who will see it, and when it gets deleted.
Last reviewed: August 2026
Scope
What we process, and what we do not
The platform handles three classes of data. Nothing outside these three classes is processed. Production or ERP data is handled only if you ask for it, and only within a scope agreed in writing.
In UK GDPR terms you remain the controller of this data. We act as processor and do only what your instructions and our contract allow.
- Class 1
Technical measurement data
Electrical quantities (kW, kWh, current, voltage, power quality), pressure, temperature, flow and equipment running states.
- Class 2
Site and asset definitions
Site name and location, device list, contracted capacity, tariff details.
- Class 3
User account details
Name, work email address, role. Nothing else personal is held.
The technical record
At a glance
- Hosting
- EU
- Finland · ISO/IEC 27001 certified data centre
- Dashboard and API
- TLS
- Encrypted end to end · certificates renew automatically
- Field link
- MQTT 8883
- TLS protected · separate credentials per site
- Password storage
- bcrypt
- Irreversible hash, never stored in plain text
- Authorisation
- 2 layers
- Role based and site based
- Backups
- daily
- Automatic · retained 30 days
Transfers
Where your data sits, in UK terms
Servers are in Finland, inside the European Economic Area. This matters for UK procurement: the UK recognises the EEA as providing an adequate level of protection, so personal data moving from the UK to our infrastructure needs no additional transfer safeguards.
One point we would rather state than have you discover: our support and engineering team works from Türkiye. Under UK GDPR, remote access from outside the UK counts as a transfer, and Türkiye does not hold a UK adequacy decision. Where personal data is in scope, an International Data Transfer Agreement can be put in place, with a transfer risk assessment alongside it.
If you would rather no data left your own network at all, that option exists too. See the on-premise section below.
Ownership
Your data belongs to you
This is the most important line on the page. On request, data is exported in a machine-readable format or permanently deleted.
Customer data is never shared with third parties, never used commercially, and never used in another customer’s analysis.
Energy data reveals a site’s production rhythm, shift pattern and capacity utilisation. That is precisely why we do not pool it, benchmark it against other customers, or use it to train models.
The life of a data point
- 01 Collected field → gateway Readings arrive over TLS from the site gateway; every site connects with its own credentials.
- 02 Stored EU · 30-day backup The database is closed to the internet; backups run daily and are kept for 30 days.
- 03 Used for you only Analysis covers your own sites. It is never pooled, benchmarked or used to train models.
- 04 Handed over machine-readable Exported on request; format and schedule are agreed with you.
- 05 Deleted end of contract Permanently removed from the system within the agreed period.
Access, network and application
- Access
Who can see what
Authorisation works in two layers: role based (administrator or user) and site based. A user sees data only for the sites they are authorised for, and administrative endpoints carry an additional role check. Sessions use signed tokens and expire.
- Network
Network and servers
The database and internal services are closed to the internet; only dashboard access is exposed. The firewall restricts by source, so field devices reach defined endpoints only. Administrative access to servers is key based and limited to a small number of people.
- Process
Application process
Source code is held in a private repository with restricted access. The most recent full internal review completed in July 2026, closing findings on authorisation checks, input validation, error message content and network access restrictions. A backup is taken before every release.
Artificial intelligence: what goes where
There are two distinct AI components and they behave differently. The difference is how far the data travels:
| Findings and savings recommendations | Natural-language assistant | |
|---|---|---|
| How it works | Rule-based engine | Cloud language model service |
| Where it runs | Entirely on our own infrastructure | Calls an external service |
| What is sent | Nothing, no data leaves | Only summarised figures for the question |
| What is not sent | — | Raw measurement archive, user details |
| Can it be switched off | The module itself can be | Yes, entirely, per organisation |
With the assistant switched off, everything else continues to work: monitoring, alarms, reporting and the recommendation engine are unaffected.
Notification channel
WhatsApp: what goes where
Alarm notifications and the Enver conversation are also available over WhatsApp, as an option. The channel runs on Meta’s WhatsApp Business (Cloud) API; transport is encrypted, but on the business side the message content passes through Meta’s infrastructure.
For that reason what is sent to WhatsApp is deliberately kept to a minimum. The channel can be switched off at organisation, person or rule level; when off, e-mail and panel notifications continue unchanged.
Delivery and read status and the content sent are kept on the panel, so an audit can show which warning went to whom and when.
Sent to WhatsApp
- Alarm title, measured value and threshold
- Site name and timestamp
- A link back to the panel
- The question asked and the summary figures of the answer
Not sent
- The raw measurement archive
- User lists or credentials
- Data from sites outside your authorisation
- Anything at all to an unverified number
What we have not done yet
Most security pages list only what has been done. Stating what has not been done is what makes the rest credible. Current gaps:
| Item | Status | Note |
|---|---|---|
| Independent penetration testing | Not started | On request we agree a schedule with you and share the summary findings |
| Second-location backup copies | In progress | Daily backups run; a second geographic copy is still being built |
| ISO/IEC 27001 certification | Not complete | The data centre is certified; certifying our own ISMS is a separate process |
On-premise
Keeping data inside your own network
The platform can run on your own server, or on a dedicated appliance we supply.
In that model measurement and production data never leaves your network: no ports are opened to the internet and all connections are outbound only. We decide the deployment model together.
Contractual commitments
-
Non-disclosure agreement
Signed on request before any detail is shared.
-
Data Processing Agreement
Under UK GDPR, with an IDTA where a restricted transfer applies.
-
Supplier questionnaire
We complete your own security assessment questionnaire.
-
Breach notification
We notify you without undue delay, so you can meet your 72-hour ICO obligation.
If your procurement process needs a fuller security document, we can send the briefing note this page is based on.
Let us measure what is happening on your site.
In a one-hour call we look at your existing setup and set out exactly which measurement points are needed and what you would be able to see.