Beta mumus is in public beta: free while we test it with real teams. Found something odd? Tell us.

Privacy policy

Version 1.8 · Effective: 15 November 2026 · Magyar változat (same content)

In short

  • For the content of a workspace (reports, screenshots, comments, files), the customer decides: we process it on the customer's behalf. For accounts, billing, security and our website, we are responsible ourselves.
  • Workspace data and its backups are hosted in Germany. Payments go through Stripe, invoices through Számlázz.hu.
  • No advertising, no third-party trackers. Optional usage analytics run only with your consent.
  • You can export and delete your data yourself; write to privacy@mumus.app for anything else.

1. Who is responsible

Digital Zombies Kft., Bethlen Gábor u. 36., 1191 Budapest, Hungary, company registration number Cg. 01-09-329919, e-mail hello@mumus.app (see imprint). Data protection contact: privacy@mumus.app. Based on our assessment of our current processing, we are not required to appoint a data protection officer; we review this when our processing changes.

2. Controller or processor?

Roles depend on who decides why and how data is processed:

SituationControllerDigital Zombies
A company uses mumus for its own websitesThe companyProcessor (data processing agreement)
An agency uses mumus for a client, and the reports contain personal data of the client's customers or staff, processed on the client's instructionsThe client (the agency is its processor)Subprocessor
Customer accounts, billing and accounting, security of the service, our website, optional usage analyticsDigital ZombiesController

An agency can also be a controller for some processing of its own, for example for its own staff. If your data is in a workspace, the organisation that runs it is your first contact; we forward requests we receive to it.

Screenshots and recordings contain what is on the screen. Page contents, addresses, e-mails and logs can contain personal data, also on publicly accessible websites. The browser's permission to capture a tab is only a technical permission, not a legal basis for processing the data of everyone visible in it. The organisation that uses mumus is responsible for having a legal basis for what its users capture.

3. Accounts

Name, e-mail address, password (stored only as an Argon2id hash), optional profile picture, two-factor secrets (encrypted), notification settings, language and time zone setting, login timestamps, memberships, roles and member groups. Your time zone is detected once from your browser when you first use the app; you can change it in your profile. We use it only to display dates and times and to send time-based reminders (for example due-date reminders) at the right local time. Optionally a mobile number for SMS alerts, stored only after you verify it (SMS alerts are not active at the moment; before we turn them on, we will name the SMS provider here).

Legal basis. If you are a sole trader or freelancer who concludes the contract with us yourself: performance of the contract (Art. 6(1)(b) GDPR). If you use mumus as an employee or representative of a business customer, or because a customer invited you (for example as a team member or client guest), you are not a party to our contract: we then process your account data for administering accounts and keeping the service secure on the basis of our and the customer's legitimate interest in providing the service the customer ordered (Art. 6(1)(f) GDPR). What happens with your data inside a workspace (for example your comments and reports) is decided by the customer (section 2). The data is kept until the account is deleted.

Single sign-on (Enterprise): if your organisation signs in through its own identity provider (for example Microsoft Entra ID or Google Workspace), we receive your name, e-mail address and a stable user ID from that provider at each login and store the link between that ID and your mumus account. We don't receive your password there. Your organisation is responsible for its identity provider. Legal basis: the legitimate interest of your organisation and of us in central, secure account management (Art. 6(1)(f) GDPR). The link is deleted with your account.

Sign-up: unconfirmed sign-ups expire after 24 hours and password-reset links after 1 hour; both are deleted after 7 days. When a workspace is created, we store which versions of the ÁSZF/terms, the data processing agreement, this policy and the checkbox wording were shown, a fingerprint of those texts, that the highlighted provisions were accepted separately, when the form was sent and when the e-mail address was confirmed (legal basis: our legitimate interest in proving the contract, Art. 6(1)(f) GDPR); this record is deleted with the workspace.

4. Billing and payments

