Privacy

Version 2026-09-15.1 · last updated 15 September 2026

Memoe is in beta. You are early. The app changes often, so this page changes with it — what is written here is what today’s Moe does, and we will say so at the top when it changes. If you find something that does not match, tell us; that feedback is what keeps this page honest.

This policy is from Yisrael Gottlieb, a sole proprietor in New Jersey, United States, who makes Memoe (“we”, “us”). Write to hello@moebot.app about anything on this page.

The short version

• Free, on your Mac: your memories and conversations stay on your Mac. Moe runs there and keeps them there. What leaves is what you send to the AI you connected, the services you connect, and the few things listed below.
• Signing in with Google creates a Memoe account on our server. It holds your email address and nothing from your Mac. You need it for some connections, for problem reports that get a reply, and to pay. Everything else works without it.
• If you upgrade to Away, Moe moves in to a private computer in the cloud, just for you. Your memories, conversations and connections go with it, encrypted on the way. Our server stores your memories, conversations and AI sign-in in a form it cannot open. On your cloud computer they are readable, because that is where Moe thinks — and our staff do not look at it (see the no-look rule).
• We do not sell your data, share it for advertising, or use it to train models. We have no models.

Who Memoe is for

You must be 18 or older to use Memoe. We do not knowingly hold anything about anyone younger; if you believe we do, write to us and we will delete it.

What stays on your Mac

• Your voice. Speech recognition runs on your Mac using local models, and audio is not stored after it is transcribed. On the free tier your voice does not leave your Mac. On a paid tier with Cloud voice turned on it does — see Cloud voice.
• Memory. What Moe knows about you lives in plain Markdown and text files in ~/.moe and ~/.hermes. You can read, edit and delete them with any editor.
• Conversation history. Your conversations are kept as plain files in ~/.moe/conversations, with an append‑only record of what was said in ~/.moe/ledger. The agent keeps its own working store in ~/.hermes. On the free tier none of it leaves your Mac. If you upgrade to Away, a copy goes to your cloud computer — see Away.
• Meetings. A meeting is recorded only when you start it, and a red indicator shows the whole time. Recordings, transcripts and notes stay in ~/.moe/meetings on your Mac, readable only by your account; the audio is deleted once the notes are written unless you choose to keep it. There is one exception: if a recording produced almost no transcript, Moe keeps the audio anyway rather than delete the only copy of a meeting it may have failed to hear, up to half an hour of it. Any meeting can be deleted from Settings. If “Summarise with your AI” is on, the transcript goes to the AI you connected while the meeting is running — the newly transcribed lines about once a minute, so Moe can spot action items — and then the whole transcript once at the end to write the notes. A question you ask during the meeting sends the recent lines with it, and if you step away and come back, the lines you missed go once for the recap. Off, nothing about the meeting leaves your Mac. If notes are pushed to your own Telegram afterwards, they go through your assistant to your own account and nobody else’s.
• Credentials. A Claude subscription sign-in is stored in your macOS Keychain. A ChatGPT sign-in is held by the vendor’s own tool. An API key is written to ~/.hermes/.env, a file only your account can read. On the free tier none of them are sent to us. If you upgrade to Away, your AI sign-in goes to your cloud computer so Moe can think there.

What leaves your Mac, and when

• Requests to the AI you connected. When you talk to the agent, your request and the context it needs go to the provider you chose: Claude, ChatGPT, an API key with a provider, or a local model on your machine. From your Mac it goes there directly, through that vendor’s own tool or API, never through us. Your AI provider is yours, not ours: their privacy terms apply to what they receive, and they are not our sub-processor. When “Moe sees your screen when you talk to it” is on (it is by default), that context includes a screenshot of the screen under your cursor taken the moment you press the talk key, sent only when what you said looks like it is about the screen; that one is not saved to disk, and the switch is in Settings. When Moe works the Mac for you it does save what it sees, in ~/.moe/screen, keeping the five most recent.
• Connectors you set up. If you connect mail, a calendar, or a messaging service such as WhatsApp or Telegram on your Mac, Moe talks to that service directly from your Mac, the same way a mail client does. With Away, your own Telegram and WhatsApp are also reached from your cloud computer, which joins each as another device of yours — see Away. Some apps are connected through Composio instead — see Apps connected through Composio. If you let Moe make a Telegram bot for you rather than pasting a token, Moe uses a setup service run by Nous Research, the makers of Hermes, the agent inside Moe (setup.hermes-agent.nousresearch.com): it receives the bot’s name, has Telegram create the bot, and hands the bot’s token to your Mac once; after that the token lives on your Mac. Before the agent sends a message or an email on your behalf, it shows you exactly what will go out and waits for you to confirm.
• Downloads. On first use, Moe downloads the speech and voice models it needs from Hugging Face, and the installer fetches the agent runtime from GitHub. These are ordinary file downloads and carry no information about you.
• Update checks. Moe checks moebot.app/appcast.xml for a newer version. That is a plain web request saying which version of Memoe is asking; it sends no profile of your Mac and no identifier of yours.
• Problem reports, only when you ask Moe to send one — see Problem reports.

