Before you trust a host with your HumHub community, you need to know who you sign with, where the data is, how it is protected and how you get it back. This page answers the questions of a vendor assessment one by one, for data-protection officers, IT managers and boards, with links to the texts that bind us.
A registered business in Ireland, hosting HumHub since 2017, with a named person who answers for it.
Germany (EU), the USA or Singapore (APAC). In Germany (EU), hosting and backups never leave the European Union.
An Article 28 Data Processing Agreement with every subscription, sub-processors listed, 30 days' notice of any change.
At most 1 hour of data lost on Business and 24 hours on Team; restores tested, encrypted, with a second provider.
Within 72 hours at the latest, with what is known and what was done.
A complete export at any time, open-source code, the unused days refunded.
CUZY is a small business, not a limited company: the person who signs is the person who answers for it. Our partnership with HumHub GmbH, the publisher of HumHub, is described in how we work with HumHub; more about us on the about page and in the legal notice.
A small provider has to answer this question openly.
| What | Where |
|---|---|
| Application, database and uploaded files | A Hetzner Cloud server in the region you choose: Germany (EU, Nuremberg and Falkenstein), the USA or Singapore (APAC) |
| Backups | Backblaze, in the same region, encrypted before they leave the server; Singapore communities: United States |
| Emails sent by your community | SMTP2GO, EU sending infrastructure |
| Domain names (DNS) | Cloudflare: addresses only, no community content |
| Administration of the servers | CUZY staff, from the European Union |
| Business plan options | Push notifications (HumHub GmbH with Google Firebase), address geocoding for the map modules (Google), WhatsApp support for one named contact |
Organizations whose members are in the European Union choose Germany (EU), the default: hosting and backups then stay in the EU. Every sub-processor, its purpose, its location and its transfer safeguard is listed in the privacy policy (section 4); you are told at least 30 days before one is added or replaced and may terminate without penalty if you object. Details: data privacy.
Certifications. The data centers are ISO 27001 certified; CUZY itself holds no ISO 27001 certificate or SOC 2 report and has not yet commissioned an outside penetration test. In their place: the published measures, made binding by the Data Processing Agreement; a security review of every new piece of CUZY code before release; servers built from one hardened configuration and audited weekly; and read-only SFTP access, so you or your auditor can read every line of code your community runs.
| Layer | Who patches, and how |
|---|---|
| Server operating system | CUZY: security updates installed automatically, restarts in the announced maintenance window |
| Database, cache, web proxy | CUZY: pinned versions, updated on the advisories reviewed every month, urgent ones at once |
| HumHub | CUZY: backup first, a small group of communities first, health checks, then the rest |
| Modules | CUZY: marketplace modules updated daily on Team and Business |
| Critical vulnerabilities | Fixed on every community within 48 hours through a hotfix pipeline |
Release windows and support hours: update and support policy. Security problems are reported to security@cuzy.app (disclosure policy).
| Team | Business | |
|---|---|---|
| Frequency and retention | Daily; 30 daily, 12 weekly, 12 monthly kept | Hourly; 72 hourly, 60 daily, 12 weekly, 12 monthly kept |
| Maximum data loss (RPO) | 24 hours | 1 hour |
| Time to restore (RTO) | 8 hours | 4 hours |
| Real restores tested | Quarterly | Monthly |
Backups hold the full database, files, configuration and modules, are encrypted before upload, stored with a second provider in the same region, checked weekly, and you can download or restore any of them from your customer account. Every figure: backup and retention schedule.
Organizations whose HumHub community CUZY hosts include Enercoop, ATD Quart Monde, Transition Network, Inforisque, Mentalify, ADI Nouvelle-Aquitaine, Fondation SEVE, Université du Nous. Public reviews of a specialist host are few; a conversation with a customer tells you more. Ask us and we put you in touch with a customer who has agreed to answer prospects.
No. CUZY is the registered business name of Marc Farré, a sole trader in Ireland (business name registration 760136). Your contract is with Marc Farré trading as CUZY, under Irish law, and the commitments of the terms of sale and the Data Processing Agreement bind him personally.
No. The data centers that host the servers (Hetzner) are ISO 27001 certified; CUZY itself has no certification and no outside penetration test yet. What it offers instead: published security measures that the Data Processing Agreement makes binding, a security review of every new piece of its code, read-only SFTP access so you can audit the code your community runs, and answers to your questionnaire.
The databases are: each community's database is encrypted at rest, with the key stored on the server, apart from the data files, and in an encrypted vault. Backups are too: they are encrypted on the server before they leave it, with keys stored elsewhere. Uploaded files on the server disks are not encrypted at rest; they are protected by the isolation of each community, the access rules on this page and the physical security of the ISO 27001 certified data centers.
CUZY's Data Processing Agreement is accepted with every subscription and a signed copy is sent on request. If your organization requires its own agreement, send it: we review it and say which clauses we can accept. Security questionnaires are answered in writing.