Morse vs Brave Leo: who reads your prompt, and who checks the enclave
The Morse teamPublished Facts checked 11 min read
In Morse vs Brave Leo, both keep your chat history on your device and neither trains on your chats, and they split on who can read a prompt and who checks. As of November 6, 2026, Brave runs 13 of Leo's models on infrastructure it says it operates itself, under a policy that it keeps nothing, and encrypts one model, GLM 5.3 Flash, end to end, with Brave's own server checking the enclave on your browser's behalf. Morse lets you choose per chat, and in an E2EE chat your browser checks the enclave itself before anything leaves your device. Choose Brave Leo if you want AI built into your browser, a model that runs on your own machine, or encrypted chat on a free plan; choose Morse if you want the check on your own device, GPT, Claude, and Gemini without your name on them, and over 30 models in one account.
On November 6, 2026, we read Brave's Leo page and its FAQ, the Leo section of Brave's browser privacy policy (dated September 23, 2026), five Leo articles in Brave's help center (models, Bring Your Own Model, ChatGPT, chat history, and memory), Brave's premium pricing page, and both of Brave's posts on Leo's trusted execution environments, from November 20, 2025 and October 15, 2026. We ran no tests. Brave earns credit for publishing the code for every stage of its encrypted pipeline, and its October post names its own remaining gap in plain words. For Leo next to Duck.ai and Lumo, see our three-way comparison.
Morse vs Brave Leo at a glance
As of November 6, 2026. Every Leo cell comes from a Brave page linked here or in the sections below.
| Morse | Brave Leo | |
|---|---|---|
| Where your prompt is decrypted | E2EE: only inside an enclave your browser verified. Anonymous: at the GPT, Claude, or Gemini provider, without your identity. Private: at hosts with zero data retention agreements | 13 models: on infrastructure Brave runs; its June 30, 2025 post says Claude and DeepSeek go "through AWS Bedrock with the same zero-retention configuration" (Brave). GLM 5.3 Flash: only inside NEAR AI's TEE (Brave) |
| Who verifies the enclave | Your browser, against versions pinned in the app | Brave's AI Gateway: "Today, your browser relies on the gateway for this check" (Brave) |
| Where chat history lives | In your browser, encrypted, locked when you sign out | On your device, "encrypted when stored," and in Brave Sync if you turn it on (Brave) |
| Trains on your chats | No | No (Brave) |
| Ads | No ads, no advertising trackers, no third-party analytics | None described on Leo's pages |
| Account | None to try a chat; an emailed code or Google to keep chats | None for free Leo; an account for Premium, kept apart from your use by "unlinkable tokens" (Brave) |
| Where it runs | Web app at trymorse.ai | The Brave browser on desktop, Android, and iOS (Brave) |
| Models | Over 30, open and closed | 5 free and 13 on Premium in Brave's table, plus GLM 5.3 Flash and your own through BYOM |
| Free plan | 15 messages a day, 3 images a day | "Reasonable rate limits," with no number |
| Paid plans | Pro $19 a month ($17 billed yearly), Max $49 | Premium $14.99 a month or $149.99 a year, with a 7-day trial (Brave) |
Can Brave read your Leo chats?
For 13 of Leo's models, Brave's servers process your prompt, and Brave's no-logs policy is the protection; for GLM 5.3 Flash, Brave says it can't read it at all. Brave's help center says every Leo model runs on Brave's own infrastructure (Brave), and a June 30, 2025 post says that for Claude and DeepSeek this means AWS Bedrock "with the same zero-retention configuration," which ended "the 30-day data retention that previously applied to Claude models under Anthropic's standard API terms" (Brave). Our three-way comparison quotes the rest of the retention policy.
Brave is candid about what that policy is. Its October post describes the protections its first enclave release ran under, "encrypted in transit, never logged, and discarded once a response was generated," and then says: "Those protections rested on our policies, not yet on cryptography" (Brave). Those are the same protections every Leo model except GLM 5.3 Flash runs under today.
Is Brave Leo end-to-end encrypted?
One model is: since October 15, 2026, GLM 5.3 Flash chats are sealed in your browser for a NEAR AI enclave, and Brave's gateway checks that enclave before your browser gets its key (Brave). Our three-way comparison walks through that relay and verifier, and what Oblivious HTTP is covers the protocol.
Brave's post describes its check closely enough to set beside Morse's.
| Brave Leo, GLM 5.3 Flash | Morse, E2EE chat | |
|---|---|---|
| How fresh the check is | The gateway re-checks before relaying each message, "using a verification no more than an hour old" | Your browser checks the enclave's hardware attestation itself before anything leaves your device |
| What it's checked against | Approvals recorded by Brave's verification oracle | Versions pinned in the Morse app; an OS image hash that differs fails |
| How each message is sealed | A fresh one-time key "each turn," and your browser "re-encrypts the entire conversation history" | Each message is sealed on your device for that enclave only |
| What you can see afterward | Brave's post and its public code | A lock on each reply listing every check that passed, and a full report you can download |
| What's next | Brave plans to "verify the hardware attestation directly, so you no longer need to trust any Brave server to vouch for the TEE" | Already in your browser |
Brave's Leo column comes from its October 15, 2026 post (Brave). Morse's guarantee rests on the enclave hardware and attestation working as designed, and our guide to verifying an AI enclave's attestation explains what each kind of check proves.
Every route a Leo prompt can take, and Morse's nearest
Leo's privacy depends on what you pick, and Brave's pages describe at least six routes. Each Leo cell comes from the Brave page linked in its row, read November 6, 2026; the Morse column shows the mode you'd use for the same job.
| What you pick in Leo | Who reads your words in Leo | Who sees your IP address in Leo | What Leo keeps | Morse's nearest route |
|---|---|---|---|---|
| A Brave-hosted model, such as Claude Sonnet 5.5, GPT 5.6 Terra, or Qwen 3.6 35B | Brave's model infrastructure, or AWS Bedrock for Claude and DeepSeek (Brave) | Brave says it's "proxied through an anonymization server" (Brave) | Nothing on Brave's servers past the reply, by policy | Anonymous for GPT, Claude, and Gemini: the provider reads it without knowing it's you. Private for DeepSeek, Kimi, GLM, and Grok: hosts with zero data retention agreements |
| GLM 5.3 Flash | Only code inside NEAR AI's enclave (Brave) | Brave's AI Gateway, which drops it before the enclave | "No conversation stored by Brave or NEAR AI" | E2EE with an open-weight model like GLM, Kimi, or DeepSeek: only an enclave your browser verified |
| A question answered with web results | Brave Search, which gets "queries derived from your input" (Brave) | In GLM 5.3 Flash chats, "Neither the TEE nor Brave Search ever sees your IP" (Brave) | For GLM 5.3 Flash, searches use the Search API's zero data retention option | Web search, on the Free plan too, under zero data retention agreements; none in E2EE chats |
| Bring Your Own Model, a local model such as one served by Ollama | Only your device: prompts "never leave your machine" (Brave) | No one | Your device | No equivalent |
| Bring Your Own Model, a remote API such as OpenAI's | The third party; "Requests bypass Brave's servers entirely" (Brave) | The third party, since Brave's "reverse proxy" doesn't apply | Whatever the third party's terms allow, including training | Anonymous: GPT, Claude, and Gemini sent under Morse's own account, with your account, email, and IP address removed |
| A thumbs up or down on a reply | Brave, which receives the "full text of the current conversation" (Brave) | Not stated | One year on Brave's servers | Morse doesn't train AI on your content |
Brave's help center has an article on how to "add my ChatGPT account to Brave Leo," which takes the fifth route, through an OpenAI API key (Brave), and Brave's Bring Your Own Model article warns that the third party may "Use your data for model training" (Brave). On Morse, the same models go through Anonymous mode under Morse's own account, and the provider may keep a message for a limited time to check for abuse, under its own policy. A Leo chat in a Private Window or Tor window is "never saved to history" (Brave); Morse's temporary chats are kept in memory only.
Where does Leo keep your chat history and memory?
On your device. Brave's help center says Leo conversations are "stored locally on your device only," "encrypted when stored," and removable under Settings, then Leo, with Clear Leo data, or by turning off Store my conversation history (Brave). Turn on Sync and the history joins your other Brave data in an encrypted file on AWS, with "the decryption key, which is stored on your devices," and an unused sync chain expires after 12 months (Brave).
Leo's memory is local too, and you add each memory yourself. Brave notes that memories "are included with your prompts," so they travel to the model with each message (Brave). Morse also keeps history in your browser, encrypted, and locks it when you sign out. Opening it takes one key that never leaves the device and one Morse's server gives you at sign-in, so a copy of the browser data alone can't be read.
Which models does each offer?
Leo has 5 models for free users and 13 on Premium in Brave's help center table, which our three-way comparison lists in full (Brave), plus any model you connect through Bring Your Own Model. That table, read November 6, 2026, leaves out GLM 5.3 Flash, the one encrypted model, which Brave's October post says is "available today to every Brave user" (Brave), and the Leo page's FAQ still names Mixtral and Llama, which the table doesn't list (Brave). Open Leo's model menu to see what you'll get.
Morse has over 30 models, open and closed, in one account, from GPT, Claude, and Gemini to DeepSeek, Kimi, GLM, and Grok, with Characters for roleplay and companion chats and Studio for images. Paid plans add unfiltered models, for dark fiction and straight medical and legal answers that other apps refuse; none of the Leo pages we read describes an unfiltered option.
Is Leo Premium cheaper than Morse Pro?
Yes. Leo Premium is $14.99 a month or $149.99 a year, with a 7-day free trial (Brave). Morse Pro is $19 a month, or $17 billed yearly, and Max is $49. Free Leo has "Reasonable rate limits" with no number published, while Morse Free gives you 15 messages a day, 3 images a day, and web search, with no card.
The plans buy different things. Premium adds models and "Higher rate limits" (Brave). Morse Pro adds E2EE chats, unlimited Pro models such as Claude Sonnet 5.5, DeepSeek V4.1 Flash, and Grok 4.7, unfiltered models, memory across chats, and 250 credits a month for frontier models.
Where Brave Leo is better
- A model on your own machine. Bring Your Own Model runs a local model on desktop, and Brave says the prompts "never leave your machine."
- Encrypted chat that can search. GLM 5.3 Flash calls Brave Search from inside the enclave. Morse's E2EE chats use only tools that run on your device, so they skip web search.
- Encryption on the free tier. Brave says its encrypted model is open to every Brave user; Morse's E2EE chats come with Pro.
- Claude under zero retention. Brave's June 2025 post says Claude runs through AWS Bedrock in a zero-retention configuration. On Morse, Claude runs in Anonymous mode, where the provider sees the message without knowing it's you and may keep it for a limited time to check for abuse.
- The page you're on. Leo summarizes the tab you're reading, PDFs, and Google Docs, and can organize your tabs (Brave).
- Open code for the encrypted path. Brave publishes its client, gateway, and verifier code, and NEAR AI publishes what runs in the enclave (Brave).
- A lower price. Premium is $14.99 a month, against $19 for Morse Pro.
- History on every device. Brave Sync carries Leo history between your devices, encrypted with a key kept on them.
How Morse puts the enclave check on your device
Leo's privacy rests on Brave twice: on its no-logs policy for 13 models, and on its gateway's word that the enclave is genuine for the fourteenth. Morse is built so the step you'd most want to check runs where you can see it, in your own browser.
- E2EE, for a prompt no server should read or vouch for. Your browser checks the enclave's hardware attestation against versions pinned in the Morse app, and fails the check if, say, the OS image hash differs from the pinned one. Then it encrypts the message so only that enclave can read it, Morse's servers relay ciphertext they can't read, and the reply is decrypted only in your browser. Each E2EE reply has a lock you can open to see every check that passed, and a full report you can download. The enclaves are run by third-party providers, not by Morse, and the guarantee rests on the enclave hardware and attestation working as designed. E2EE runs open-weight models like GLM, Kimi, and DeepSeek, without web search or image generation, and comes with Pro.
- Anonymous, for GPT, Claude, and Gemini without your name. Our proxy removes your account, email, and IP address and sends the message under Morse's own account, so the provider sees it without knowing it's you. It may keep it for a limited time to check for abuse, under its own policy, so leave out names and details you'd rather keep.
- Private, for DeepSeek, Kimi, GLM, and Grok on hosts that keep nothing. Morse has zero data retention agreements with its inference, search, and other providers. Where a provider confirms zero retention on each reply, Morse checks it and refuses a reply that doesn't.
In every mode, history stays in your browser, encrypted. Clearing the browser deletes it and Morse can't recover it, so keep a copy of anything you need. We don't train AI on your content, sell your data, or show ads, and because we don't store chats, we usually have very little to give authorities (privacy policy).
Brave Leo or Morse: which to pick
- Choose Brave Leo if you want Claude in the zero-retention setup Brave describes, encryption without paying, and Leo history carried between your devices by Brave Sync.
- Choose Morse if you want the enclave checked by your own browser against pinned versions, a report of that check you can download, Anthropic's and OpenAI's models with your account and IP address removed, unfiltered models on paid plans, and history that locks when you sign out.
Try a chat from the home page without an account, or start free with 15 messages a day and no card. With Pro, the lock on each E2EE reply lists the checks your browser ran.
Morse publishes this comparison. We've tried to keep it fair; if something's wrong or out of date, email hello@trymorse.ai.
Brave and Leo are trademarks of Brave Software, Inc. Morse is not affiliated with or endorsed by Brave Software, Inc.
Common questions
Is Brave Leo the same as Ask Brave?
No. Brave launched Ask Brave on September 29, 2025 as search and AI chat in one interface on Brave Search, free in any browser, while Leo is the assistant built into the Brave browser. The end-to-end encryption Brave announced in October 2026 covers Leo's GLM 5.3 Flash chats.
Can I use my ChatGPT subscription in Brave Leo?
Not a ChatGPT Plus plan. Brave's help center says adding ChatGPT to Leo requires you to be an OpenAI API customer, pasting an API key into Leo's Bring Your Own Model settings, and requests then go straight to OpenAI under its terms.
Do I need the Brave browser to use Leo?
Yes. Brave says Leo is available in the Brave browser for desktop (macOS, Windows, and Linux), Android, and iOS. Morse is a web app at trymorse.ai.
Which one has less to hand a court?
Brave's policy says it keeps no Leo prompts or replies on its servers, and Leo history sits on your device. Morse doesn't store chats on its servers, so it usually has very little to give authorities. This isn't legal advice.