What's stored, what's sent, what isn't.

Your speech is transcribed on your Mac. Audio buffers and transcripts never leave the machine. The only things Parakeety, the local Mac dictation app, sends over the network are a one-time speech-model download from Hugging Face and license checks against my license server. No analytics, no telemetry, no third-party SDKs.

Parakeety is a one-person operation, just me. For the data the app does send out (essentially the license checks below), I'm the data controller. Get in touch via the contact page.

While you hold the push-to-talk key, Parakeety captures your microphone into a memory buffer. That buffer is fed to a speech model running locally on your Mac. Transcription happens entirely on the device, with no network call involved.

Once the transcript is produced, it's pasted at the cursor and copied to your clipboard. The audio buffer is discarded immediately. Parakeety does not write transcripts to disk. It does not send audio anywhere. There is no cloud transcription path, even as a fallback.

Parakeety talks to a small license backend to activate keys, revalidate them every few hours, and track trial state. The only things sent are your license key, a SHA-256 hash of your Mac's hardware ID, and your machine name (the hostname you've set in System Settings). No audio, no transcripts, no usage data.

The backend is hosted by Supabase Inc., a US company that runs on AWS. They act as a data processor for me, receiving the data above so license checks can work.

On first launch, Parakeety downloads the speech model (around 600 MB) from huggingface.co. This is a one-time fetch; after that, transcription is fully offline.

The model is cached locally so the download only happens once. Hugging Face will see the request as part of operating their CDN. I don't tell them who you are; they get whatever a normal HTTP download exposes.

The speech model, around 600 MB, cached so transcription stays offline.

A debug log with app events and timestamps, so I can help if something breaks. Transcript content is never written to it; only redacted lengths, e.g. "transcribed 47 chars". You can clear the log from inside the app at any time.

On first run, Parakeety asks for two system permissions. Microphone access, so it can capture speech while you hold the push-to-talk key. Accessibility access, so it can synthesize the Cmd+V keystroke that pastes your transcript at the cursor in whichever app you're typing into.

Both can be revoked at any time from System Settings, under Privacy and Security. Revoking microphone access stops transcription. Revoking accessibility access stops the auto-paste, but the transcript will still land on your clipboard.

If something goes wrong and you want help, there's a "Report an issue" button in the menu bar and in Settings. It generates a diagnostic report (basic system info, plus the recent app log with transcript content redacted), copies it to your clipboard, and opens the contact form in your browser. You paste it in, decide whether to send it, and submit when you're ready.

Parakeety doesn't submit anything on its own. The report only travels anywhere if you choose to paste and send.

I don't run analytics. Parakeety doesn't ship with Sentry, Firebase, PostHog, Mixpanel, Amplitude, or any of the usual suspects. There are no tracking pixels on the app, no ad SDKs, no behavioral profiling, no automatic crash reporters phoning home. I don't sell data. I don't share data with anyone outside Supabase, and Supabase only sees what's needed for license checks.

If a future version ever needs to add a network call I haven't listed here, I'll write it on this page first.

Under UK and EU data protection law you can ask for a copy of any personal data I hold about you, ask me to correct it, or ask me to delete it. In Parakeety's case there's not a lot to hold: your license record (key, machine ID hash, activation and expiry timestamps), and any correspondence you've sent me through the contact form or in reply to my support emails.

Audio and transcripts aren't covered, because they're never sent to me in the first place. To get rid of those, you delete them locally on your Mac (clear the debug log inside the app, and remove the model and prefs files if you want a clean wipe).

To exercise any of these rights, get in touch via the contact page and I'll respond within thirty days.

Parakeety isn't marketed to children, and I don't knowingly collect data from anyone, child or adult, beyond what's described above. If you believe a child has somehow ended up with a license record on the server and you'd like it removed, drop me a note via the contact page.

When this policy changes, I'll update the "last updated" date at the top of the page. Anything meaningful (a new network call, a new processor, a change to what's logged) will also be called out in the release notes for the version that introduces it.

Questions, requests, or anything that reads oddly on this page: use the contact page. It comes to me directly.