journeymail

What journeymail keeps about people

journeymail runs a workspace's journeys without keeping a profile of anyone. An event from a host app names a person by a reference, and what a journey asks about them, whether they have paid, their first name, is answered by the host app at the moment a step needs it and is not stored. Two kinds of personal data are kept, each for a stated time.

The send log

For every email sent: who it went to, its subject, when it was sent, and from which journey and step. A run's log keeps each email as it was rendered, so the workspace can see what a person was sent. These outlive the run, as the record of what was sent.

Carried details

An event a workspace declares itself, sent from its own website, form tool or AI, arrives with details: a first name, whether someone wants a call back. The details are kept with each run that event starts, as that run's facts, for as long as the run is active, and are erased the moment the run ends, however it ends. The run and its log stay, naming the steps it took, each verdict and each email as it was rendered, which is the send log's record. An arrival that starts no run keeps no details, and a refused arrival is listed with the name of the detail and the type wanted, never the value sent.

A real-person preview

A person building an email can view it as a real person the host app knows: journeymail asks the host app for that person's facts, draws the email on their screen once, and forgets them. Nothing is stored, logged, cached or sent to the AI assistant, the browser keeps nothing, and leaving the preview, editing the email or moving to another page clears it. A workspace key or a host key cannot ask for it; only a signed-in person can.

Nothing else about a person is kept: no profile, no audience, no facts stored between steps.