Data flow

Privacy and data flow

NeoMail is a native Mac application. Network traffic goes to the services you connected—Google, Microsoft, your IMAP host—and to the LLM HTTP endpoint you configure. There is no parallel “NeoMail cloud inbox” reading along beside you.

On your Mac

  • Rules & state. Automation definitions, handled-message IDs, and app preferences stay in local storage you control.
  • Credentials. OAuth tokens, passwords, and API keys are stored in Keychain, not in NeoMail plaintext files.
  • Bulk heuristics. Category and list detection for obvious traffic runs locally before any optional LLM call.

Over the network

  • Mail providers. Standard provider APIs or IMAP/SMTP—same surface area as other desktop mail clients.
  • Your LLM vendor. Prompts include only what your rule configuration allows (headers, excerpt length, optional thread slice). Provider logging and retention follow their policy and your account settings.
  • Software updates. Update checks may contact distribution infrastructure (e.g. Apple, or a direct download host). They do not include message bodies.

If you need a formal DPA or company-specific terms, contact us through the same channel you use for billing support—we’ll keep legal copy boring and precise.