The agreement under Article 28 of the GDPR between CUZY, the processor, and every customer of CUZY Hosting, the controller of its community's data. It also covers the UK, Swiss, Canadian and US privacy laws, and lists our sub-processors.
New to HumHub? What it is, who it is for and what you can do with it.
Data Processing Agreement, version 1.2, effective 28 October 2026. Part of the contract between CUZY, 80 St. Columbanus Road, Dundrum, Dublin 14, D14 WP98, Ireland ("CUZY", the processor) and the customer who subscribes to CUZY Hosting (the "Customer", the controller), under Article 28 of the GDPR. The terms of service and the privacy policy apply; where they differ from this agreement on the processing of personal data, this agreement prevails. Terms such as "personal data", "processing", "data subject", "sub-processor" and "personal data breach" have the meaning the GDPR gives them. For a Customer subject to the Swiss Federal Act on Data Protection (FADP), this agreement also serves as the contract its Article 9 requires, and every reference to the GDPR includes the FADP where it applies; section 14 covers the United Kingdom, Canada and the United States.
CUZY processes the data only on the Customer's documented instructions. The instructions are: this agreement, the terms, the settings the Customer makes in the community and in the customer account, and the support requests the Customer sends. CUZY informs the Customer immediately when, in its opinion, an instruction infringes the GDPR or other EU or Member State data protection law, and may wait for its confirmation before following it. CUZY may process the data to comply with a legal obligation of EU or Irish law; it then tells the Customer first unless that law forbids it on important grounds of public interest.
The Customer decides what the community is for and who joins it. It has a lawful basis for what it and its members put in the community, informs its members (the community's own legal pages, written from CUZY's templates, are the usual place), answers their requests with the help of section 9, and gives only lawful instructions. When the community holds special categories of data, the Customer chooses the region, the plan and the settings that suit them.
The people CUZY authorises to access the data are bound to confidentiality, a duty that lasts beyond the end of their work for CUZY and of this agreement. CUZY accesses a community only for support at the Customer's request, to investigate an incident, or when required by law. Every staff login to the community is recorded in the community's audit log, visible to its administrators; every other staff action on it (a restore, an upgrade, a command, a reading of its logs) is recorded in CUZY's own event log, which the Customer obtains on request. CUZY uses the data for no purpose of its own and never sells or shares it.
CUZY applies the measures published on cuzy.app/security, which the Customer has read and accepts as appropriate under Article 32: one isolated environment per community, encryption in transit and of every backup, least-privilege access with two-factor authentication for staff, monitoring, tested restores, a documented incident process. CUZY may change a measure when the new one gives at least the same protection. The page, as it stands on the day the Customer accepts this agreement, is the Customer's annex of technical and organisational measures; CUZY keeps every earlier version of the page and sends it on request.
The Customer authorises the sub-processors below. Before CUZY adds or replaces one it notifies every Customer by email and on the privacy policy page at least 30 days ahead; a Customer who objects within those 30 days may terminate the hosting subscription without penalty, with the unused period refunded.
| Sub-processor | Purpose | Location and transfer basis |
|---|---|---|
| Hetzner Online GmbH | servers | the region the Customer chose: Germany (EU), the USA or Singapore (APAC); in the USA and Singapore, Hetzner runs the servers in data centers operated through its subsidiaries Hetzner US LLC and Hetzner Singapore Pte. Ltd., under the transfer safeguards of its data processing agreement |
| Backblaze, Inc. | encrypted backups and exports | the same region as the community, except Singapore communities, whose encrypted backups are stored in the United States; Standard Contractual Clauses |
| Cloudflare, Inc. | DNS of the community's address; forwarding of replies to our service addresses | global; EU-US Data Privacy Framework |
| SMTP2GO Ltd | delivery of the community's emails | EU sending infrastructure; company in New Zealand (adequacy decision) |
| HumHub GmbH & Co. KG (push.humhub.com, through Google Firebase) | push notifications of Business communities: the device tokens of the members who turned them on and the text of their notifications | Germany (EU); Firebase in the United States, Standard Contractual Clauses |
| Google LLC (Google Maps Platform, Geocoding API) | address geocoding of the map modules of Business communities, with the key CUZY provides: the postal address sent for each lookup | United States; EU-US Data Privacy Framework |
| WhatsApp (Meta Platforms Ireland Ltd) | the Business support channel, for the contact the Customer names | Ireland (EU); Meta may process the data in the United States: EU-US Data Privacy Framework and Standard Contractual Clauses |
| Infomaniak Network SA | CUZY's own mailboxes (what the Customer writes to support) | Switzerland (adequacy decision) |
Each sub-processor is bound by a written contract that gives the data at least the protection of this agreement, and CUZY remains fully liable to the Customer for its sub-processors' work. On request, CUZY shows the data protection terms of a sub-processor, commercial details removed. The external uptime monitor (StatusCake Ltd, United Kingdom) sees hostnames only and processes no personal data. No AI service processes the Customer's data: the support assistant is switched off (9 October 2026).
Data stays in the region the Customer chose. For a region outside the EU, and for the backups of Singapore communities, the transfer rests on Chapter V of the GDPR: an adequacy decision or the European Commission's Standard Contractual Clauses (processor to sub-processor) between CUZY or its sub-processor and the recipient, as listed above, or the safeguards of the sub-processor's own data processing agreement, with the encryption of section 5 as a supplementary measure. For a Customer established outside the EU and the EEA, the Standard Contractual Clauses, module four (processor to controller), apply between CUZY and the Customer to the extent the GDPR applies to CUZY's processing. CUZY makes its assessment of a transfer available on request. CUZY does not transfer data elsewhere without the Customer's instruction. For a Customer under the FADP, a transfer outside Switzerland and the EU rests on the same clauses, which the Swiss Federal Data Protection and Information Commissioner recognises with the adaptations it requires.
CUZY discloses data to a public authority only when a binding legal order requires it. It then tells the Customer first unless the law forbids it, checks the order's legality and contests it when there are reasonable grounds, and discloses the minimum the order requires. CUZY tells the Customer of any inquiry, inspection or audit by an authority about the processing, where the law allows. CUZY has built no means for anyone to reach the data outside these procedures.
CUZY helps the Customer answer members' requests (access, rectification, erasure, portability, restriction, objection) with the tools of the community and, where those do not suffice, by support within ten business days. A request a member sends to CUZY directly is passed to the Customer without undue delay and is not answered by CUZY unless the Customer asks it to. CUZY helps with the security obligations, data protection impact assessments and prior consultations with the information it holds, and cooperates with the supervisory authorities. Assistance beyond what the tools and the plan's support include is charged at the published hourly rate, agreed in writing first.
CUZY notifies the Customer without undue delay, and at the latest within 72 hours after becoming aware of a personal data breach affecting the Customer's data, by email to the account address, with what is known: nature, data and people concerned, likely consequences, measures taken, a contact. The information may come in phases. CUZY takes the measures to contain the breach and limit its effects, and helps the Customer inform the members when the Customer decides to. The Customer remains responsible for the notifications to the supervisory authority and to the members.
On request, at most once a year unless a breach or an authority requires it, CUZY provides the information needed to show compliance with this agreement: the published security page, the list of sub-processors, the results of the last restore test, the certifications of the sub-processors, answers to a written questionnaire. An on-site audit by the Customer or an auditor bound to confidentiality is possible with 30 days' notice, during business hours, at the Customer's cost, without access to other customers' data. CUZY also submits to the inspections of a competent supervisory authority.
CUZY tells the Customer promptly if it can no longer meet an obligation of this agreement, or if a change in the law is likely to prevent it. The Customer may then suspend the processing concerned and, if compliance is not restored within a month, terminate the hosting subscription without penalty, with the unused period refunded.
When another privacy law governs the Customer's data, CUZY meets its processor obligations under the same terms:
This agreement lasts as long as CUZY processes the data for the Customer; sections 4, 8, 10 and 11 apply until the last copy of the data is deleted. Liability follows the terms of service; nothing in this agreement limits what the GDPR makes the parties liable for. Irish law applies; the courts of Dublin have jurisdiction, without prejudice to the GDPR's rules on the competent supervisory authority. Accepting these terms at checkout concludes this agreement; a Customer who needs a signed copy for its records asks at contact@cuzy.app and receives this text with its name and both signatures, unchanged. Notices about this agreement go to that address, and to the Customer's account address; a personal data breach is reported to CUZY at security@cuzy.app.