How Mimoto Works

Plain-English and technical explanation of how Mimoto reads message data locally across iMessage (macOS) and WhatsApp (iOS), creates analysis outputs, and keeps message content on-device.

Short answer: Mimoto reads supported local message data, analyzes it on-device, and produces reports and exports without sending message content to a remote server, across iMessage on macOS and WhatsApp on iOS.

What data does Mimoto read?

Mimoto supports two ingestion flows:

iMessage on macOS: reads local Apple Messages data from chat.db after folder access is granted. This path analyzes your full available iMessage history.
WhatsApp on iOS: uses an iOS-specific import flow based on user-selected WhatsApp chat exports. This is a selective, chat-by-chat workflow (including WhatsApp multi-export steps).

The ingestion steps differ by platform, but both feed into the same local-first analysis foundations for reports, insights, and exports.

What stays local?

Message content and analysis processing stay local on both platform paths. Mimoto’s product boundary is local-first analysis rather than cloud message ingestion.

What reports and exports are included?

Mimoto can generate readable reports, pattern summaries, and searchable exports for follow-up review.

Human-readable relationship reports
Structured exports for tabular tools
Timeline-oriented conversation views

Why is iMessage analysis harder than it looks?

iMessage history is not stored as one clean transcript file. It is split across multiple structures, with sender mapping, time normalization, and attachment context requiring careful reconstruction before meaningful analysis is possible.

Why can’t iMessage be analyzed directly on iOS?

iOS does not provide direct access to chat.db, so iMessage analysis requires the macOS path where that database can be accessed locally with user permission.

Are features consistent across platforms?

Most analysis features and scoring logic are shared across iMessage/macOS and WhatsApp/iOS because both apps use the same business-logic layer. A key difference today is that macOS can display images inside message history, while iOS currently does not.

When is Mimoto useful?

Mimoto is useful when users want private reflection, relationship review, personal documentation, or serious preparation workflows without handing private conversations to a remote service.

What is Mimoto not designed for?

Mimoto is not designed as a general chatbot, a cloud collaboration analytics suite, or a surveillance product.

Worked example

A user wants to understand changes in tone and frequency in one private conversation over six months. They load local message history, run analysis on-device, and export a searchable file for personal review.

Not a fit

Mimoto is not the right tool when a team needs shared cloud dashboards, live multi-user collaboration, or unsupported messaging platforms.