Procurement reads this page so your engineers don't have to ask. Data ownership in one sentence, security posture in concrete mechanisms, and the honest status of what we do and don't hold — the same standard we apply to our forecast numbers.
In practice: your inverter, string, meter and sensor data, your forecasts, your reports and your work-order history are yours — exportable at any time, portable if you leave. DYNVOLT retains ownership of its model architectures, trained model weights, and aggregated, anonymised learnings across the fleet. The line is drawn in the contract in those words, not discovered in a dispute.
Formal certification is on our compliance roadmap, sequenced by customer requirements. What we have today is a concrete, auditable posture — ask us to demonstrate any line below.
Edge gateways accept no inbound connections. All connectivity is outbound encrypted tunnels; administrative access rides a private mesh, not an exposed port. There is nothing on the plant network for an internet scanner to find.
Configuration and secrets arrive in signed envelopes the edge verifies before applying. OS packages come from a GPG-signed repository; application images are CI-built. An attacker who owns the transport still can't inject config or code.
One identity provider for every surface: offline-verifiable tokens, TOTP step-up for sensitive actions, machine-to-machine credentials scoped per service.
Audit records are hash-chained — an edit or deletion breaks the chain visibly. Every plant-control write also lands in a per-write command log with the actor, role, and context — the same log our own forecast audit used to find and exclude curtailment days.
Connectivity loss never becomes a control gap: control loops, alarms, and the export limit keep running at the edge, with encrypted off-site backups resuming on reconnect.
The AI operator that analyses your fleet holds no plant-control scopes — by entitlement, not by policy document. It can read, correlate and recommend; it cannot write a setpoint. Trading recommendations are propose-only: a person confirms before anything is submitted to a market.
Source-code escrow is available for customers who require it. Your data is exportable at any time in open formats. And because the edge is autonomous by design, the plant keeps monitoring, alarming and enforcing its export limit even if every DYNVOLT cloud service vanished — vendor failure degrades reporting, not operation.
Energy operators fall inside NIS2 scope, which makes DYNVOLT part of your supply chain risk. We support your obligations with the mechanisms above, documentation of our architecture, and evidence on request — a supplier posture you can verify today, with formal certification on the compliance roadmap.
DYNVOLT DOO Kavadarci
Bel Kamen 50, Kavadarci, North Macedonia
Registration number: 7957653 · Tax ID: 4011026526422
admin@dynvolt.com
The same entity appears in our terms, privacy policy, and on your contract.
Security architecture walkthrough, data-ownership contract language, and escrow terms — on a call with the people who built it.