Skip to content

Privacy Policy

Effective 18 November 2026

1. Who makes Mucq

Mucq is made by Dangerous kangaroos, s.r.o., Krátká 190, 267 16 Vysoký Újezd, Czech Republic, company ID (IČO) 17179831, entered in the Commercial Register under C 367795, kept by the Municipal Court in Prague. We are the controller of the personal data this policy describes. Questions about this policy or your data: support@mucqapp.com.

2. What stays on your device

Your servers, projects and settings are stored on your device, in Mucq's own storage. Passwords, imported keys and the device key are kept in your device's Keychain and Secure Enclave; the device key's private part never leaves the Secure Enclave. The host keys you confirmed and Mucq's log are stored on your device too.

3. Network

Mucq connects only to the servers you add, directly over SSH. It uses Local Network access only to reach servers on your local network. Push notifications on iPhone and iPad reach your device through Apple and our relay, as section 6 describes.

4. Files

Mucq sends a file to your server only when you send it. To preview a file, it downloads the file from your server into its own cache on your device; the cache is emptied each time the app launches.

5. The log

Mucq's log stays on your device. It leaves your device only when you share it.

6. Push notifications (iPhone and iPad)

If notifications were never turned on, and on the Mac, nothing ever goes through our relay. When you turn notifications off in Mucq, it unregisters your device from every server it is connected to within seconds, and from any other server the next time it connects to it; from then on nothing goes through our relay for that device. If you deny notifications in iOS Settings instead, Mucq unregisters the device the next time you open it. Until a server's registration is removed, that server may still send your device's token to the relay, but never a name or any content.

When notifications are on, Mucq can tell your iPhone or iPad that Claude needs you or has finished, even while the device is locked. This works without an account and without Mucq storing anything about you.

What happens on your server. When your iPhone or iPad with notifications on connects to one of your servers, Mucq installs a small script there (~/.local/share/mucq/notify) and registers the device over your own SSH connection. Registering writes one file per device into ~/.config/mucq/push/ on that server. The file holds a random device identifier, the app's identifier, your device's push environment and its push token, the address Apple gives your device for notifications. The folder also holds a random secret (a salt) that Mucq creates there. Nothing about the registration is sent to us.

What is sent when Claude needs you or is done. Unless a Mucq app that checks that server counts you as present at that moment (a Mac that is unlocked, awake and in use within the last couple of minutes, or an iPhone or iPad with Mucq open in front), the script on your server sends one request to Mucq's push relay at push.mucqapp.com. The request contains:

  • whether Claude needs you or is done;
  • the push tokens and random identifiers of the devices registered on that server;
  • the app's identifier and each device's push environment, which Apple needs to route the notification;
  • a tag: a one-way hash of the session's name, salted with the secret that only your server and your devices know.

It never contains the names of your projects, sessions or servers, file paths, your prompts or anything Claude writes. The same session always gets the same tag, so notifications for one session can be linked with each other, but not traced back to its name without the secret. Like any internet connection, the request comes from your server's IP address.

What the relay does. The relay passes each notification to the Apple Push Notification service (APNs) with fixed text only: “Claude needs you”, or “Claude is done”, and “A session on one of your servers is waiting for you”, or “…has finished”. On your device, Mucq replaces that text with the project and server names from a list it keeps on the device itself. Those names never leave your server and your device. The relay stores nothing: it has no database, it does not log requests, and its logging is turned off. It processes each request only for the moment it takes to deliver it. To prevent abuse, it limits how many notifications a device token or an IP address can trigger per minute; the counters behind that limit last about a minute. When Apple reports that a push token is no longer valid, the relay says so in its answer, and the script deletes that device's file from your server.

Who processes the data. The relay runs on Cloudflare Workers. As our infrastructure provider, Cloudflare processes connection data such as IP addresses to deliver and protect the service, under Cloudflare's privacy policy. Apple processes the push token and the notification to deliver it to your device, under Apple's privacy policy.

Your control.

  • Turning notifications off in Mucq's Settings, or denying them in iOS Settings, removes your device's file from each server the next time Mucq connects to it. Deleting a server in Mucq removes it there too, if the server can be reached.
  • When the last device is unregistered from a server, Mucq removes the script and the folder from it.
  • You can also delete ~/.config/mucq/push/ on a server at any time.
  • The Mac apps never use push: they show notifications locally on your Mac.

7. What we receive

Mucq has no analytics, no tracking and no account. With push notifications on, our relay handles the data described in section 6 only while it delivers each notification, and keeps none of it. Beyond that, we see only what you send us yourself, such as a support email, and what sections 8 and 9 describe.

8. Apple's crash reports

If you share analytics with app developers in your device's settings, Apple may send us crash reports from Mucq. This is Apple's setting, and you can change it at any time.

9. This website

mucqapp.com is a set of static pages. It sets no cookies. To count visits, it uses Cloudflare Web Analytics, which stores nothing in your browser and, as Cloudflare states, does not fingerprint visitors. It records the page you view, the page you came from, your browser, operating system and device type, your country and how fast the page loads. Our host, Cloudflare, processes the technical data every web request carries, such as your IP address and browser, to deliver and protect the site.

10. Launch e-mails

The site's “Email me at launch” and “Join the Pro waitlist” buttons open your own mail app with a message to us; the site itself does not collect your address. If you ask to be told about the launch, we use your address only to reply and to tell you once when Mucq or Mucq Pro is available, and then we delete it. Other e-mail to us is kept as section 11 says.

11. Legal bases and how long we keep data

We process personal data only for the purposes this policy describes, on these legal bases under the GDPR:

  • Push notifications (section 6): delivering the notifications you turned on, as part of the app you use (Article 6(1)(b)), and protecting the relay from abuse, our legitimate interest (Article 6(1)(f)). Once a notification is delivered, only the counters behind the rate limit remain, for about a minute.
  • E-mails you send us: answering you (Article 6(1)(b), or our legitimate interest in replying, Article 6(1)(f)). We keep a support conversation for at most two years after its last message, then delete it.
  • Launch e-mails (section 10): your request to be told, which you can withdraw at any time by writing to us (Article 6(1)(a)). We delete your address once we have told you.
  • This website (section 9): delivering and protecting the site, and counting visits with Cloudflare Web Analytics, our legitimate interest (Article 6(1)(f)).
  • Crash reports (section 8): finding and fixing crashes, our legitimate interest (Article 6(1)(f)), and only if you allowed Apple to share them with us.

12. Who else processes data

  • Cloudflare, Inc. hosts this website and counts visits to it, runs the push relay, and forwards e-mail sent to our address to our mailbox.
  • Apple delivers push notifications through APNs and, if you allow it, sends us crash reports.
  • Our e-mail provider stores the e-mails you send us.

Cloudflare and Apple may process data outside the European Union, including in the United States. Such transfers rely on the EU–U.S. Data Privacy Framework or on the European Commission's standard contractual clauses.

13. Your rights

You have the right to access the personal data we hold about you, to have it corrected or erased, to restrict its processing, to object to processing based on our legitimate interest, to data portability, and to withdraw a consent at any time; withdrawing does not affect what was done before. To use any of these rights, write to support@mucqapp.com.

Most of what Mucq handles never reaches us (sections 2, 4 and 5): it stays on your devices and your servers, where you control it yourself.

You can also complain to a data protection authority. Ours is the Czech Office for Personal Data Protection (Úřad pro ochranu osobních údajů, uoou.gov.cz).

We make no automated decisions about you and do no profiling.

14. Contact and changes

Write to support@mucqapp.com. When this policy changes, we publish the new version on this page with its new effective date.