Give storage owners a real door into their own battery data
Home and commercial battery storage systems already compute SOC, SOH and cycle data for the installer app. The Data Act gives owners — and the energy aggregator or VPP operator they choose — a standing right to that same data, separate from the Battery Regulation's passport disclosures.
Two obligations, two different jobs
The Data Act has applied generally since 12 September 2025 and covers ongoing owner and third-party access. The Battery Regulation separately introduces passport and durability disclosure duties for larger batteries — don't let one substitute for the other in your compliance plan.
| Requirement | Status on review date | What it means for a storage vendor |
|---|---|---|
| Owner access-on-request | Binding since 12 September 2025 | Provide an authenticated request path for SOC, SOH, cycle and energy-flow data already logged |
| Owner-directed third-party sharing | Binding since 12 September 2025 | Let an owner route their own storage data to an aggregator or energy-service provider of their choice |
| Pre-contract data transparency | Binding since 12 September 2025 | Disclose what a new storage system records and how it can be exported, before purchase |
| Accessible by-design architecture | Applies to systems placed after 12 September 2026 | New monitoring platforms should ship the access API as a core feature |
Usually in scope
- State of charge (SOC)
- State of health (SOH)
- Cycle counts
- Charge/discharge power and energy-flow data
- Fault and alarm events
Usually outside Chapter II
- Proprietary battery-management or degradation-prediction algorithms
- Cross-installation fleet analytics used for warranty risk modeling
- Cell-chemistry engineering data unrelated to the installed unit's own readings
- Data never captured or retained by the monitoring platform
| Field group | Typical source | Delivery format |
|---|---|---|
| State of charge (SOC) | Battery management system (BMS), IEC 62933 context | Time-series export or streaming API |
| State of health (SOH) | BMS degradation estimate | Periodic export tied to cycle milestones |
| Cycle count | BMS cycle counter | Structured export with cumulative and recent-window counts |
| Charge/discharge energy flow | Inverter telemetry | Interval export aligned to tariff or dispatch windows |
The BMS already knows. The owner still can't ask.
Every field a storage system needs to share already lives in the battery management system and inverter telemetry. What's missing is a governed path from that internal data to the owner and the third party they authorize.
Today: a closed loop
Product
Battery storage system
Backend
Storage/inverter vendor cloud
- State of charge (SOC)
- State of health (SOH)
- Cycle count
- Charge/discharge energy flow
Only exit
Manufacturer's own app
- No user-facing export or API
- No route for the user to authorize a third party
- No permissions model, so every request is a one-off exception
- No audit trail if a user or regulator asks what was shared
With a Data Act access layer
Product
Battery storage system
Backend
Storage/inverter vendor cloud
- State of charge (SOC)
- State of health (SOH)
- Cycle count
- Charge/discharge energy flow
New layer
Data Act access layer
- Field catalog
- User & device entitlements
- Consent & grant registry
Customer export & portal
CSV/JSON, self-service, same quality as the manufacturer sees
Third-party API (OAuth)
Purpose-bound grant to a repairer, analytics or energy provider
Audit & compliance log
Request, decision, recipient and delivery evidence for review
What we implement, concretely
SOC, SOH, cycle and energy-flow data API and customer access, plus third-party sharing for aggregators and VPP operators.
| Capability | What it does |
|---|---|
| SOC/SOH/energy-flow API | Authenticated access to current and historical battery state per installation |
| Customer export & portal | Self-service export and entitlement view for the system owner |
| Third-party sharing & OAuth grants | Purpose-bound, revocable access for an energy aggregator, VPP operator or installer |
| Fault & alarm feed | Structured event stream separate from routine state telemetry |
| Entitlement & audit layer | Owner/lessee-aware access control with a reviewable decision log |
Trace the BMS/inverter pipeline
Map every field from BMS and inverter through the monitoring cloud, and classify raw vs. derived.
Model entitlements
Connect installation identity to ownership, lease and finance records, including end-of-term handoff.
Design the owner API
Define catalog, request, third-party grant and delivery endpoints separate from internal engineering APIs.
Build the decision engine
Turn catalog, entitlement, trade-secret and privacy checks into explainable allow, partial and refuse outcomes.
Ship export and streaming
Deliver a historical export and, where useful, near-real-time energy-flow access for aggregator dispatch.
Test the edge cases
Run through leased systems, installer-operated monitoring, and disputed degradation-model requests.
Energy storage system Data Act FAQ
How is this different from the Battery Regulation's passport and durability disclosure?
They're related but distinct duties. The Battery Regulation's passport and durability/performance disclosure requirements are about publishing standardized information tied to a specific battery model or unit, largely aimed at larger batteries and aimed at transparency across the supply chain. The Data Act is a separate, ongoing right for the owner — and any third party they choose — to access and export their own installation's operational data on request. A compliance plan needs both, and shouldn't assume one satisfies the other.
Is an energy aggregator or VPP operator an eligible third party?
Yes, generally, provided the system owner is the one directing the sharing and the aggregator isn't a Digital Markets Act gatekeeper. Virtual power plant participation depends on exactly this kind of data flow — SOC, SOH and energy-flow data routed from the owner's storage system to the aggregator managing dispatch — so this is one of the more common and legitimate Article 5 use cases for residential and commercial storage.
Are degradation-prediction models protected trade secrets?
The models themselves can be, through the Act's structured trade-secret process. The underlying SOH, cycle-count and charge/discharge readings that feed those models are a different matter — they're the operational data the owner is entitled to, independent of whatever proprietary degradation forecast the vendor builds on top of them.
How does entitlement work for a leased or financed home battery system?
The Data Act's user definition extends to lessees and renters for the duration of their agreement, not just the registered owner. A financed or leased storage system needs an entitlement model that follows the finance or lease term, with a clear handoff at end of term so access doesn't outlive the agreement or lag behind it.
Is real-time energy-flow streaming required, or is periodic export enough?
Only where continuous delivery is both relevant to the request and technically feasible, and it must match the quality already available to the data holder. If your platform already streams SOC and power flow in near-real-time internally, a compliant export should offer that same cadence; if it only refreshes periodically, periodic export can be a compliant answer too.
Can an installer or integrator company be the data holder instead of the cell or system OEM?
Yes, if the installer operates the monitoring platform that actually receives and can make the data available — which is common where a storage system is monitored through the installer's own portal rather than the cell manufacturer's cloud. Settle this in the OEM-installer supply relationship, including who publishes pre-contract data disclosures, rather than leaving it ambiguous.
Primary sources and status
Reviewed 9 September 2026. The Data Act, GDPR and Battery Regulation are binding EU regulations. The Commission FAQs are non-binding implementation guidance. IEC 62933 is cited as technical context, not as a legal source. Yarify's API contract, entitlement model and delivery sequence are engineering recommendations, not legal advice.
- Regulation (EU) 2023/2854 — the EU Data ActBinding legal text covering connected-product data access, third-party sharing, fair terms and transitional dates
- Regulation (EU) 2016/679 — the General Data Protection RegulationBinding data-protection rules relevant where storage-system data is linked to an identifiable household
- Regulation (EU) 2023/1542 — the Battery RegulationBinding EU regulation introducing battery passports and durability/performance disclosure duties for larger batteries
- European Commission — Data Act FAQs, version 1.4Non-binding implementation FAQs covering scope, roles, access, trade secrets, compensation and cloud switching
