Privacy, Trust, and Architecture
Short answer: Mimoto analyzes supported message history locally across iMessage (macOS) and WhatsApp (iOS), and never sends message content to remote analysis servers.
Does Mimoto upload my messages or send message content to a server?
No. Mimoto never uploads your message content, and message content is not sent to a server.
What does “on-device” mean in practice?
It means message parsing, analysis, and report generation run on your machine, not on a remote compute service handling your conversation content.
What data is stored locally?
Mimoto stores local app data needed to run and revisit analysis results, including imported chat data, generated outputs, settings, caches, and thumbnails. This storage is local to your device and supports reruns and review without cloud message hosting.
Can I delete local data?
Yes. You can delete local data by uninstalling the app and deleting any container folders created for app data or exports.
Does Mimoto use user data to train models?
No. Mimoto does not use your data to train models.
What public trust signals should users inspect?
The most useful privacy proof is not a slogan. It is the set of boundaries a user can check:
- the App Store privacy label for the current Mimoto listing
- the product description and platform permissions shown before install
- the local Messages folder and Contacts permissions requested on macOS
- the user-selected WhatsApp export flow on iOS
- the absence of a Baxnet cloud message-analysis account or dashboard requirement
The current Mimoto App Store listings describe the workflow around no cloud accounts and no tracking, and the public App Store privacy label lists Data Not Collected. Users should still treat exported files as sensitive because local exports can be shared, backed up, or synced by the operating system after they are created.
What permissions are required?
Mimoto for iMessage (macOS) requests access to:
- your Messages folder (which includes
chat.db, the SQLite source used for import) - your Contacts
Contacts access is required because the Messages database does not store full contact names directly; it stores identifiers that Mimoto links to your contacts so reports can show readable participant names.
Mimoto for WhatsApp on iOS uses a different platform-specific ingestion flow, but the same local-processing privacy boundary. In the iOS WhatsApp path, users explicitly choose which chats to export, so no broad contact-sharing permission is required.
What remains the user’s responsibility?
Local processing reduces the exposure created by upload-based tools, but it does not make message history harmless. Users still control:
- which chats they analyze
- which report images or CSV/JSON exports they create
- where those exports are stored
- whether exports are shared with another person
- whether device-level backup or sync settings copy files elsewhere
Not a fit
Mimoto is not designed for shared team dashboards, organization-wide monitoring, or cloud collaboration workflows.
Related reading
- Founder note: Privacy boundaries beat AI hype
- All blog posts
- Official privacy policy (App Store link)
Download Mimoto
Choose the app path that matches your message source. Mimoto is built around local analysis, user-controlled exports, and clear platform boundaries.
Free to download. Optional paid upgrades may be offered in-app. Check the linked App Store listing for current regional details.