Privacy policy
Last updated 18 November 2026
This is a description of what actually happens, written so that each sentence can be checked. It covers this website, the server that issues licences, and the MacRoom app.
The website
The site sets no cookies and stores nothing in your browser. It counts visits with Webyz, an analytics service that records the page you visit, the site that sent you, your screen size, how long a page was in front of you and how far you scrolled, links you follow to other sites, files you download, and pages that were not found. Webyz identifies no one: visits are counted from a hash computed on its server that changes every day, and nothing is kept in your browser unless you opt out, which stores only that choice. If your browser sends Do Not Track, nothing is counted at all. The site is served through Cloudflare, whose network logs requests, including your IP address, under Cloudflare's own privacy policy. Our own web server keeps standard request logs for a short time for operating the site.
Buying a licence
Payment is taken by Paddle, the merchant of record. Your card, billing address and tax details go to Paddle and never reach us; Paddle's privacy policycovers them. When a purchase completes, Paddle tells our server the transaction id, and our server reads back from Paddle the email address you bought with. Those two values are written into your licence and the licence is emailed to that address through Resend, a transactional email provider. Our server stores nothing: there is no customer database, and the licence can be regenerated from Paddle's record alone, which is what the "get your licence again" page does.
The app
MacRoom has no analytics, no crash reporter and no account. It checks your licence on your own Mac against a public key built into the app and never contacts a server to do so.
Nothing sends network traffic unless you asked for the thing that does. These are all of them, besides MacRoom updating itself, which is described below:
- The speed test, the round trip check and looking up your public address use Cloudflare's public endpoints, with no account and no key. Cloudflare sees your IP address, as any site you visit does.
- Checking your other apps for updates, when you ask for a check, sends the bundle identifier of each App Store app and the region your Mac is set to, to Apple's App Store lookup, and reads the update feeds their own developers publish.
- Homebrew commands MacRoom runs for you, listing what is installed when you open that page and installing or upgrading when you ask, talk to Homebrew exactly as they would from a terminal, including whatever analytics you have left Homebrew to send.
- The network inspector forwards the traffic you point at it to where it was going. With "Use MacRoom for This Mac" on, that is all of this Mac's web traffic, passed through on your Mac and held in memory. Its replay sends the request you chose to the address it was first sent to, or, with Edit & Replay, to the address you typed.
- SSH servers and tunnels you set up connect to those servers with your Mac's own ssh. A tunnel set to start when MacRoom opens connects at launch and reconnects by itself.
- Connecting a VPN from MacRoom starts the VPN you configured in System Settings.
- Container commands go to whichever Docker daemon your docker command is set to use.
- Sharing a local port. If you choose to share a port, MacRoom opens an SSH connection from your Mac to the service you pick in the confirmation, localhost.run or srv.us, and traffic to the public address passes through that service to the port you shared. The service can see that traffic and your IP address, and srv.us also sees your SSH public key, which is how it identifies you. Nothing is sent until you confirm, nothing is sent to MacRoom or its developer, and the connection ends when you stop sharing, when its time is up, when your Mac sleeps or when MacRoom quits. These services are run by third parties under their own terms.
- Plan limits on the AI usage page are asked of the Claude Code and Codex tools already installed and signed in on your Mac, while that page is open. Each tool contacts its own provider under your account, as it does when you use it. MacRoom never opens their login files or your keychain, and sends them none of your prompts or files. When a tool does not answer, the limits may be read from the Claude desktop app's own usage file on your Mac.
- A web search, a bookmark, a link read from a QR code, an App Store page or the page to buy a licence opens in your browser. MacRoom itself sends nothing.
- Scripts, automation rules and Shortcuts you add yourself do whatever you made them to do.
What stays on your Mac
Clipboard history, snippets, notes, timers and the hours you worked, power history and cleanup history stay in files on your Mac, readable only by your user account. Your licence, which holds the email address you bought with and the transaction id, is kept the same way. Screenshots, recordings and files you export are ordinary files where you saved them. Nothing syncs and nothing is uploaded. Some things are never written down at all: recent notifications and network inspector traffic are held in memory and are gone when MacRoom quits, unless you export a capture yourself.
Several features read information that is already on your Mac, and it goes no further than the app:
- Token counts are read from the records Claude Code and Codex keep on your Mac. Only the counts, the model, the time, the session's id and the project folder's name are read, never the prompts, files or answers beside them.
- Browser bookmarks are read from your browsers' own files so the palette can search them.
- Contacts are read only if you switch that on, and are held in memory for the palette to search.
- The camera preview shows your camera in a window while it is open. Nothing is recorded or kept.
- Screenshots, recordings and text recognised from the screen are made and kept on your Mac. Recognition runs offline.
- Your Wi-Fi network's name needs the Location permission, because macOS requires it. MacRoom never reads your position.
A permission is asked for when you first use the feature that needs it, or, for notifications, when the first alert or timer is due, never at launch, and each can be withdrawn in System Settings.
When you write to us
If you email us, we receive your address and what you wrote. Our support address is a Gmail address, so Google carries that mail under its own policy. If you use Report a Problem, the app builds a report and shows you all of it before you send it yourself from your own mail app: what you wrote, the MacRoom and macOS versions, your Mac's model, chip and memory, whether you are on a trial or licensed (never the licence itself), which sections and switches are on, and up to the last hour of MacRoom's own log, with the path of your home folder removed. You can leave the diagnostics out. We use it to fix the problem and to reply.
Updates to MacRoom
MacRoom checks for a newer version of itself when you press Check for Updates, and on a schedule only if you agree when it first asks. A check fetches a list of releases from macroom.app. Like any request to this site, it reveals your IP address, and it names the version of MacRoom you have. Beyond the ordinary headers any web request carries, nothing about you or your Mac is sent, and the app sends no system profile. Installing an update downloads it from macroom.app, and it is installed only if it is signed with MacRoom's update key.
Your rights
Because our server stores nothing, there is nothing to export or delete there. Paddle holds the transaction and handles requests about it under its own policy. If you have emailed us and want that correspondence deleted, ask and it will be.
Questions go to [email protected].