Data flow

The customer is the organisation embedding MailEditor in its application. This describes the implementation reviewed on 16 September 2026.

Data flow diagram

Dashed arrows depend on the integration, enabled features or referenced content.

Loading diagram…

MailEditor stores the supplied user identifier, origin, session timestamps, and hashes of the token, requesting IP address and user agent. The iframe URL carries identity parameters. Session tokens expire after 60 minutes; this does not delete stored data.
Template names and HTML autosave to MailEditor, which sanitizes the HTML. Its database holds drafts, metadata and countdown settings; background workers generate previews and write files. Files use MailEditor-managed storage or the customer's S3-compatible bucket. MailEditor still processes drafts in either case. Generated video thumbnails use MailEditor's R2 storage. Uploaded images have public URLs.
Editor template and image APIs filter by plugin and session identity. The authenticated customer backend can retrieve identifiers and templates across its plugin's users.

When	Recipient and data
AI text generation	Configured OpenAI, Anthropic, Google Gemini or OpenRouter receives submitted text and instructions. OpenRouter forwards requests to a model provider.
Stock images or video thumbnails	Unsplash, Pexels or Pixabay receives searches and image/download requests. YouTube or Vimeo receives video identifiers and thumbnail requests.
Test email	The mail provider receives addresses, subjects and messages. MailEditor stores pending HTML and recipient approval records, and sends tests after approval where required.
External assets load	Image/font hosts, including configured Google Fonts, receive asset URLs and network metadata from browsers, preview workers or email clients.