Terms, in plain language.Quietly enforceable.
Last updated 3 July 2026. Ten sections in plain language, each mapping onto the comprehensive 27-section document. This page is a faithful map, not a replacement. Where the two could be read differently, the full document governs. How we handle personal data lives in the privacy policy, incorporated by reference (full § 13).
Who you're engaging
fyzno is a digital infrastructure studio based in the Netherlands. We provide managed web hosting, managed SMTP, web development, AI integrations and AI workflows. Anything we call a sub-processor or partner in the written scope of your engagement is part of fyzno for the purposes of these terms.
How a project begins
Every project begins with a written scope and a written price. The scope names the deliverables, the timeline, the assumptions and the boundary of what is out of scope. A signed scope fixes its price for that scope; list prices for new work can change. Work begins only after both parties have signed. Verbal agreements are not engagements.
Quarterly 99.9% target, missed = contacted
For managed hosting and managed SMTP we commit to a quarterly uptime SLA of 99.9% on managed infrastructure. If we miss the threshold in any given quarter, we contact you on the same business day with a written post-mortem. We don't bury incidents behind auto-credit or marketing copy. See § 06 for the operational reality behind this number.
What we keep
Anything you share in the course of an engagement, including source, credentials, customer data and contracts, stays confidential. We sign your NDA if you have one. If you don't, ours is in the default scope and binds every named partner and sub-processor.
Where the work lives
Production workloads run in the EU by default. AI workloads involving personal data can be run on private infrastructure on request. We don't sell or trade customer data. Backups are encrypted at rest and held for at least thirty days, with encrypted daily backups retained in Strasbourg off the primary site. You remain responsible for keeping your own copies of your data.
One primary node. Zero pretending.
We run a single primary node today, in OVHcloud's Gravelines site, with a documented failover design and encrypted off-site backups. We are actively implementing a second operational node plus a separate backup node; the migration plan is written and progress is public on /status. We don't claim multi-region high availability we haven't shipped, and we don't sell uptime we can't measure. When something is wrong, we contact you as soon as we know, usually within minutes, and we figure out the next step together: a prorated refund for the affected period, a free extension of the term, or hands-on help getting your environment back on track. If we miss the bar, we make it right.
Invoices, subscriptions, and what happens if one goes unpaid
Project work is invoiced monthly in arrears and payable within fourteen days. Managed services (hosting, SMTP) run per term and renew automatically unless cancelled before the renewal date; you manage the cancellation, we don't make it hard. Late payment pauses non-critical project work first. Sustained non-payment can suspend or, ultimately, terminate managed services; the full document spells that power out bluntly, but we will always contact you before anything is switched off.
Leaving cleanly
Either party may end an engagement with thirty days' written notice. On termination we hand back source, credentials, runbooks and a written export of any data we held. After thirty days we delete our copies and send you the deletion certificate. Separately, access to the public Services themselves can be ended as described in § 15 of the full document: that clause protects the platform; your engagement deliverables are governed by the signed scope.
Maximum legal exclusion
We provide our services on an "AS IS" basis and exclude all liability to the absolute maximum extent permitted by mandatory EU and Dutch law. Where liability fundamentally cannot be waived (such as willful misconduct, gross negligence under Burgerlijk Wetboek art. 6:75, or death), our aggregate liability is strictly capped at the fees paid to us in the six months preceding the claim. You also indemnify us against third-party claims arising from your use of the services.
Dutch law, Dutch courts
These terms are governed by the laws of the Netherlands. Disputes are settled first by good-faith discussion; if that fails, exclusively in the competent Dutch courts. Claims must be brought within one year of the cause arising.
The binding document: definitions, purchases and renewal, prohibited activities, intellectual property, indemnification, and the full liability posture. It governs; this page maps it.
Questions about these terms? Write to info@fyzno.com. We reply within forty-eight hours, signed.