More
Privacy and security
What goes where, who can read it, and how long it stays. The limits are in the Privacy Policy; this page is the detail, feature by feature.
On your device
- Everything lives on your device first: recordings, transcripts, summaries, tasks, folders, your Ask chats and drafts, and settings. Your profile photo stays on that device only. A watch recording goes from the watch to your phone directly.
- Without a sign-in nothing leaves the device. The AI needs a sign-in, also with a Mullo Pro key or your own AI key.
- Free up space: Settings, Storage removes audio from that device and keeps the text; the copy in your account keeps its audio.
In your account
- Sign-in: email and a one-time code, Sign in with Apple, or Google. No password. With Google or Apple, they tell our sign-in provider your email, and the name and picture on that account if it has them.
- Your copy is stored with Supabase in Canada (Montreal): recordings and audio, transcripts, summaries, tasks (with their drafts), folders, and Activity. The database lets an account read only its own rows; audio sits in a private storage space, a folder per account. More on your account
- Activity keeps every change, so a mistake can always be undone. Deleting your account erases it for good (backup copies roll over within 30 days).
The AI
- Transcribing. The audio goes through Mullo's server (Cloudflare Workers) to an AI transcription service working for Mullo, on paid terms that don't let it train on your audio (the kinds we use). Which one depends on the recording, for example its language and length. Which models: Limits and AI models.
- Silence. Your device checks for speech first: a recording with none isn't sent at all (in a browser, only recordings up to 3 minutes are checked). Otherwise the whole recording is sent, and lines written inside long silent stretches are dropped.
- Summaries and tasks. The transcript text goes the same way to our AI service.
- Ask. Your device picks the notes that fit the question (or the one recording you chose with "Ask about this") and sends them with the last few messages of the chat. Mullo's server keeps nothing of Ask; the chat and its drafts are kept only on your device.
- Drafts on your tasks. When a note gives you an email or message to send, Mullo drafts it once the summary is ready, from that one note. The draft is kept with the task. Mullo never sends anything. Turn it off in Settings, Tasks, "Draft emails and messages for me".
- An OpenAI model. In Settings, Summaries, you can choose a model made by OpenAI for summaries, tasks, Ask and drafts. Only after Mullo tells you and you agree, that text then goes through Mullo's server to OpenAI's paid API, with OpenAI asked not to store it; OpenAI doesn't train on API data. Your audio still goes only to the transcription services. If OpenAI can't answer, that summary is made the usual way. Choose a Gemini model again to stop.
- Your own AI key (Gemini or OpenAI). Your audio or notes go to that company under its terms, and it bills you. Mullo's server locks the key (AES-256-GCM) so only Mullo's server can use it, and only for the Mullo account that added it; your device keeps the locked copy and Mullo doesn't store it. When you pick a summary model, Mullo sends that company a short made-up test note with your key (none of your notes). More
- Speakers are marked per recording only. No voiceprints.
How long Mullo's server keeps it
- The audio until its transcript is written, then it's deleted.
- The finished transcript and summary wait so your devices can still collect them (a phone that lost signal, or your computer while Mullo is closed on your phone), then they're deleted: 24 hours, or less in Settings, Privacy & data, Mullo's server (6 hours, 1 hour, or until one of your devices has it: deleted as soon as one of your devices saves it, and after an hour at most if none can say so). The recording itself is never kept there for this.
- The AI services working for Mullo may keep a copy for a limited time, only to detect abuse and meet legal duties, under their terms; they never train their models on it.
- Keep recordings, in Settings, Privacy & data: delete a recording's audio once its notes are made, or 7 or 30 days after you recorded it. It goes from that device and from your account, with no copy kept for restoring; the transcript, summary and tasks stay. Your other devices keep audio they already downloaded until you make the same choice there.
What Mullo's server keeps for your account
- Your plan and the AI you used each month. Mullo's server keeps these in Cloudflare's eastern North America region.
- Website subscriptions: the Stripe ids and the email you paid with. iPhone: Apple's subscription id, status and renewal date. Android: a fingerprint of Google Play's purchase token, the plan and its dates.
- Fingerprints only of your email (one trial per mailbox), Mullo Pro keys and API keys; Mullo can't show a key again.
- In the iPhone and Android apps, if you allow notifications: your phone's notification address, so Mullo can say "Your note is ready" when the server finished a note with Mullo closed. Apple or Google delivers it; it carries no words from the note unless you turn on "Show the note's title" (Settings, Notifications). The address goes when you sign out, turn it off or delete your account.
- Setup steps your account has done (set up the watch, recorded a first note, opened the plans screen, reached a plan's limit) and which days it opened Mullo.
- Which of a few setup choices are on: your own AI key, your own server, Transcribe on this phone, Transcript only, and when one changed. On or off only: never the key, the server's address or a note. Counts with no account in them (how many accounts changed a choice or deleted their account in a month) stay after you leave.
- Problem reports: what you wrote, your email, a screenshot if you added one, and Mullo's version, your device and browser, the screen, your plan and language, recent error messages, and a note's id if it's about one. Never a note's words or audio.
Connected apps and Google
- Connected apps and API keys only read. The database refuses them any change and any audio. An API key's grant is locked (AES-256-GCM) on Mullo's server. App connections
- Google Calendar and Google Tasks get a task's words, context, the recording's title and date. Mullo keeps the locked grant and the ids that link tasks, never their words.
Security
- HTTPS only, everywhere, with browsers told never to use an unencrypted connection.
- Stored data is encrypted at rest by Supabase and Cloudflare.
- Secrets (Google grants, your own AI key, API key grants) are encrypted a second time by Mullo's server with a key only it holds.
No system is completely secure; these are reasonable safeguards for the kind of data Mullo holds, and we keep improving them.
The Privacy Policy (the limits all of this stays within), the Terms of Service, and the Service providers.