Meeting Use Case · Journalism & Investigation

Private source interview notes on Mac

Protect confidential sources, whistleblower interviews, and backgrounder notes in sovereign Markdown on macOS.

Verified WorkflowEvidence in codebase: main/security/source-guard.ts, main/net/guard.ts (as of 2026-10-03)air-gapped transcription, zero cloud telemetry

Problem

Journalistic risks in source attribution

  • Third-party AI meeting bots create digital attendee trails that expose confidential whistleblowers
  • Unencrypted source voice recordings uploaded to cloud transcription servers risk subpoena seizure
  • Investigative reporters spend hours manually transcribing encrypted phone calls and audio files

Response

How Oyma shields confidential backgrounders

  • Capture confidential source interviews silently via ScreenCaptureKit without an attendee bot
  • Transcribe sensitive spoken testimony 100% on-device on Apple Silicon with zero audio cloud egress
  • Connect source revelations to evidentiary documents and investigative dossiers via wikilinks

Investigative journalism and deep investigative research depend entirely on cultivating trust with confidential sources, whistleblowers, and industry insiders. During these high-stakes background interviews, reporters uncover corporate malfeasance, regulatory corruption, environmental violations, and internal government misconduct. The physical safety and professional livelihoods of sources frequently hinge on absolute anonymity.

Yet capturing and organizing investigative interviews presents severe operational hazards:

Reporters must listen with intense focus, evaluate source credibility, detect nervous speech patterns, and formulate probing follow-up inquiries. Taking hasty handwritten notes often produces incomplete quotes and missed facts. However, introducing a cloud-based AI recording bot into an encrypted call or uploading interview audio to commercial transcription platforms is journalistic malpractice: cloud vendors retain transcripts on servers vulnerable to surveillance, data breaches, and court-ordered subpoenas.

Oyma resolves this investigative dilemma on macOS. Utilizing Apple’s native ScreenCaptureKit framework, Oyma captures the audio of your background interviews silently without introducing a third-party bot into your Signal call, Zoom session, or Google Meet. Transcription executes 100% locally on Apple Silicon using on-device Whisper models, converting sensitive spoken testimony into encrypted, sovereign Markdown investigative files stored exclusively on your Mac.

The acute operational risks of investigative source reporting

Protecting source confidentiality requires an uncompromising security posture across the entire reporting workflow:

  1. Digital attendee trails and metadata leaks: Automated transcription bots leave undeniable electronic trails in meeting logs, enterprise calendar entries, and server metadata. An adversary examining call records can easily deduce who the whistleblower was talking to and when.
  2. Biometric voice identification risks: A human voice is a unique biometric identifier. Transmitting audio recordings to cloud AI vendors exposes the source’s vocal timbre and pitch to commercial databases and government intelligence monitoring.
  3. The chilling of insider candor: When a source is risking their career to expose wrongdoing, seeing an automated bot in the video call immediately destroys trust. Whistleblowers will only speak openly when they know the room is secure and air-gapped.
  4. Complex evidentiary cross-referencing: A single investigative scoop involves reconciling hundreds of off-the-record claims against FOIA disclosures, SEC filings, and corporate registries. Scattered audio files create massive investigative synthesis bottlenecks.

The investigative reporter’s dossier architecture in plain Markdown

Oyma organizes investigative findings directly into an interconnected, private Markdown vault on your local encrypted storage:

vault/
├── investigations/
│   ├── project-monolith/
│   │   ├── master-chronology.md
│   │   ├── source-notes/
│   │   │   ├── source-alpha-interview-01.md
│   │   │   └── source-beta-interview-02.md
│   │   └── evidence/
│   │       ├── DOC-01-internal-audit-memo.md
│   │       └── DOC-02-epa-water-sample.md
│   └── secure-index.md

Connecting source claims to documentary exhibits and chronological event logs via [[wikilinks]] enables reporters to assemble ironclad, fact-checked exposés.

Sample on-device source interview note

Here is an authentic Markdown artifact generated during an investigative backgrounder session in Oyma:

---
sourceCodename: Source Delta
reportingProject: "[[investigations/project-monolith]]"
interviewDate: 2026-10-09
duration: 48m
groundRules: "Deep Background (Information may be used without attribution or quotation)"
interviewer: "Elena Rostova (Senior Investigative Reporter)"
securityClassification: "CONFIDENTIAL // JOURNALISTIC WORK PRODUCT"
tags:
  - investigative-journalism
  - whistleblower
  - deep-background
---

# Investigative Backgrounder: Source Delta (Session 02)

## 1. Verified Identity & Corroborating Position
Source Delta is a senior compliance officer at Monolith Industrial Holdings. Identity was independently verified prior to session via encrypted Signal verification and review of official corporate credentials.

## 2. Core Revelations & Whistleblower Disclosures
- **Deliberate Sensor Tampering:** Source stated that between June 2025 and August 2026, effluent discharge telemetry at the Ohio refining facility was deliberately offset by -42% during EPA inspection cycles.
- **Executive Awareness:** Source confirmed that the Vice President of Manufacturing received weekly unadjusted sensor reports and directed the compliance team to archive them on an offline NAS drive.
- **Key Source Statement (Deep Background):**
  > "The executive committee knew within forty-eight hours of the initial sulfur spill that the telemetry pipeline was reporting falsified numbers to the state environmental agency."

