Morse privacy policy

Last updated: October 25, 2026. This covers the Morse app and the morse command. It is checked against the code in this repository. If the two ever disagree, open an issue.

The short version

• There is no Morse account and no Morse server. Morse collects nothing about you and sends nothing to the people who make it.
• When you ask for a change, Morse sends what it needs to write that change to the model you chose: Claude Code, Codex, or an Anthropic, OpenAI or other API address you entered.
• When you open the bar or the Mods panel, Morse may download the gallery list of mods other people made, from GitHub Pages. It does this at most once a day.
• When you run morse doctor, the morse command asks npm whether a newer version is out. It does this at most once a day.
• A few things you can choose to use send data elsewhere. They are listed below under "Only when you use them".
• Nothing else leaves your computer.

What is sent to your model, and when

Morse sends something only when you send a request. That means you type or say a change or a question, ask for more on a result, or use "Explain this page", "Describe this picture" or a "Fix it" that needs the model. It also sends when one of your saved mods stops working on a page, if you turned on "Fix my mods automatically when a site changes". That setting is off until you turn it on.

Sent to the model you chose:

• what you typed or said
• the address and title of the page or app window
• the HTML of what you pointed at, and the page's layout, headings and button labels around it. This can include text that is on the screen, such as message previews or names.
• the CSS rules that style what you pointed at, and the app's look: its colors, fonts and sizes, a few of its buttons, fields and lists near what you pointed at, and which icons it uses
• with "Polish changes" on (it is on unless you turn it off), after a change that adds or restyles something: a screenshot of that part of the page or window with the change applied, without Morse's own bar, so the model can check the change fits the app and fix it once
• when you ask for more, or use Fix it: the code of the mod and the error it hit
• for "Describe this picture": the picture, or a screenshot cropped to it
• for "Show me once": the steps you did on the page while it was recording, such as what you clicked and what you typed. What you type in password and card number fields is never kept or sent.

Where it goes depends on your choice:

Claude Code and Codex are separate programs with their own privacy terms. Morse starts them and hands them the request. It does not see what they log.

Apart from that setting, Morse sends nothing to a model on its own. Opening the bar, pointing, the Edit tools, the other Page tools, "Easier to use", Read aloud and "Check this page" itself run on your computer. They send nothing to the model.

The gallery list

To show "Mods for this site", Morse downloads the list of gallery mods from https://getmorse.vercel.app/site/mods/index.json, and then the mod files that match the site you are on.

• It happens only when you open the bar or the Mods panel. The list is downloaded at most once a day.
• The request carries no cookies and nothing about you or the page. If you set a different list address in settings, the same goes to that address instead. The list is hosted at getmorse.vercel.app. Like any website, that host sees your IP address and which mod files were asked for. A mod file is named after the site it is for, so this can show that you visited that site.
• To turn it off, turn off "Show mods others made" in Morse settings. Then nothing is downloaded.

Checking for a newer version

morse doctor shows whether a newer version of the morse command is out. To know, it asks npm, where the command is published: https://registry.npmjs.org/morse-cli/latest.

• Only morse doctor asks. Nothing else in Morse does. (The Morse app checks its own updates on GitHub, below.)
• It asks at most once a day. The answer (the newest version number and when it was asked) is kept in ~/.morse/update-check.json.
• The request carries no cookies and nothing about you, your model, your mods or your pages. npm is run by GitHub. Like any website, it sees your IP address. If you set MORSE_UPDATE_REGISTRY to another address, the same goes there instead.
• To turn it off, set MORSE_NO_UPDATE_CHECK=1 in your environment. Then nothing is asked and nothing is kept.

Only when you use them

These send data somewhere other than your model, and only when you use them:

• Voice in a browser. In a browser opened with Morse, Morse uses the browser's own speech recognition. Chrome sends your voice to Google to turn it into text. If you never use voice, no audio is recorded.
• Voice in desktop apps. Morse turns speech into text with OpenAI (when you gave it an OpenAI key) or with Whisper on your computer (nothing leaves your computer).
• Read aloud. Morse picks a voice installed on your computer. If there is none, the browser uses its default voice, which can be an online Google voice.
• Sharing. A share link holds the whole mod after the #. Browsers do not send that part to a server, so the install page at GitHub Pages never sees the mod. You decide who gets the link. The "Post" button opens x.com with your request and the link filled in. The link holds the mod. Nothing is posted until you post it.
• Mod packs from an address. When you install a pack from a web address, Morse downloads it from there. If you chose to get its updates, Morse checks that address at most once a day. The request carries no cookies and nothing about you or the page. Like any website, that server sees your IP address. "Stop updates" in the Mods panel ends it.
• Submitting to the gallery opens a new GitHub issue with your mod in it, in your browser. Nothing is posted until you click Submit on GitHub.
• Updates. The Morse app checks the "preview" release on GitHub for a newer version when it starts and every 4 hours, and downloads it when there is one. The request carries nothing about you; like any website, GitHub sees your IP address.

What stays on your computer

• Your mods: in ~/.morse/mods, for apps and websites alike.
• Your API keys: in ~/.morse/config.json, which only you can read. They are sent only to the service they are for.
• Your past requests, backups and exports.
• What you asked, and a picture of the part you pointed at, go to the model you chose when you press Enter, and nowhere else.

What mods can do

A mod is code that runs inside the page or app it is for, like any userscript. It can see what you see there. Your model writes the mods you make, when you ask. Before you install a mod from someone else, Morse tells you what it does and lets you read its code. Morse does not check what a mod sends over the network. Read the code, or don't install the mod.

Things Morse never does

• No analytics, tracking, crash reports or ads.
• No selling or sharing of data. Morse has no data to sell.
• Nothing is sent from a page until you use Morse there. Morse runs on every page so its shortcut works and your saved mods run. It only looks at a page to answer you.

Children

Morse is not made for children under 13 and collects nothing from anyone.

Changes

Changes to this policy are made in this file, so its history on GitHub shows every change. If you have a question, open an issue.