ENVIRONMENTAL CODE OF CONDUCT
Five rules on environmental impact
Secyda is a software company. We don’t manufacture hardware, we don’t generate electricity. But we choose who does it for us, and that choice has consequences.
Every infrastructure decision is an environmental decision. We choose providers the way we choose jurisdictions: with criteria.
Secyda operating rule
Our infrastructure, in numbers
Renewable energy
Main infrastructure powered by hydroelectric energy. Certified by independent auditors, not by us.
Hetzner (Germany/Finland) · Hydroelectric since 2008Source: Hetzner ↗Energy efficiency
PUE between 1.10 and 1.16. The industry average is around 1.5. The closer to 1.0, the less energy is wasted on non-computing operations.
Natural air cooling · No water consumptionSource: Hetzner ↗Hardware lifespan
8-year average versus the usual 3–5. Refurbished servers, recycled components. Less electronic waste.
Refurbishment and component recyclingSource: Hetzner ↗Water consumption
Natural air cooling 98% of the year. No cooling towers, no water consumed to cool servers.
WUE = 0 · Air cooling onlyOVHcloud cooling
Secondary provider. Water cooling with 7 times less consumption than average. 100+ proprietary patents in cooling systems.
OVHcloud (France) · Over 100 patentsSource: OVHcloud ↗EMAS certification
EU Eco-Management and Audit Scheme. Independent European audit at Hetzner’s German data centres. Not a self-awarded label.
Certificates: naturenergie · VattenfallThe five rules
No environmental certification, no deal
We require public energy data, PUE and independent certifications. If they don’t have them, we don’t work with them. Same as with jurisdictions.
Data is hosted close to its users
Nearest data centre within the EU. Less distance, less energy in transit. It’s sovereignty and efficiency—you don’t have to choose.
Open standards, zero forced obsolescence
ODF, CalDAV, WebDAV, OpenID, SAML. If your contract changes, your data migrates with you. No forced migrations, no disposable temporary infrastructure.
Modular architecture, proportional consumption
Independent services that scale separately. Each component consumes what it needs. No monoliths burning resources to keep features nobody uses.
If we can’t measure it, we don’t publish it
Today we don’t have our own energy consumption figures. We’ll publish them when we can verify them. Until then, this rule exists so we don’t make up a pretty dashboard.
Limits of our influence
There are things we don’t decide. We could have said nothing, but that’s exactly what everyone else does.
Hardware
We don’t choose components or manufacturing processes. Our control extends to selecting providers with long life cycles and certified recycling practices.
Energy
Today our providers use renewables. Tomorrow that could change. What we control: annual audits and certifications as a requirement, not a preference.
Network
Data travels through infrastructure we don’t operate. What we control: hosting data close to users and minimising transfers between centres.
Provider audit
This is not an ESG report. It’s an internal code of conduct we decided to make public. It’s updated when the facts change, not when it’s time to publish something.
Last update: April 2026
POLITICAL COVERAGE
Those who decided to migrate before it was mandatory have a story to tell. And a headline they don’t have to run from.
Let’s talk.