Mail you connect

Connecting a mailbox is optional and off until you do it. Moe reads Gmail over IMAP with an app password you create yourself at myaccount.google.com/apppasswords — for mail there is no Google sign-in and no key to your account held anywhere but your own Keychain. You can connect as many mailboxes as you like, personal and work.

• The password goes into your macOS Keychain, never into a file. The only thing written to disk is the address, the label you gave it, and the mail host, in ~/.moe/connectors/gmail-accounts.json, readable only by your account.
• Moe connects to your mail server directly from your Mac, over IMAP with TLS, the same way a mail client does. It does not pass through our server.
• Reading changes nothing. Moe opens your mailboxes read-only, so looking at your mail does not mark it read, move it or delete it.
• What it keeps. Every ten minutes Moe notes the date, the sender, the subject and whether it is unread, for the last day and the last fifteen messages only, into the brief in ~/.moe/context on your disk. Message bodies are not stored there.

The one place mail does travel, and it is your choice. The brief is part of what Moe tells your connected AI when you ask it something, so the senders and subjects in it go to the provider you chose — from your Mac, directly, under their terms. Ask about a particular message and the part needed to answer goes too. If you connected a local model, nothing leaves your Mac. Turn the mailbox off and none of it is gathered in the first place.

The deep read is separate, and it asks first. Moe can also read back over up to a year of your inbox and sent mail to learn how you write and who matters to you — once, and after that only what is new, once a day. It reads nothing without your yes for that mailbox: the first-run screen lists what is connected with each one ticked, and nothing is read until you save it (untick a mailbox to leave it alone); a mailbox you connect later is asked about on its own; and Settings › Background turns it off again. Each pass sends the text it read to your connected AI to be distilled; the raw text is written to ~/.moe/context/crawl, readable only by your account, and deleted as soon as the distilling is done. What survives is a digest you can read and delete in ~/.moe/memory/profile.

Taking it back. Revoke the app password at myaccount.google.com/apppasswords and Moe cannot reach that mailbox again, from that moment, whatever else is on your Mac. To clear what is on your Mac, use Disconnect on the mailbox in Settings › Connections, which removes both the saved password and the account entry; then delete the files under ~/.moe/context and ~/.moe/memory/profile — they are ordinary files, and deleting them is the deletion.

What Moe reads from your mail is never sold or shared with anyone for their own purposes, never used for advertising, and never used to train models — we have none. On the free tier it is never sent to us. If you upgrade to Away, what Moe has learned from it moves to your cloud computer with the rest of Moe’s memory.

Sending mail

Moe can also send mail from a connected mailbox, over SMTP with TLS, using the same app password. Nothing is ever sent without your explicit approval. A dialog shows the recipients, the sending address, the subject and the message before anything leaves your Mac, and nothing is preselected — Escape cancels it. If a message is long enough that the dialog cannot show all of it, it tells you exactly how many characters it is not showing.

Google Docs and Sheets

This is optional and off until you set it up. It uses Google’s drive.file permission, which Google classes as non-sensitive: Moe can only see the documents you personally pick in Google’s own file chooser, and nothing else in your Drive — not the files you did not pick, and not new ones.

• You choose the files. The picker is drawn by Google in your browser. Moe never sees your Google password.
• The sign-in token goes into your macOS Keychain, never into a file. What is written to disk is the list of files you picked — their identifiers, names, kinds and when you picked them — in ~/.moe/connectors/drive-docs-files.json, readable only by your account. No file contents.
• The reading happens from your Mac, directly to Google. It does not pass through our server.
• Taking it back. Disconnect in Settings › Connections hands the permission back to Google and clears the list. You can also revoke it yourself at myaccount.google.com/permissions.

As with mail, the contents of a document you asked about travel to the AI provider you chose, from your Mac, under their terms.

Your calendar, contacts and files