Subscriptions are paid through Stripe (Stripe Payments Europe Ltd., Dublin, Ireland), using Stripe Checkout and the Stripe customer portal. Card and bank details are entered on Stripe's pages: mumus never sees or stores them. Stripe receives the name, e-mail address, billing address, VAT ID and payment data of the person who subscribes, and checks EU VAT IDs in VIES. Stripe processes part of this data as our processor (for example payment processing for our subscriptions) and part as an independent controller for its own legal obligations, such as fraud prevention, anti-money-laundering and financial regulation; see Stripe's privacy policy. Stripe may transfer data to the USA, based on the EU-US Data Privacy Framework and standard contractual clauses.

VAT number check: for customers in other EU countries, we check the VAT number in the European Commission's VIES system before the payment page opens and again for every invoice; the request contains the VAT number and our own VAT number. We keep the result (valid or not, the company name and address VIES returns, the consultation number and the time) as evidence for the reverse-charge invoice, like the invoices themselves for 8 years (Art. 6(1)(c) GDPR).

We store the Stripe customer and subscription IDs, the plan, the billing interval, the subscription status and the invoice data. The legally valid invoice is issued through Számlázz.hu (KBOSS.hu Kft., Budapest), our processor, which receives the billing name, address, e-mail, tax number and the invoice amounts and reports the invoice to the Hungarian tax authority (NAV), which receives the data as an independent controller.

Legal basis: performance of the contract with the business customer, or our legitimate interest where the contact person is not the contracting party (Art. 6(1)(b) and (f) GDPR), and legal obligations for invoices and accounting (Art. 6(1)(c) GDPR; Sections 159–169 of the VAT Act, Áfa tv., and Section 169 of the Accounting Act, Szt.). Invoices and accounting records are kept for 8 years, also after the workspace is deleted.

5. What the browser extension sends

The extension works only on websites that belong to one of your projects; the browser asks for permission per website. It communicates only with the mumus server you signed in to:

