Skip to main content

Vendor assessment of CUZY Hosting: the answers

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.

Last updated: October 25, 2026. This page sums up our commitments; the binding texts are the terms of service, the Data Processing Agreement and the security measures it refers to.

In short

A known operator

A registered business in Ireland, hosting HumHub since 2017, with a named person who answers for it.

Your region

Germany (EU), the USA or Singapore (APAC). In Germany (EU), hosting and backups never leave the European Union.

GDPR agreement

An Article 28 Data Processing Agreement with every subscription, sub-processors listed, 30 days' notice of any change.

Tested backups

At most 1 hour of data lost on Business and 24 hours on Team; restores tested, encrypted, with a second provider.

Breaches reported

Within 72 hours at the latest, with what is known and what was done.

Free to leave

A complete export at any time, open-source code, the unused days refunded.

Who you sign with

  • Contracting party: Marc Farré, sole trader, trading as CUZY
  • Registration: business name CUZY, registration number 760136, at the Irish Companies Registration Office (core.cro.ie, public register of business names)
  • Business registration number: 0117829GB (Ireland)
  • Address: 80 St. Columbanus Road, Dundrum, Dublin 14, D14 WP98, Ireland
  • History: hosting HumHub communities for organizations since 2017; publishing HumHub modules since 2020, most of them on the official HumHub marketplace, the free ones used by more than 2,000 HumHub installations
  • Applicable law: Irish law; the Irish Data Protection Commission is CUZY's supervisory authority

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.

If CUZY's founder is unavailable

A small provider has to answer this question openly.

  • The platform runs by itself. Backups, security updates, monitoring and alerts are scheduled tasks, not people; each tenant server keeps running even if CUZY's own systems stop.
  • A second person can step in. A trusted person holds the emergency access to every account and key the platform depends on, receives the same critical alerts, and follows written recovery procedures that do not need the founder.
  • You are never stuck. Your complete export is in your customer account at any time, and everything your community runs is open source: it can be restored on your own server or with another HumHub host, HumHub GmbH included.

Where your data is, and who processes it

WhatWhere
Application, database and uploaded filesA Hetzner Cloud server in the region you choose: Germany (EU, Nuremberg and Falkenstein), the USA or Singapore (APAC)
BackupsBackblaze, in the same region, encrypted before they leave the server; Singapore communities: United States
Emails sent by your communitySMTP2GO, EU sending infrastructure
Domain names (DNS)Cloudflare: addresses only, no community content
Administration of the serversCUZY staff, from the European Union
Business plan optionsPush 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.

GDPR documents

  • Data Processing Agreement under Article 28 GDPR, part of the terms of sale and accepted with every subscription; a signed copy on request. It also covers the UK GDPR, Swiss, Canadian (Quebec included) and US state laws: read the agreement.
  • Roles: you are the controller of your members' data, CUZY the processor acting only on your instructions, using the data for nothing of its own: no advertising, no selling, no AI.
  • International transfers rest on an adequacy decision, the European Commission's Standard Contractual Clauses or the EU-US Data Privacy Framework, with encryption as a supplementary measure.
  • Public authorities: data is disclosed only on a binding legal order, which CUZY checks and contests when there are grounds; you are told first unless the law forbids it.
  • Audit: once a year on request, the information that shows compliance (the results of the last restore test, the sub-processors' certifications, answers to your questionnaire), or an audit with 30 days' notice (agreement, section 12).

Security controls

  • Isolation: each community has its own container, database, file store and credentials, with memory and CPU limits.
  • In transit: HTTPS only, certificates renewed automatically, custom domains included.
  • At rest: the databases are encrypted at rest; uploaded files on the server disks are not. The database key is stored on the server, apart from the data files, and in an encrypted vault; backups and the platform's secrets are encrypted too, with keys stored apart from the data. The files are protected by isolation, the access rules below and the physical security of Hetzner's ISO 27001 certified data centers.
  • Privileged access: named staff only, with SSH keys, from restricted networks; two-factor authentication on the staff accounts of our management platform; administrative interfaces are not exposed to the internet.
  • Support access: only if you allow it, through one-time login links that expire within minutes and are recorded in your community's audit log; you can switch it off.
  • Your administrators: two-factor authentication is installed in every community and required for administrators from the start; you can extend it to other groups.

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.

Patching and vulnerabilities

LayerWho patches, and how
Server operating systemCUZY: security updates installed automatically, restarts in the announced maintenance window
Database, cache, web proxyCUZY: pinned versions, updated on the advisories reviewed every month, urgent ones at once
HumHubCUZY: backup first, a small group of communities first, health checks, then the rest
ModulesCUZY: marketplace modules updated daily on Team and Business
Critical vulnerabilitiesFixed 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).

Backups and recovery

TeamBusiness
Frequency and retentionDaily; 30 daily, 12 weekly, 12 monthly keptHourly; 72 hourly, 60 daily, 12 weekly, 12 monthly kept
Maximum data loss (RPO)24 hours1 hour
Time to restore (RTO)8 hours4 hours
Real restores testedQuarterlyMonthly

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.

Incidents and breaches

  • Detection: every community is checked from outside every minute; servers, backups, certificates and email delivery are monitored, and alerts reach our team day and night.
  • Response: written procedures for every risk of our register, reviewed quarterly; a compromised server is isolated, its secrets rotated and it is rebuilt with communities restored from clean backups.
  • Information: incidents are posted on the status page and sent to your administrators.
  • Personal data breach: notified to you without undue delay and within 72 hours at the latest, by email, with the nature of the breach, the data and people concerned, the likely consequences and the measures taken (agreement, section 11).

Leaving CUZY

  • Complete export of the database and files from your customer account, once a day: with the open-source code, it rebuilds the same community on any HumHub server.
  • Stop when you want: ask us to end your subscription and the unused days are refunded pro rata (terms of service, section 10).
  • Deletion: the community is archived about 30 days after the end and deleted with its backups 6 months after the end at the latest, earlier on request, with written confirmation.

References

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.

Questions from vendor assessments

Is CUZY a limited company?

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.

Is CUZY certified ISO 27001 or SOC 2?

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.

Is our data encrypted at rest?

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.

Will you sign our Data Processing Agreement or fill in our questionnaire?

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.

Your own questionnaire, your Data Processing Agreement to review, or a reference to call? Contact us: data-protection officers and IT managers get a written answer from the person who runs the platform. We share the details behind our security measures under a non-disclosure agreement.

Loading...