Privacy

Last updated 6 October 2026

Celery turns your voice into text for dictation and keeps the meeting transcripts you ask it to remember. These two jobs handle data differently, so this page spells out both.

Dictation

In on-device mode, dictation audio and transcription stay on your Mac. In cloud mode, audio or a live transcript is sent over an encrypted connection to the providers needed to transcribe and clean it. The service does not retain the dictation audio or transcript after returning the result. Your dictation history is stored on your device.

Silence is trimmed on your device before anything is sent, so the pauses at either end of a dictation never leave your machine at all.

Meetings

New live meetings are transcribed while the call is happening. Celery stores the timestamped transcript, summary, action items, topics, and notes so you can return to the meeting, search it, ask questions about it, or share it. The new live path does not retain a meeting audio file. Older meetings created through the previous recording workflow may still have audio attached. Deleting a meeting removes its stored meeting data and any attached audio.

A meeting share link exposes only the parts shown on its viewer page. You can decide whether notes are included, whether the viewer can save a copy, and revoke the link later.

What we do keep

To run accounts and bill correctly, we store:

• your email address, and the identifier your sign-in provider gives us;
• your plan, and when your trial ends;
• one row per dictation containing how many seconds of audio it was, which model handled it, which app you were dictating into (Slack or Mail, for example), and how many words and filler words it contained — used for your usage total and, if you have asked for it, your daily digest;
• a record of your devices, so a lost Mac can be signed out without signing out the rest.

Dictation usage rows do not include what you said. Meeting records do include the meeting text described above.

Who else is involved

Cloud transcription and cleanup run through Google and OpenAI APIs under their business API terms. Payments run through Stripe, or through Apple if you subscribe in the iPhone app; either way they hold your card details and we never see them. Email is sent through our mail provider. Our servers run on Railway, audio from older meetings is kept with a storage provider, and this website is hosted on Vercel. That is the entire list.

This website

This page and the rest of the site count their own visits, in two ways. Vercel's built-in analytics records a pageview, the page you arrived from, and roughly where in the world you are. We also keep our own count, so the numbers sit alongside everything else rather than in somebody else's dashboard.

What our own count records, per visit: which page, which site you came from, your country, and whether you are on a phone or a computer. How long the page took to load, how far down it you scrolled, how long you stayed, and whether you pressed one of a short list of links — Download, Pricing, GitHub, the email links. That is everything.

There are no marketing cookies. Nothing is stored against you or your address: the country is worked out at the edge, before anything reaches us, and the address itself is never passed on or written down. Visits are tied together by a random number held for as long as the tab is open, which is thrown away when you close it — so we can tell one visit from three, and we cannot tell that you came back tomorrow, or follow you anywhere else. To count how many people visit each day, rather than how many tabs, the site turns your address and browser into a scrambled code that only works for that day; only the code reaches us, never the address, and tomorrow the same visit makes a different code. We do not record what you typed into a search engine to find us, only which one it was.

When a landing-page experiment is running, the version is placed in the page URL and attached to anonymous pageview and conversion events. Campaign source and campaign name may also be recorded when they are present in the URL. This tells us which message led to a Download click without creating a persistent advertising identity.

Deleting your account

Delete it from Settings in the iPhone app, or email hello@usecelery.io and we will delete your account and everything attached to it. Deleting an individual meeting from the app removes that meeting's stored transcript and any audio attached to an older meeting.

Questions

Ask: hello@usecelery.io. The app is open source, so you can also read exactly what it sends: github.com/lenajeremy/celery.