Reviewed 2026-08-20
Keep the recording local. Describe the network honestly.
This policy describes the reviewed v1.0.2 application source and this static website. It distinguishes audio processing from optional or incidental network traffic.
Application audio processing
Core format detection, conversion, RNNoise cleanup, de-clip, auto-level, playback, and library work happen on the device. No recording-upload path or telemetry SDK was found in the reviewed v1.0.2 manifests and source. Temporary and output files remain subject to your own device, backup, and retention controls.
Transcript text and persistence
Imported, pasted, or typed transcript text stays in the desktop app. The released editor associates saved transcript segments with the selected audio track on that device and does not upload them for transcription. Local app storage is not a substitute for a transcript file or backup: export SRT or TXT before moving the recording, clearing app data, or relying on the work elsewhere. If storage is unavailable, changes last only for the open session and the app instructs the user to export them.
Application network behavior
Core conversion does not require the network. Selecting Install for an optional model downloads a bounded asset from GitHub and verifies its SHA-256 hash; the recording is not part of that request. The source supports update checks only in a release build configured with a verified updater key and endpoint. v1.0.2 was published without that configuration or updater assets, so its updater is dormant. Network destinations ordinarily receive request metadata such as IP address and headers; the website does not claim that only a version string is visible to them.
Browser file identifier
The identifier reads at most the first 8 KB of the selected file in the browser. It does not upload, hash, log, or send the filename, file size, prefix bytes, audio metadata, duration, or playback state. Optional playback uses a local object URL that is revoked on replacement, reset, error, or page exit.
This website
The repository builds a static Astro site for Cloudflare Workers Static Assets. The pages contain no analytics, advertising, session replay, heat maps, or fingerprinting code. Fonts are self-hosted. Release facts and direct asset URLs are committed, so the site does not call the GitHub Releases API on page load. Normal website requests still reach the hosting infrastructure and are subject to its operational logs and policies.
External-request inventory
Scroll horizontally to review every column.
| Request | Trigger | Purpose | Data sent | Fallback behavior |
|---|---|---|---|---|
| GitHub installer asset | You activate a download link. | Download a reviewed macOS or Windows installer. | Standard HTTPS request metadata, including IP address and headers. Site code does not add the selected filename, identifier result, or recording bytes. | Use the release-status page to confirm expected filenames and checksums, then retry the tagged release when GitHub is available. |
| GitHub source or issue page | You open an external source or issue link. | Inspect the source or report a problem. | Standard HTTPS request metadata plus anything you choose to submit to GitHub. The site does not automatically send selected-file data. | Use the on-site format and support guides. Do not submit a confidential recording casually. |
| App model asset | You select Install for an optional model. | Download the requested model asset for an optional feature. | Standard HTTPS request metadata and the asset request. Audio, filenames, file paths, and case data are not part of the request. | Continue without that optional model; features that require it remain unavailable until installation succeeds. |
| App update endpoint | No trigger in v1.0.2; a future correctly configured release could check its signed updater endpoint. | Fetch update metadata when a verified updater is enabled. | If enabled, standard HTTPS request metadata and the updater request. Audio is not part of the request. | Check the release-status page or tagged release manually. v1.0.2 does not depend on an updater endpoint. |
Reporting a problem
Do not attach a confidential recording casually. Prefer a synthetic or non-confidential reproduction, remove identifying content and metadata, and assume GitHub issues are public. See the safe sample checklist before contacting the public issue tracker (opens in a new tab).