Nothing leaves your machine.
MeetPing is the listener you can install on your work laptop without filing a security ticket. This page is the long version: what's in RAM, what (briefly) touches disk, what entitlements the app requests, and why.
Nothing leaves your machine.
MeetPing is the listener you can install on your work laptop without filing a security ticket. The model lives in your app bundle. Audio buffers stay in RAM until they age out of the 30-second window. Transcripts are never written to disk.
v0.1 has zero outbound connections. Pull the ethernet, kill your Wi-Fi, run MeetPing in airplane mode — nothing changes. Verify it yourself with Activity Monitor or Little Snitch. Remote alerts in v0.2 will be opt-in and visibly outlined in Settings.
Process boundaries
MeetPing is a single user-space process. It does not spawn helper processes, daemons, or LaunchAgents. Audio is read by Core Audio inside the same process, frames are passed to the FluidAudio Swift package via in-memory buffers, and Parakeet inference runs against the Apple Neural Engine through CoreML — all in-process. The keyword scan, the rolling buffer, and the popover view are also in-process. There is no IPC.
What lives in RAM vs. on disk
RAM only: raw audio frames, the rolling 30-second PCM buffer used for ping replay, streaming partial transcripts, and the rolling text buffer that backs the popover. All of it is allocated in the MeetPing process and freed when the listener disarms or you quit the app. None of it is mmap-backed by a file.
On disk: only your settings (watchwords, profile, alert channels, license token) inside ~/Library/Application Support/MeetPing/. The Parakeet model bundle ships inside the .app and is read-only after install. No log file contains transcript text.
Entitlements MeetPing uses
- com.apple.security.device.audio-input
Microphone access. Required to read mic audio for streaming ASR. Audio is consumed in 16-bit PCM frames and never persisted.
- com.apple.security.cs.allow-dyld-environment-variables
Allows the FluidAudio runtime to load the Parakeet TDT v3 BNNS dynamic library at startup. Used for model load only.
- Screen Recording (TCC)
Optional. Granted by the user when they enable system-audio capture so MeetPing can also listen to the meeting app's output (remote participants). MeetPing does not capture pixels.
- Notifications (UNUserNotificationCenter)
Used to fire local notifications on a keyword match. No push tokens are registered with Apple's push servers.
Hardened Runtime is on. App Sandbox is off in v0.1 because Core Audio Taps and the BNNS dynamic library load are incompatible with sandbox restrictions today; we are tracking the upstream changes that would let us enable it.
Verify it yourself.
On-device privacy
The data exfil ledger, RAM vs disk breakdown, and the audit you can run yourself.
read ›Why on-device ASR matters
The case for running Parakeet locally instead of round-tripping to a cloud API.
read ›Auto-arm
Listener idles outside meetings. No always-on recording, no constant transcription.
read ›