Energy and telecommunications
Data protection for energy and telecommunications
Energy suppliers and telecommunications providers serve large customer bases and manage metering and connection data – in billing, network and customer systems. Espresso shows where the data is stored, enforces retention periods and proves every deletion.
What makes it challenging for energy and telecommunications
Large customer bases
Move-ins, move-outs, provider switches and contract ends constantly generate data that has to be deleted at some point.
Metering and connection data
Smart metering systems and connection data reveal how people live and communicate.
Retain – and then delete
Some data must be retained for a certain period; after that, any further retention requires a reason.
Critical infrastructure
High requirements for security and operations – the data stays within your own network.
How the industry uses Espresso
- Data Deletion Deletion after the end of the contract Customer and contract data that is due is deleted across billing, CRM and specialist systems – in the right order and with proof. Go to the module
- Data Discovery Customer data in file storage Find exports, lists and customer correspondence in file storage, databases and Microsoft 365. Go to the module
- Subject Request Requests from customers Answer access and erasure requests on time, with every step recorded. Go to the module
- Privacy Delivery Test data and analytics Test data in a valid format and pseudonymised exports for analytics. Go to the module
The framework for energy and telecommunications
In addition to data protection, there are sector-specific rules for metering data, communications and critical infrastructure.
| Rule | What it means |
|---|---|
| FADP and GDPR | Register, access requests, erasure, data security. |
| Electricity supply law | Rules for processing data from smart metering systems. |
| Telecommunications law | Telecommunications secrecy and data protection in telecommunications. |
| Surveillance of Post and Telecommunications Act (SCPTA) | Telecommunications service providers retain secondary telecommunications data for six months (Art. 26 para. 5 SCPTA). |
| Information Security Act (ISA) | Obligation for operators of critical infrastructure to report cyberattacks. |
Overview without any claim to completeness; does not replace legal advice in individual cases. As of: 6 October 2026.
Getting started
Try it with your systems
In the proof of concept, Espresso runs in your test environment – with the modules and applications you are interested in, and with success criteria agreed in advance.
Frequently asked questions
Does it work with SAP and other systems?
Yes. The applications do the deleting themselves using their existing functions; they are connected via an open interface or via Azure Service Bus. At Pax, the Swiss pension insurer, deletion runs across SAP and non-SAP systems.
Does the data stay within our network?
Yes. Espresso runs in your environment, and your applications are connected within your own network. Espresso never establishes a connection to the vendor of its own accord.
Can deletions be paused for a maintenance window?
Yes. New deletion runs can be held for a maintenance window and resumed afterwards.
How are exceptions handled?
Applications can object to a deletion, and deletion holds stop deletions for individual cases – for example in the event of litigation.
Related topics
- Delete Deleting across many systems Orchestration, approval, objections: how to delete reliably in legacy IT landscapes. Read more
- Delete Retention and deletion periods How long data must and may be retained in Switzerland – and how retention periods become deletion rules. Read more
- Fundamentals Running data protection software yourself Why data protection software often needs to run in your own data centre or your own cloud. Read more
See Espresso in 30 minutes
We will show you the cockpit with sample data – and discuss where you should start.
Request a demoor write directly to info@espressodataprivacy.com