Calendar events, contacts, reminders and notes are read from the apps already on your Mac, so Google calendars you have added to Calendar work with no sign-in of any kind. Files in Google Drive are read from the folder Google’s own Drive for Desktop app syncs to your Mac, if you have it — again with no sign-in to us. Chrome browsing history is off unless you switch it on, and when on it records page titles and sites, never the query strings in an address.

Signing in with Google

Signing in is optional. It asks Google for your email address and nothing else — not your name, not your contacts, your Drive or your calendar. What we keep is that address and the account number Google gives us for you, in a Memoe account on our server. We send one welcome email when you first sign in.

Signing in uploads nothing from your Mac. The account exists so that connections made through Composio belong to you and nobody else, so a problem report has somewhere to send the reply, and so a subscription belongs to somebody. Signing in means you agree to the Terms and this policy. Moe records that agreement on our side when it can: it is signed on your Mac and sent right away, with the date and the versions of both.

How an agreement is recorded. Only Moe on your Mac can record that you agreed. Each agreement is signed by a key that only the Memoe app can use, and we record which versions you agreed to and when. If a key for agreeing is set up on another Mac, or the one on your Mac is replaced, we email you.

Apps connected through Composio

Some apps in Settings › Connections are connected through Composio, a service that holds the sign-in to that app and carries Moe’s requests to it. When you connect one, we create a Composio project that is yours alone, so the key your Mac holds can reach your connected accounts and nobody else’s. Composio holds the sign-ins for those apps; what Moe asks of them passes through Composio to the app and back. Our Composio account can administer your project — that is how it is made and how it is deleted — and that is covered by the no-look rule like everything else of yours we hold.

Away: your own computer in the cloud

Away is a paid upgrade. Before it starts, Moe shows you what is about to happen and asks you to agree, and we record the agreement with the date and the versions of these documents. Agreeing does not start the copying: copying starts once your plan is active. If you agree and then leave the payment page, nothing leaves your Mac.

What moves. Your memories and the conversations you’ve had; what Moe knows about you and how you like things done; the apps and accounts you’ve connected; the ways you message Moe; and your AI sign-in. Your own Telegram and WhatsApp come too, in the one way they can: your cloud computer becomes one of their devices, so it can read and send there — your Mac lets it into your Telegram by itself, and WhatsApp asks you to type a code on your phone. It shows among each app’s linked devices, and you can remove it there; Moe does not add it back by itself. From then on, what Moe learns on either side is kept in step.

Where it goes. To a computer rented from Fly.io in Ashburn, Virginia, United States, which runs only your Moe. Our own server — which also runs on Fly.io in Virginia, with its database at Neon in the same region — carries things between your Mac and that computer.

How it is protected, precisely.

• Your memories, conversations and AI sign-in, on the way and on our server: encrypted on your Mac with keys that only your devices hold. Our server stores them in a form it cannot open.
• On your cloud computer: readable. That is where Moe thinks, so it has to be able to read your conversations, memories and AI sign-in there, the same way your Mac does. Its disk is yours alone, but it is not encrypted against us: someone with access to our Fly.io account could technically open it. That is why the next rule exists.

What our server does read. Not everything we hold is locked away from us. Our server can read: your email address; your problem reports; the tokens for messaging channels you connect for Away (a Telegram bot’s token, for example), so it can receive and send on your behalf; the name and chat of anyone who messages your bot before you’ve let them in, so you can decide; the key to your Composio project, which it stores encrypted with a key of its own and can open; your tier, your usage against its allowance, your agreements, and Stripe’s identifiers; and messages crossing a channel, in transit (see below).

The one step where you trust us. When you start Away, our server introduces your cloud computer to your Mac, and your Mac then encrypts your keys to the computer it was introduced to. That introduction is the one step where you trust us rather than the maths: an honest server introduces your computer, and ours does.

The no-look rule. Our staff open your cloud computer only to fix something you asked us about, with your yes on the ticket, and we note it on that ticket. We do not browse it, sample it, or read it to improve Moe.

Stopping it. Settings › Privacy has Keep a copy in the cloud. Turn it off and your Mac stops copying anything new; while Away is paid, that means the cloud Moe stops learning anything new, and Moe tells you so before it happens. Turning it off does not delete the copy already on your cloud computer. To remove that, cancel Away (it is deleted after the retention period below) or delete your account (it is removed straight away).

Messaging Moe through a channel

