Skip to content
mesj
Open mesj

Privacy

Privacy cannot be a marketing line.

This page separates what the current early-access preview actually does from the architecture mesj intends to build.

Current early-access preview

  • Example conversations
  • Local demonstration rules
  • No external model receives demonstration drafts
  • No real contact delivery
  • No claim of production end-to-end encryption
  • No external MCP connection
  • No LinkedIn inbox connection

Intended production principles

  • End-to-end encryption for private messages
  • On-device assistance wherever technically possible
  • Explicit permission before optional external processing
  • Minimum necessary context
  • Clear separation between private messaging and connected services
  • No advertising based on private conversation content
  • No automatic sending
  • User-controlled deletion and retention, subject to technical realities

These are intended principles. They are not completed, shipped or independently audited technology.

What end-to-end encryption does not solve

A draft may remain private between messaging endpoints, but optional external assistance would create another data recipient. mesj intends to make that boundary visible rather than hide it inside general terms.

Private

Happens on the device

Optional cloud

Selected content shared after permission

Future architecture—not implemented

Connected service

Only authorised information shared with a named service

Future architecture—not implemented