WhenWhat is sent
Signing in and outA one-time code to get the login token; then your profile and project list are loaded
When you open the extension on a project websiteThe page address without query string, to load the existing reports (pins) for that page; opening a pin loads that task and its images
When you send a reportYour text; a screenshot of the visible tab (you can remove it before sending); the page address (sensitive parameters such as tokens removed), page title, the pinned element's position and selector; browser, operating system, language, time zone, window and screen size; recent console errors and failed network requests of that page (address, method and status, with secrets redacted)
Only when you start a recordingA video of the tab (no audio); the browser shows a recording indicator (Chrome and Edge; Firefox doesn't offer tab recording to extensions)
When you comment or change a taskThe comment or the change
Only if you are a project manager and accept the offerA screenshot of the page as the project's preview image

The extension does not track your browsing, does not read websites outside your projects, contains no analytics and shares nothing with advertisers. The login token stays in the extension's background process.

Dictation (microphone button): you can dictate the title and description of a report instead of typing them. The extension uses the microphone only while dictation is running (the browser asks once for microphone permission and shows when it is in use). Where Chrome offers on-device speech recognition for your language, speech is converted to text on your computer: the audio never leaves it. If on-device recognition isn't available, the extension asks you once whether it may use your browser's online speech service instead; only if you agree does Chrome send the audio to Google's speech service to convert it to text, under Google's own privacy terms (Google is not our processor for this). In Microsoft Edge, the same applies to Microsoft's speech service. In both cases mumus receives no audio, only the text that ends up in the form and that you choose to send. The extension keeps your dictation language and whether you allowed the online service in its own storage; you can change both in the extension's settings.

Redaction has limits. Before upload, the extension removes known secret formats (for example API keys, JWTs and bearer tokens), values of parameters and fields with secret-looking names (such as token, password, session) and e-mail addresses from addresses and log messages; the server applies the secret rules again. Request and response bodies, headers and cookies are never captured. Redaction doesn't work on what is visible in screenshots and videos or on what you type, and it can miss unusual formats, so please check before sending.

This data is workspace content: the organisation is the controller (section 2).

6. Reports by e-mail and through the website widget

  • E-mail: a message to a project's secret address arrives in our report mailbox at IONOS (Germany), which mumus reads and empties every minute. We check its DKIM signature and the sender's membership, and store the subject, text, attachments and sender as a task. Messages that fail these checks are discarded; only a log line with the reason and the sender's domain remains in the server logs (section 8). The sender receives a confirmation.
  • Widget: it does nothing for normal visitors of the website. For signed-in reporters, it sends the report text, the optional screenshot, the page address, the pinned element, the browser, operating system, language, time zone, screen and window size, orientation and uncaught JavaScript errors of that page, and, on a browser where a reporter is signed in, recent console messages and failed network requests of that page (address, method and status; secrets, e-mail addresses and sensitive parameters redacted; no request or response contents). It stores a "1" flag in the website's local storage and a sign-in token (7 days) in the storage of the mumus frame.
  • CMS connectors: an organisation can connect its WordPress, TYPO3 or other system, which then signs in its own logged-in users to the widget. We receive their name and the user ID that system sends and keep a reporter record for them (no mumus login, no e-mails); the widget keeps a sign-in token (1 day) for each such person in the storage of the mumus frame. The organisation decides who may report this way and is the controller (section 2).

These reports are workspace content (section 2).

Time entries that members log on tasks (person, task, date, duration, note) and the AI agents an organisation creates for first-level support are workspace content too: the organisation is the controller, and AI agents are not people.

7. Optional usage analytics (only with consent)

If you click “Accept all” in the cookie banner, or turn on “Optional usage analytics” in the preferences, we measure how the mumus website and web app are used, to find confusing flows. We do this ourselves, on our servers in Germany, without third-party tools:

  • Page views: only the page type (for example “project board”), never IDs, task addresses or query strings.
  • Clicks on interface elements: an identifier defined by our developers (for example “new task button”) and the position relative to the page. Never text content, form input or keystrokes.
  • Rapid repeated clicks on one spot, scroll depth, time on the page and the window width (rounded).

The events are linked to a random ID that exists only for one browser-tab session (mumus-analytics-session in session storage), and to whether the visitor was signed in. We store no user ID, e-mail address or IP address with them. This makes the data pseudonymous, not anonymous, so we treat it as personal data. No tracking across other websites, no profiling. Events are deleted after 90 days.

Legal basis: your consent (Art. 6(1)(a) GDPR, Section 155(4) Eht.). Without consent, nothing is measured: the browser sends nothing, and the server also discards events that are not covered by a recorded consent. Your choice is recorded as a consent receipt: a random ID, accepted or rejected, the notice version, a fingerprint of the banner wording you saw, and the time; no name, e-mail, account or IP address. The receipt ID is stored in the mumus_consent cookie and on the analytics events collected under it, so we can show that each event was covered by consent. Receipts are deleted after 13 months (legal basis: our legal obligation to be able to demonstrate consent, Art. 6(1)(c) and Art. 7(1) GDPR). You can withdraw consent at any time under “Cookie settings” in the footer or the account menu; measurement stops at once and the session ID is deleted. Details: cookie policy.

8. Operating and securing the service

To provide support, enforce storage limits and bill correctly, we look at usage figures per organisation, such as the number of members, projects and tasks, the storage used, the subscription status and the last login. We don't read report content for this. Legal basis: our legitimate interest in a stable, fairly used service (Art. 6(1)(f) GDPR).

Our servers write technical logs (IP address, time, requested address, status code, browser) and security events (for example failed logins, rejected tokens) to keep the service secure. Logs contain no report content. They are deleted after 30 days at the latest (and are also limited in size). If a security incident requires it, we keep the relevant entries separately as evidence for as long as the incident needs. Legal basis: our legitimate interest in IT security (Art. 6(1)(f) GDPR). We provide the balancing test on request.

Error tracking: to find and fix errors, we can use an error-tracking service. It receives the error type, a cleaned error message, the code location (stack trace), the HTTP method and the page path with IDs and tokens removed, the software version and the internal account ID; never IP addresses, e-mail addresses, names, cookies, request contents or query strings. Events are kept for at most 30 days. Legal basis: our legitimate interest in a reliable, secure service (Art. 6(1)(f) GDPR). If we use an external provider for this, it is listed in section 11 before it receives any data.

Breached-password check: when you choose a password, the first five characters of its SHA-1 hash are checked against Have I Been Pwned (k-anonymity). The password itself never leaves our server.

9. E-mails from mumus

Service e-mails: we send e-mails that belong to the service you use, for example invitations, notifications you chose, password resets and invoices, and announcements about maintenance, security and important changes to the service or the terms (for example the 30-day notice of a terms change). When the browser extension is connected to your account, we send you a security notice with the time and the approximate browser and operating system (read from the browser's User-Agent; no IP address or location), so that you can spot a connection you didn't make. We send these to workspace owners or to all users, depending on the topic. They are not advertising and you can't unsubscribe from them while you have an account. We keep a record of which announcement was sent to which account, with the delivery status and time, as proof that we informed you, for 5 years after sending (see below). Legal basis: performance of the contract (Art. 6(1)(b) GDPR) for customers, and our legitimate interest in informing users about the service and its security (Art. 6(1)(f) GDPR) for invited users.

Product newsletter (only with consent): if you opt in, at sign-up (the box is not ticked by default) or later under Account → Notifications, we occasionally send you news about new features and tips. We use your e-mail address and language and store evidence of every opt-in and opt-out: yes or no, the date and time, where you did it (sign-up form, account settings or unsubscribe link) and the version of the wording you agreed to; no IP address or device data. We record which newsletter was sent to your account; we don't track opens or clicks. Legal basis: your consent (Art. 6(1)(a) GDPR and Section 6(1) of the Hungarian Act XLVIII of 2008, Grt.). Consent is voluntary and not a condition for using mumus. You can withdraw it at any time, free of charge and without logging in, with the unsubscribe link in every newsletter (also your e-mail program's “Unsubscribe” button) or in your account settings; it takes effect immediately, also for a sending in progress, and doesn't affect earlier sending (Art. 7(3) GDPR). E-mails are sent through our hosting provider IONOS (section 11).

How long we keep these records: We keep the record of your newsletter consent (whether you subscribed or unsubscribed, when, where and which wording you saw) while you are subscribed and for 5 years after you unsubscribe or delete your account, and the record that a service announcement or newsletter was sent to you for 5 years after sending, so that we can prove consent and notices if a claim is made (GDPR Art. 5(2) and 7(1); legitimate interest under Art. 6(1)(f); general limitation period of 5 years, Section 6:22 of the Hungarian Civil Code). If you delete your account, we keep these records without your name or e-mail address: they are linked only to a keyed, irreversible code computed from your e-mail address, which lets us check a later claim made with that address.

10. Customer stories

On our customer stories page, we only publish names, photos, logos and quotes of people and companies who have given us their written consent (Art. 6(1)(a) GDPR). Consent can be withdrawn at any time, and we will then remove the story.

11. Service providers and recipients

RecipientPurpose and dataRoleLocation
IONOS SE, Elgendorfer Str. 57, 56410 Montabaur, GermanyServer hosting (all data in this policy), sending e-mails (invitations, notifications, password resets), mailbox for reports by e-mailProcessorGermany
Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, GermanyEncrypted off-site backups (encrypted before transfer)ProcessorGermany
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 where neededProcessorRomania / EU
KBOSS.hu Kft. (Számlázz.hu), BudapestIssuing invoices, NAV reporting: billing name, address, e-mail, tax number, amountsProcessorHungary
Stripe Payments Europe Ltd., Dublin, IrelandPayments, customer portal, VAT ID check, tax calculation: billing contact and payment dataProcessor and, for its own legal obligations, independent controllerIreland; transfers to the USA under the EU-US Data Privacy Framework and standard contractual clauses
Nemzeti Adó- és Vámhivatal (NAV)Invoice data reporting required by lawIndependent controllerHungary
European Commission (VIES) and the tax authority of the customer's countryChecking EU VAT numbers: the VAT number and our VAT numberIndependent controllersEU

AI assistants you connect yourself (for example Claude Code or Codex) receive the task data they request with your token; you control and revoke these tokens, and the AI provider is your own contractual partner, possibly outside the EU. We add or replace providers only after updating this policy; for workspace content, the procedure in the data processing agreement applies.

12. How long data is kept

  • Workspace content (reports, comments, files): until the organisation deletes it or the workspace.
  • Cancelling a subscription doesn't delete anything: the workspace becomes read-only. If it stays without a subscription for 6 months, we announce the deletion to the owners by e-mail with a date at least 30 days ahead, and delete it from that date on, at the latest 30 days after it.
  • Deleting a workspace (by its owner): read-only at once, purged automatically after 30 days.
  • Deleting your account: your account, tokens, memberships, notifications and settings are deleted at once. Workspaces where you are the only member are deleted with it. Comments and reports you wrote in other organisations' workspaces stay there, because they belong to that workspace's history, but are shown as “Deleted user”; the organisation can delete them. Newsletter consent records and records of e-mails sent to you are kept in pseudonymised form, as described in section 9.
  • Usage analytics: 90 days. Consent receipts: 13 months. Logs and error-tracking events: 30 days. Sign-up and reset links: deleted after 7 days.
  • In-app notifications: read notifications are deleted 6 months after they were read; unread ones are kept until they are read or the account is deleted. The due-date reminder log (task, user, due date, time sent) is deleted 6 months after sending, and the “last opened” markers of tasks (which show new activity) 6 months after the task was last opened.
  • VAT number checks (VIES): 8 years, like the invoices.
  • Newsletter consent records: while you are subscribed, then 5 years after you unsubscribe or delete your account. Records of platform e-mails sent to you (service announcements, newsletters): 5 years after sending; the e-mail's content is deleted together with its last record. After account deletion both are kept in pseudonymised form (keyed code of the e-mail address, no address or name) and are deleted automatically at the end of the period.
  • Invoices and accounting records: 8 years (Section 169 Szt.).
  • Backups: nightly server dumps are kept 14 days; off-site backups are kept for about 3 months. Deleted data disappears from them when the last backup that contains it expires; until then, backups are used only to restore the service. If we ever restore a backup, we re-apply the deletions made since the backup date before the service is used again.

13. Cookies and local storage

Strictly necessary: a session cookie for sign-in and form protection, a cookie that stores your privacy choice, and settings you make yourself, kept only in your browser (for example your theme, dismissed notices, open or closed panels and unsent drafts). Optional usage analytics only with consent. No advertising or third-party analytics. Full list: cookie policy.

14. Your rights

You have the right of access, rectification, erasure, restriction, data portability and objection to processing based on legitimate interest (Art. 15–21 GDPR). You can withdraw consent at any time with effect for the future (Art. 7(3) GDPR). Write to privacy@mumus.app; we answer within one month (Art. 12(3) GDPR). For workspace content, we forward your request to the organisation that is the controller and support it.

Self-service: delete your own account under Account settings → Delete account. Workspace owners can download a complete export (JSON, CSV and all files) and delete the workspace under Workspace settings → Data & deletion.

Complaints: Hungarian National Authority for Data Protection and Freedom of Information (NAIH, Falk Miksa utca 9–11, 1055 Budapest; postal address 1363 Budapest, Pf. 9.; naih.hu), or the authority of your EU country. You can also go to court (Section 23 Infotv.), also at the court of your place of residence. Please contact us first, so we can solve the problem quickly.

15. Security, automated decisions, changes

TLS for all connections, two-factor login, optional single sign-on, role-based access per project, private file storage and encrypted secrets; details on the Security page. We handle personal data breaches under Art. 33–34 GDPR. We make no automated decisions and do no profiling (Art. 22 GDPR). We update this policy when the processing or the law changes and inform users by e-mail about significant changes.