If you reach Moe through a messaging channel that runs through our server — a Telegram bot set up for Away, for example — each message crosses our server readable in transit, because our server has to see it to deliver it to your Moe. If your Moe cannot take it right away, it is stored encrypted so only your cloud computer can read it, until it can. The messaging service itself (Telegram, WhatsApp and so on) receives what you send under its own terms.

Cloud voice

Cloud voice is included on both paid plans. You can turn it on for a faster, more natural voice. With it on, your Mac streams what you say to AssemblyAI to be turned into text, and sends the words Moe is about to say to Inworld to be spoken. Your Mac talks to them directly, with short-lived passes our server issues; our server counts how much you used against your allowance and never hears the audio. Turn Cloud voice off and your voice stays on your Mac again.

Problem reports

When you tell Moe something is broken, it can send a report to the Memoe team. Nothing is sent until you turn on Let Moe send problem reports in Settings › Privacy, which is off until you do. While it is off, Moe writes no report and keeps nothing of one on your Mac — not the conversation, not its description, not even a title — and tells you where the switch is; once you have turned it on, ask again and the report is written then. After that, a report you ask for goes straight through. Turn the switch off and reports stop, and we record that you turned it off.

• What it carries: what you told Moe, a little of the conversation around it, which version of Memoe and macOS you have, your tier, and up to the last forty lines of three of Moe’s own logs. A log line that looks like a password, a key, a token or a private key is left out, and where Moe’s own words mention a key, the key is replaced. Your name is taken out of the log lines and of what Moe writes; so are email addresses and your Mac’s name. A report is never more than about 80 KB.
• Where it goes: it is stored on our server with your account, so we can reply to your email address. It becomes an issue in our private GitHub repository, which contains your words, the excerpt and the log lines, but not your email address; a notice goes to our team’s Telegram chat; and it is read by our team and by Claude Code, Anthropic’s coding assistant, which investigates it and drafts a fix. Nothing is changed for you until you say yes to the plan by email.
• Reports sent without saying who you are: with Report without saying who I am on, no account, device, email address or tier is attached to a report. It is stored on our server under no account, and it still becomes an issue in our private GitHub repository and a notice in our team’s chat, read by our team and by Claude Code. Its log lines and Moe’s description are scrubbed of your name; email addresses and your Mac’s name come out too. They may still mention things you said or did. Your Mac must be signed in to send one, and it can send five a day; to hold that limit our server counts how many reports each account sent that way each day, and the count does not say which reports they were. Because such a report is not tied to your account, deleting your account does not delete it, its GitHub issue or its notice in our team’s chat — we cannot tell which reports were yours. It also means we cannot reply, and you will not hear when it is fixed.

Paying

Payments are handled by Stripe, who process what you type into their form. Your card number never reaches us. What we keep is which tier you are on, whether it is paid, and Stripe’s identifiers for you as a customer and for the subscription, so the app knows what you are entitled to. Stripe’s privacy policy covers what they hold, and Stripe keeps its own invoices for as long as tax law requires.

This website

• Our own counts. Each page you open and each click on Download sends one short line to our server: the page, the page you came from, your browser’s own description of itself, and a random id your browser keeps in its local storage so two visits by one person count once. No IP address is stored with it, and nothing ties it to a name or an email. Clearing the site’s data in your browser forgets the id. There are no third-party analytics or advertising scripts on this site.
• Hosting. The site is hosted by Vercel, whose servers keep ordinary web-server logs for their own operation.
• The playground’s cookie. The playground sets one cookie: a random, signed id that lets us count how much of Moe’s voice and replies one visitor has used in a day. It holds nothing about you and is used for nothing else.
• The playground’s counters use a hashed address. To stop one person running up the bill, the playground also counts per internet address. It stores only a keyed hash of the address — one that cannot be turned back into the address without a secret only our server holds — never the address itself. To stop bursts, the address is also held in memory for about a minute and then forgotten.

The playground

The playground is a demonstration, not the app, and it does not run on your Mac.

