🔒 Privacy commitment
Your conversations
never leave your Mac.
Most meeting apps treat your audio as their inventory. We built Pribble the opposite way: your machine, your files, your call.
★ The data flow
Three steps. One device.
Summaries run on a local model by default — zero network traffic. If you bring your own API key for a cloud model, Pribble calls it directly with just the transcript text. No third-party SaaS, no data stored on anyone's servers.
✦ Six principles
The rules we won't break.
On-device by default
WhisperKit runs on your Mac’s Neural Engine. The transcript is generated entirely locally — your audio never gets uploaded for transcription. Ever.
Local LLM by default
Summaries run on-device with a local model — no network call at all. If you bring your own API key for a cloud model, Pribble calls it directly with just the text. No third-party SaaS in between.
Local file storage
Recordings, transcripts, summaries — all in ~/Documents/Pribble/Recordings/. You can browse them in Finder. You can delete them. You own them.
No account required
Pribble doesn’t need an email, a login, or a profile. There’s nothing to sign up for. Download and use.
Your iCloud, your encryption
Optional iCloud Drive backup uses your iCloud account. Pribble never sees your data — Apple’s end-to-end encryption handles it.
No telemetry without consent
We don’t track your usage. No analytics SDKs, no error-reporting that includes content. If we ever add crash reporting, it’ll be opt-in and stripped of all transcripts.
· How we stack up ·
The competition. Side by side.
The pledge
If Pribble ever changes how it handles your data, your existing version keeps working the way it always has.
We may someday ship a v2.0 with new defaults. The v1.0 you have today will keep doing what it does today, with the privacy posture it shipped with. Forever.
— The Pribble team, Santa Cruz, CA
The simplest privacy policy: your stuff, your machine.
macOS 14+ · Apple Silicon