MFChatter

Privacy

Nothing survives a call but the recap email, and only in a meeting, and only because you asked for one. No account, no profile, no history.

What exists while you are here

Enough to run the call

  • A guest identity, so a reload does not lose your place
  • Who you are matched with, while you are matched
  • Chat, so it can be reported while it is happening
  • Three weak signals — an address, a cookie, a fingerprint — which is what a ban is placed against

No name, no email, no password. There is nothing to sign in to.

And in a meeting, briefly

  • The name you typed on the way in, so the transcript can say who spoke
  • An email address, only if you asked for the recap
  • The recording and transcript, until the recap is sent

Then the sweep runs and all of it goes.

How you can check

The deletion is not a promise buried in a paragraph — it is a workflow, in this site's own Automation panel, and every run of it is listed with what it did. That is the whole reason MFChatter is built on MFICore rather than as a black box.

A report is the one exception, and a narrow one: what the report is about is kept while it is looked at, because a report nobody can examine is a report nobody can act on.

We do not sell anything, because there is nothing to sell. No advertising, no trackers, no analytics that follow you anywhere else.