What the two things you can share actually are, and what happens to them.

1 Two shapes, and the toggle picks which.

ONE INCIDENT the minutes around a thing that went wrong: your journal and d47's log, side by side A HISTORY many journals at once, as far back as Include says — for finding what nobody reported Include journal history is the switch between them. Everything else on the window follows from it.

An incident is for a bug you can point at. A history is for the ones nobody has noticed yet — a callout that fires in a situation no one thought to test.

2 You read it before it goes, and it is not the raw file.

READ from your disk SCRUBBED on this machine SHOWN to you, in full YOU press, or don't The scrub works from a list of fields it keeps, not a list of things to remove. Other fields are removed by default — which is the only way it stays right as Elite adds events.

3 A history is offered as a report about itself.

HUNDREDS OF MB nobody could read this A REPORT YOU CAN ACTUALLY READ every kind of event included, and one real scrubbed line of each So consent is possible. Reviewing the thing itself would mean agreeing to something nobody read. The report is what you see; the scrubbed history is what would be sent.

The details

This page explains what the window is offering. What happens to a donation afterwards — who holds it, on what legal basis, for how long, and how to have it erased — is the donation privacy notice, and it is a different question deliberately kept on a different page.

Nothing here happens unless you press. There is no setting that turns any of it on, and there is no standing consent to withdraw, because none is ever given.

Forget sits beside Send, on both pages. One press asks for everything this installation ever sent to be deleted, and the window says what came back. The same press lives on the Privacy and egress page, and the two are the one call — an excerpt is deleted after 30 days anyway, and a donated journal history is kept until you ask for it back.

Why real journals

A bug in Directive 47 is nearly always a bug about a situation: a callout that fires when it should not, a ship state nobody anticipated, an event Frontier added that the app had never seen. Reproducing one from a description means guessing at the situation. Reproducing it from the journal that produced it means replaying it.

That is what the replay harness is for. A donated incident becomes a case it can run — the same events in the same order — so a fix can be proved against what actually happened rather than against somebody’s account of it.

The two shapes

An incident excerpt is the minutes around one thing that went wrong: your Elite journal and Directive 47’s own log for that window, side by side. That pairing is the point — the journal says what the game did and the log says what Directive 47 made of it, and a bug is nearly always in the gap between them.

A journal history is many journals at once, as far back as Include says. It is for the bugs nobody has reported: with enough real journals, a callout that misfires in some rare situation shows up as a pattern rather than as one Commander’s bad evening.

The Include journal history toggle is the switch between them, and everything else on the window follows from it — what is previewed, what the buttons say, and how big the result is.

The toggle is there whichever reading you pressed the button on, and it starts off. It used to depend on where you were: pressed on the Journal page the window opened on the history, and pressed on Log File the toggle was missing altogether. One page now, opening on the excerpt, with the history one press away.

What the scrub does

Your Commander name and the IDs that identify you are replaced with stable stand-ins, so a sequence of events still reads as one Commander’s without naming you. Other people’s words are dropped entirely: another Commander’s chat is theirs, and you cannot consent on their behalf.

It works from a list of fields it keeps, rather than a list of fields to remove. That is the part worth understanding, because it is what makes it hold: a field nobody has thought about is dropped by default. Frontier adds events, and a scrub written the other way round would leak every one of them until somebody noticed.

The scrub runs on your machine, before anything is displayed. What you review is the scrubbed result, not the original.

Why a history is shown as a report

A history runs to hundreds of megabytes. Nobody reads that, so reviewing it directly would mean agreeing to something you had not read — which is not consent.

So Directive 47 builds a report about the history instead: it names every kind of event included, and shows one real scrubbed line of each. You are reading a faithful sample of the actual content rather than a promise about it, at a size a person can get through.

An incident excerpt is small enough to show in full, so it is shown in full.

Reading your journals

Read my journals walks the journal folder and scrubs as it goes. It writes nothing and sends nothing; it can be stopped part way, and stopping leaves nothing behind. On a long history this takes a while, and the window says how far it has got.

If there is no send address

A build with no destination configured can still do all of this — read, scrub and review — and then save the result to a file instead of sending it. Where that file goes afterwards is entirely yours. Anything posted publicly can be archived beyond anyone’s reach, which is worth knowing before you paste one into a forum.