## 3. Documentary Evidence & Corroboration Matrix
| Asserted Fact | Document Reference | Current Status | Corroboration Next Step |
| :--- | :--- | :--- | :--- |
| Telemetry offset parameter | [[evidence/DOC-01-internal-audit-memo]] | Verified | Match offset timestamp with state regulatory filings |
| VP written directive | Email chain dated 2025-07-14 | Pending | Submit targeted state public records FOIA request |
| Secondary effluent report | Offline NAS backup folder | Verified | Cross-reference with independent water testing labs |

## 4. Source Protection & Vulnerability Safeguards
- **Operational Security:** Source will only communicate via Signal vanishing messages or face-to-face meetups.
- **Employment Risk:** Source is one of only four compliance personnel with access to the raw sensor database; reporting must carefully obscure internal document distribution lists to prevent attribution.

## 5. Reporter Next Steps & Investigation Milestones
| Milestone | Action Item | Target Date | Status |
| :--- | :--- | :--- | :--- |
| FOIA Submission | Draft targeted public records request for state inspection audit logs | 2026-10-14 | Open |
| Fact-Checking | Review technical sensor calibration logs with independent environmental engineer | 2026-10-18 | Open |
| Re-Interview | Conduct follow-up secure briefing with Source Delta on corporate org chart | 2026-10-22 | Open |

The investigative reporting workflow: from source briefing to published scoop

Maintaining rigorous journalistic standards while ensuring total source protection follows a structured, air-gapped protocol:

1. Discreet local call recording without metadata trails

When conducting an off-the-record briefing over Signal Desktop, Zoom, or Google Meet, toggle Oyma‘s background audio recorder. Utilizing macOS ScreenCaptureKit at the operating system tier, recording occurs quietly. No automated third-party attendee bot appears in the call roster, ensuring whistleblowers speak with complete confidence.

2. On-device acoustic transcription on Apple Silicon

Spoken dialogue is processed immediately by local Whisper models running on Apple Silicon. Technical industry jargon, whistleblower disclosures, and corporate code names undergo speech recognition entirely on your Mac’s physical hardware without transmitting data to external servers.

3. Extracting factual chronologies and corroboration matrices

Following the interview, apply Oyma‘s investigative summary prompt using local Ollama models (such as Llama 3) or your private API key. The intelligence parser identifies:

  • Discrete factual disclosures and corporate assertions
  • Ground rules established (On the Record, Background, or Deep Background)
  • Documentary exhibits requiring independent corroboration
  • Security safeguards necessary to protect source identity

4. Compiling investigative dossiers in an encrypted vault

The synthesized Markdown report saves directly into your local investigation directory. Through bidirectional wikilinks, source assertions connect to documentary discovery exhibits and master investigative chronologies in Obsidian.

Uncompromising source protection and data sovereignty

Protecting journalistic sources is a fundamental First Amendment and press freedom imperative:

  • Immunity from third-party subpoenas: Cloud transcription databases can be subpoenaed by corporate litigants or government agencies without notifying the reporter. Keeping source audio strictly on your local encrypted macOS drive eliminates third-party exposure.
  • Air-gapped verification: With Local-only mode, reporters can transcribe field recordings, synthesize investigative dossiers, and fact-check stories with zero network access.
  • Permanent, searchable archives: Unlike proprietary cloud tools that lock your files behind recurring subscription fees, your investigative notes remain standard Markdown files that you control indefinitely.

To learn more about our local audio architecture, read about botless meeting recording, explore transcribing audio files, or review our zero-leak privacy architecture.

Questions

Review all 20 use case workflows, learn how botless audio capture protects source interviews & backgrounders, or read the zero-leak privacy architecture.

How does cloud transcription compromise confidential journalistic sources?

Cloud transcription vendors store audio recordings and transcripts on centralized servers that can be intercepted, subpoenaed, or breached. Transmitting audio containing identifiable vocal patterns of a confidential whistleblower or source creates acute legal and physical safety risks.

How does Oyma protect source anonymity and journalistic privilege?

All speech transcription runs 100% on-device using local Whisper models on Apple Silicon. Audio never transmits over the internet. When paired with Local-only mode, network connections from both the app and helper processes are completely blocked.

Can investigative reporters transcribe external audio files and field recordings?

Yes. In addition to live call recording, Oyma transcribes pre-recorded voice memos, Signal audio attachments, and field recordings directly from your local disk using on-device Whisper.

How do source interview notes integrate with complex investigative dossiers?

Because files are standard Markdown, you can organize investigative materials into an encrypted Obsidian vault. You can link source assertions directly to public records, corporate filings, and timeline notes using [[wikilinks]].

Confidential source interview notes in plain Markdown.

Free during the private beta. Apple silicon Macs, macOS 14 or later.

One email when your invite is ready. No newsletter.