• What you type or say there goes to our server and on to an AI provider using our key — Groq, or OpenRouter, which passes it to Cerebras or Groq — and the answer streams back. Their terms apply to what they receive. Do not put anything private into it.
• The microphone. If you press the talk button or hold the space bar, the page records what you say and posts it to our server, which forwards it to Groq’s Whisper to be turned into text. The words come back; the audio is not kept, by us or in the page. Each visitor gets fifteen minutes of listening a day.
• The voice. Moe’s spoken replies are made by Inworld (or, if Inworld is not set up, Deepgram): the page asks our server for each sentence, which forwards the text and streams the sound back. Only Moe’s own words go there, never yours. Each visitor gets a day’s worth; after that, and if that service is unavailable, answers are spoken by your browser’s own synthesiser, which in Chrome may synthesise on Google’s servers and on a Mac does not leave the machine.
• Moe’s own voice, in your browser. On a fast enough computer, the first time you ask for a voice the page may download Moe’s voice model (about 86 MB) — the code from jsDelivr and the model from Hugging Face — and run it in your browser. Those are ordinary file downloads; what you say is not sent with them.
• No transcripts are kept. The conversation lives in the page until you close the tab.

Who else handles your data: sub-processors

These are the companies that process personal data on our behalf, what for, and where. Services you connect yourself — your AI provider, your mail, your Google account, your messaging apps — are yours, under your agreement with them, and are not on this list.

Our server and these services are in the United States. If you live elsewhere, using the parts of Memoe that involve us means your data is processed there.

How long we keep things

• On your Mac: until you delete it. It is yours, in ordinary files.
• If you cancel Away: your cloud computer stops at the end of the period you have paid for. We keep your cloud copy for 90 days so you can pick up where you left off if you come back. On day 90 we send you one email; 30 days later the cloud copy is deleted, automatically. Your Memoe account stays, free, until you delete it.
• Any time: Delete my account in Settings › Privacy deletes your cloud computer and everything on it, your connected accounts, your problem reports (except any you sent without saying who you are — see below), your agreements and your Memoe account, and cancels any plan at once. Writing to us does the same.
• What remains after you delete your account. A few things outlast the deletion, and we would rather list them than round them away:
  • Problem reports you sent without saying who you are stay as they were sent, with their issues in our private GitHub repository and their notices in our team’s chat: nothing ties them to your account, so we cannot tell which were yours.
  • For each problem report sent with your name, the issue in our private GitHub repository keeps only its number, its dates and that it was closed. Your words and the comments are removed, though GitHub may keep its own history of edits.
  • Our team’s chat may still show each report’s number and title.
  • Stripe keeps its invoices and your customer record, as the law requires.
  • We keep a record that an account was deleted, under a code that does not name you, and expired sign-in codes for 30 days.
  • Our database provider’s backups roll off within its backup window.
  • Snapshots of your cloud computer’s disk can persist for a few days after deletion.
  • If a service holding your connected accounts refuses our request to delete them, the receipt we email you says so and asks you to check your connected services.
• Problem reports and agreements: until you delete your account. A report sent without saying who you are is not tied to any account, so it is kept after that; the count of how many you sent that way each day is deleted with your account.
• Website counts and playground counters: kept as counts. They carry no name, email or address.

Your rights

Wherever you live, you can ask us to:

• see what we hold about you, and have a copy of it (access and export);
• correct anything that is wrong;
• delete it;
• object to, or ask us to stop, any use of it.

Use the buttons in Settings › Privacy, or write to hello@moebot.app. We answer within 30 days, and we will not treat you any differently for asking. We may need to check that the request comes from the account’s owner, which usually means asking you to sign in with the same Google account.

If you are in the EU, the EEA or the UK, these are your rights under the GDPR and the UK GDPR. We rely on providing the service you asked for as the basis for most of what is on this page, on your consent for problem reports (withdraw it at any time by turning the switch off) and for Away’s copying to the cloud (turning off Keep a copy in the cloud stops new copying; cancelling or deleting your account removes the copy), and on our legitimate interest in keeping the service secure and counting visits to this website. You can also complain to your data protection authority.

If you are in California, these are your rights under the CCPA, including the right to know, to delete, to correct, and not to be discriminated against for using them. We do not sell personal information and we do not share it for cross-context behavioural advertising.

Changes and versions

This policy is versioned; the version is at the top of the page. A small edit changes the date only. A material change gets a new version, and Moe asks you to agree to it again in the app — your service is not cut off while it waits. The current version always lives at memoe.app/privacy.

What changed in 2026-09-15.1: a problem report sent without saying who you are is not tied to your account, so deleting your account does not delete it (see reports sent without saying who you are). If you agreed to the previous version, Moe asks you to agree to this one.

This page is written against what Memoe actually does, and it has not yet been reviewed by a lawyer; that review happens before paid plans are generally available, and any change it brings will come with a new version.

Questions

Write to hello@moebot.app. If this page and the app ever disagree, tell us; the app is the truth and this page will be corrected.