Privacy
Last updated 30 August 2026
Your transcripts never leave your Mac. They're .md files in a folder you chose.
There's no account, no Peachy server that stores your notes, and no way for us to read them.
By default, meeting audio leaves your Mac to be turned into text. Speech-to-text runs on a cloud service (Deepgram). We put that first rather than burying it, because it's the thing you'd most want to know.
There is an opt-in on-device mode (Settings → Transcription) that keeps meeting audio on your Mac. We measured it against a cloud transcript on our own meetings: accuracy lands in the same ballpark, and on the 1:1s we tested it got who said what right, labeled Me and Them. Cloud stays the default because it's still clearer on a busy multi-person call. The app labels on-device Experimental while we keep proving it on more kinds of meetings. If your meetings are sensitive (therapy, legal, clinical), a 1:1 is where on-device is strongest, so turn it on. What we don't do is make a compliance claim. Peachy is a recorder that writes files you hold, and getting consent to record stays yours. The separate hold-to-talk dictation feature always runs on your Mac.
Exhaustive. If it isn't listed here, Peachy doesn't send it.
When a meeting finishes, its two audio channels (your mic, and the other participants) are uploaded to be transcribed. Alongside the audio, Peachy sends short vocabulary hints — the meeting title's key words and participant names (up to ~100 terms) — so the transcription service spells proper nouns correctly. These hints are used solely to produce your transcript. If you connected Google Calendar, they may include names and title words from the calendar event (see §6). Your notes, file names, and folder structure are not included. Peachy never holds a long-lived Deepgram key — it requests a token that expires in 5 minutes, issued for that upload.
Per token request, four things — no audio, no text:
| Invite code | Authorises you, applies your credit balance |
|---|---|
| Install ID | A random, anonymous per-install ID — rate limiting only |
| Meeting spend ID + credit count | A random per-meeting ID so one credit covers one meeting (up to 90 minutes) and a retry is never charged twice |
| Audio seconds | Length of your last recording — anonymous usage accounting |
The app also makes a lightweight balance check (just the invite code) so it can show your remaining meeting credits before you record, rather than failing after. That check also updates a last-seen date for your code — a date, nothing else — so we can tell active testers from lapsed ones.
Sign-in, once: during setup the app sends your identity proof (the token Google or Apple issues, or a code you type) to the broker, which verifies it and returns your invite code. The broker keeps exactly one thing from this: your email address, mapped to your code, so signing in again — or buying credits later — lands on the same balance. No name, no photo, no contact list.
Milestone stamps: the app tells the broker when you cross a handful of one-time milestones — first launch, setup started, setup completed, first recording saved, first answer — as a bare event name with your invite code (first launch uses the anonymous install ID, since no code exists yet). Each is a stage name and a server-side timestamp, written once; no transcript text, titles, names, or filenames ride along — there is nowhere in the request to put them. We use these to see where setup loses people.
Only if you turn on Settings → Help make Peachy better. The complete list:
appLaunched · recordingStarted · recordingCompleted · recordingFailed · brokerError · asrFallbackToLocal · uncleanShutdown
Event names, status codes, and coarse flags (a failure reason, whether a recording auto-started). No transcript text, titles, names, or filenames are ever attached — enforced in the single function every signal passes through.
Peachy asks justpeachy.ai/appcast.xml whether a newer version exists. An ordinary
web request; nothing identifying you is attached.
On-device speech models download the first time local transcription or dictation runs. A download; nothing of yours is uploaded.
If you connect a Google account, Peachy reads your upcoming events so it can offer to record when a meeting starts and title the transcript with the meeting's real name.
calendar.events.readonly
on your primary calendar, plus your email address (to show which account is connected). Peachy
reads upcoming events in a rolling window — titles, start/end times, attendee names, organizer,
and any video-call link. Peachy cannot create, edit, or delete anything on your
calendar — the scope makes that impossible.ThisDeviceOnly — never synced to iCloud), and never transmitted
to Peachy. Event data is held in memory only while the app is running — it is
not written to a database or file, and is gone when the app quits or refreshes.When you subscribe or buy credits, checkout is handled by Polar Software, Inc., our merchant of record. Your card details go to Polar, never to us — Peachy never sees or stores a card number. What Polar collects to take the payment is covered by Polar's own privacy policy.
From that purchase, our broker keeps only what's needed to unlock the app: your email (so a repeat purchase finds the same code), your subscription status and plan, and the Polar customer and subscription IDs, all bound to your invite code. No card data, and no meeting content, is ever part of this.
Turn on iCloud Drive for your transcripts folder and files sync through your own Apple account. That's Apple's sync, not ours — we have no access to it.
Your transcripts are ordinary files. Delete the folder and it's gone. There's no server copy to request deletion of, because there was never a server copy. Peachy's internal index is a rebuildable convenience — Settings → Reset clears the in-app lists and leaves your files untouched.
We don't sell your data, share it with advertisers, or use your content to train models. There's no mechanism for it to happen — the content isn't on our servers.
justpeachy.ai uses Vercel Web Analytics to count page views and which button was clicked. It sets no cookies and builds no cross-site profile; visitors are counted from a hashed identifier that resets daily, never a name or email. It knows nothing about your meetings. The Peachy app itself sends no meeting content to any analytics service.
Some invitation links we send are unique per recipient
(justpeachy.ai/r/…). Opening one stores the link's opaque id, the date, and a count
in our own store — that is the entire record. No IP address, browser details, or location
are stored, and no third-party tracker is involved. The id is kept in your browser's
local storage only so that clicking Download can be matched to the same invitation — it exists so
we know which invitations worked. Clear the site's data in your browser and it's gone.
Recording laws vary, and some places require everyone's consent. Peachy gives you the tools; following the law where you are is your responsibility. Tell people you're recording.