Data processing agreement (Art. 28 GDPR)
Version 1.6 · Effective: 15 December 2026 (new workspaces: on acceptance)
This agreement applies between the customer and Digital Zombies Kft., Bethlen Gábor u. 36., 1191 Budapest, Hungary, Cg. 01-09-329919 (“we”), whenever we process personal data on the customer's behalf while providing mumus. It forms part of the ÁSZF (terms of service) and is accepted with them. Need a signed copy? Write to privacy@mumus.app.
1. Roles
Roles follow who decides about the processing. The customer acts in one of these ways for the content of its workspace:
| Situation | Customer | Digital Zombies |
|---|---|---|
| The customer uses mumus for its own websites and projects | Controller | Processor |
| The customer (for example an agency) processes reports that contain personal data of its own client's customers or staff, on that client's instructions | Processor for its client (the client is the controller) | Subprocessor |
Where the customer acts as a processor, it confirms that its controller has authorised it to use mumus and us as a subprocessor, that the instructions it gives us correspond to its controller's instructions, and that it passes on our obligations and information as far as needed. The customer remains our only contact and passes on its controller's instructions and requests. We remain responsible to the customer for meeting obligations that are equivalent to those the customer owes its controller under Art. 28 GDPR, as set out in this agreement.
For our own purposes (customer accounts, billing and accounting, security of the service, our website), we are an independent controller; see the privacy policy. This agreement doesn't apply to that processing.
2. Subject and duration
Subject: hosting and operating mumus for collecting website feedback and managing tasks. Duration: as long as the main contract runs, plus the return and deletion periods in section 10.
3. Nature and purpose of processing
Storing, organising, displaying, transmitting (notifications, AI assistants connected by the customer), backing up and deleting the data the customer and its users put into mumus, solely to provide the service.
This includes recording time entries, receiving test-deployment notices from the customer's systems (deploy webhook) and sign-ins of people from the customer's content management systems (CMS connectors).
4. Types of data and data subjects
| Data subjects | Data categories |
|---|---|
| Members and client guests of the customer's workspace | Name, e-mail address, profile picture, role, project memberships, activity in the workspace (tasks, comments, status changes, timestamps), notification settings |
| Members, client guests, and anyone visible or mentioned in the reported content | Reports, comments, screenshots, screen recordings, attachments, page addresses, browser and device details, console and network metadata captured by the extension or the website widget, reports received by e-mail (sender, subject, text, attachments) |
| Members of the customer's workspace who track time | Time entries: person, task, date, duration, optional note, source (manual or timer); the running timer (task, start time) |
| People whom the customer's content management system signs in to report (CMS connectors) | Name and user ID as sent by the customer's system, the reports they create and their status |
Time entries record the working time of identifiable people. The customer decides whether to use time tracking and who sees the entries, including its own clients, and makes sure this complies with employment and data protection law. For people signed in by a CMS connector, the customer's system decides who may report and which name is sent; the customer makes sure it may share this data with us. AI agents the customer creates are not natural persons; their accounts contain no personal data of their own.
Screenshots, recordings, page addresses, e-mails and logs can contain personal data, also when they come from publicly accessible websites, for example names, e-mail addresses or customer records shown on a page. The browser's permission to capture a tab is a technical permission, not a legal basis. The customer decides what its users capture and is responsible for having a legal basis for it. Special categories of personal data (Art. 9 GDPR) are not intended to be processed; the customer makes sure that content doesn't contain them unnecessarily.
The extension and the server automatically redact values that look like secrets (see section 7). This reduces risk but is not a guarantee: it doesn't apply to pixels in screenshots and videos or to text users write, and it can miss unusual formats. Users should check screenshots and texts before sending.
5. Instructions
We process the data only on documented instructions from the customer, including for transfers to third countries, unless EU or member state law requires otherwise; in that case we inform the customer beforehand unless the law forbids it. The contract, the product settings and the customer's actions in the app count as instructions; this includes roles, project access, member groups and the visibility of tasks, comments and files restricted to the team or to groups. If we believe an instruction breaches data protection law, we inform the customer without undue delay and may suspend it until it is confirmed or changed.
AI assistants and AI agents that the customer connects through the MCP interface receive the data their tokens allow, on the customer's instruction. The provider of the AI tool is chosen by the customer and is not our subprocessor; the customer is responsible for its contract with that provider and for having a legal basis for the transfer. We don't send content to AI providers ourselves. The same applies to the customer's own systems connected through a deploy webhook or a CMS connector.
6. Confidentiality
Everyone authorised to process the data is bound to confidentiality by contract or by law. Our staff and the contractor named in section 8 access customer content only where support, operation or security requires it, and only to the extent necessary.
7. Technical and organisational measures (Art. 32 GDPR)
- Encryption in transit: TLS for all connections, HSTS.
- Access control: passwords hashed with Argon2id, breached-password check, login throttling, two-factor authentication (organisations can require it), session timeouts, scoped and revocable API and MCP tokens, single sign-on on Enterprise.
- Encryption of secrets: two-factor secrets are encrypted at rest (XChaCha20-Poly1305) with a key stored separately from the database.
- Authorisation: deny-by-default, role-based access per organisation and per project, “own tasks only” for client guests, automated tests for the authorisation matrix.
- Private storage: files are stored outside the web root under random names and are delivered only after an authorisation check. Uploads are checked by content, and images are re-encoded and stripped of metadata.
- Redaction: before upload, the extension removes known secret formats (for example API keys, JWTs, bearer tokens), values of parameters and fields with secret-looking names, and e-mail addresses from page addresses, console messages and failed-request addresses; the server applies the secret rules again. Request and response bodies, headers and cookies are never captured.
- Availability: a nightly database dump on the server (kept 14 days), and a nightly encrypted off-site backup of the database and the files with restic (AES-256) at a second provider in Germany, with its own snapshots; restore tests.
- Location: the servers and backups for workspace content are in data centres in Germany.
- Infrastructure: firewall, key-only SSH, automatic security updates of the operating system, containers without root privileges, pinned and scanned images, dependency vulnerability checks in the build pipeline.
- Patch management: dependencies and container images are checked for known vulnerabilities every night; security fixes are prepared automatically, tested and deployed promptly, with an automatic health check and rollback after each update.
- Internal content: tasks, comments and files can be restricted to the customer's team or to groups; the restriction is enforced on every channel (web app, notifications, e-mails, browser extension, website widget, AI-assistant interface, exports).
- Monitoring: health checks, error tracking where enabled, without workspace content or contact details (see the privacy policy), automatic rollback of failed updates.
- Logging: security events are logged without content and deleted after 30 days at the latest.
More details: Security. We may adapt the measures to the state of the art, provided the level of protection doesn't decrease.
8. Subprocessors
The customer authorises the subprocessors listed here (general written authorisation, Art. 28(2) GDPR).
| Subprocessor | Service and data | Location |
|---|---|---|
| IONOS SE, Elgendorfer Str. 57, 56410 Montabaur, Germany | Server hosting (all workspace content), sending e-mails (invitations, notifications), mailbox for reports sent by e-mail | Germany |
| Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany | Encrypted off-site backups (database and files, encrypted before transfer; Hetzner can't read them) | Germany |
| TARGET E DIGITAL SRL, Str. Regele Ferdinand nr. 33, OP 1, 400110 Cluj-Napoca, Romania (J2015002717122, VAT RO34987063) | Development and operations support with access to the production system, only where needed | Romania / EU |
We impose on every subprocessor, by contract, data protection obligations that are equivalent to those in this agreement, in particular sufficient guarantees for appropriate technical and organisational measures. We remain fully liable to the customer for our subprocessors' performance of their obligations.
Changes: we announce any intended addition or replacement of a subprocessor at least 30 days in advance by e-mail to the workspace owners and on this page. The customer may object within that period for reasons of data protection. We will then try to find a solution, for example not using the new subprocessor for that customer. If no solution is possible, the customer may terminate the affected subscription with effect from the change; we refund the fees paid in advance for the unused full months.
Error tracking: we currently use no external error-tracking provider. If we decide to use one, it is added to the list above through this change procedure before it receives any data.
Not subprocessors: Stripe (payments) and Számlázz.hu (invoicing, NAV reporting) process billing data of the customer, not workspace content; their roles are described in the privacy policy. AI assistants the customer connects with its own token (for example Claude Code or Codex) receive data on the customer's own instruction and under its own contract with that provider; they are the customer's recipients, not our subprocessors.
9. Assistance and personal data breaches
Taking into account the nature of the processing, we support the customer with requests from data subjects (Art. 15–22 GDPR) and with its obligations under Art. 32–36 GDPR (security, breach notifications, data protection impact assessments, prior consultation). Requests that data subjects send to us directly are forwarded to the customer without undue delay; we don't answer them ourselves unless the customer instructs us to.
We notify the customer of a personal data breach affecting its data without undue delay after becoming aware of it. The first notice is sent as soon as we can describe the breach, with the information then available, at the latest within 48 hours; we provide further information in stages as it becomes available. The notice includes, as far as known, the nature of the breach, the categories and approximate number of data subjects and records, the likely consequences, the measures taken or proposed, and a contact person.
10. Return and deletion
- The owner can download a complete export (JSON, CSV and all files) at any time under Workspace settings → Data & deletion.
- Deletion by the customer: when the owner deletes the workspace, it becomes read-only at once and is purged automatically after 30 days (it can be restored during that time).
- End of the contract: when the subscription ends, the workspace stays read-only so the customer can retrieve its data, for at least 30 days. The customer chooses whether to delete it itself (point 2) or to leave it. A workspace that has stayed read-only without a subscription for 6 months is deleted by us: we announce a deletion date to the owners by e-mail at least 30 days in advance and delete the workspace from that date on, at the latest 30 days after it. On written request, we delete earlier or extend the retrieval period.
- Backups: deleted data disappears from the nightly server dumps after 14 days and from the off-site backups after about 3 months, when the last snapshot that contains it expires. Until then, backups are used only to restore the service; the backup job fails and alerts us if old backups are not removed on time. If a backup is restored, deletions made since the backup date are re-applied before the service is used again.
- Data we must keep by law (for example invoices) is not workspace content and is kept by us as controller.
11. Audits
On request, we provide the information needed to demonstrate compliance with Art. 28 GDPR, in particular this agreement, the description of our measures and, where available, reports. The customer, its controller, or an auditor bound to confidentiality and mandated by them, may carry out audits, including inspections, after reasonable notice (as a rule 30 days; shorter after a personal data breach or a request by a supervisory authority), during business hours and without disrupting operations or other customers' data. Each party bears its own costs. If an audit causes us substantial effort beyond providing information, we may ask for reimbursement of our reasonable, documented costs, agreed in advance. These conditions never limit audits or requests by a supervisory authority.
12. Governing law, liability and precedence
This agreement is governed by Hungarian law. Liability towards data subjects is governed by Art. 82 GDPR; between the parties, the terms of service apply. If this agreement conflicts with the terms, this agreement takes precedence in matters of data protection.