Privacy policy
Last updated October 3, 2026
Earpiece is an open-source command center for your agents. It is built to keep your work on your machine. This page lists everything the website and the Mac app collect. The app’s code is public on GitHub, so you can check every claim here.
What never leaves your machine
Your code, prompts, agent messages, summaries, project names, file paths and API keys are never sent to us, unless you use Pro’s hosted voice (below). Earpiece’s settings, session list and log stay in ~/.earpiece on your Mac.
The website
earpiece.dev uses Google Analytics to count visits and clicks on its buttons (for example “Download for Mac”). Google Analytics sets cookies and receives your IP address, browser and approximate location. The site is hosted on Vercel, which keeps standard request logs.
Usage stats in the Mac app
A few times a day the app sends: a random install id made on first launch, the app version, the macOS version, the CPU architecture, your locale, which agents are connected, which features are switched on, which voice engine is used, whether a Smallest or OpenAI key is set (yes or no, never the key), and how many lines were spoken and skipped that day. We use this to know how many people use Earpiece and which features matter.
While you’re signed out, turn it off any time under General → Share usage stats. While you’re signed in, usage stats are part of your account; sign out to stop them. The earpiece command-line tool sends nothing.
Signing in with Google (optional)
Every feature works without an account. If you choose to sign in, we receive your Google account’s email address, name and profile picture URL. While you stay signed in, usage stats are always on and linked to your account. We use your email to tell you about Earpiece, and you can ask us to stop. We don’t sell or share it. Sign out under General → Account.
Voice and summary providers
If you add your own Smallest.ai or OpenAI key, the app sends the text it needs straight to that provider under your own account. That traffic never passes through us, and the provider’s own privacy policy applies.
Earpiece Pro hosted voice
With a Pro plan, Earpiece uses its own voice and summary keys so you don’t need any. To do that, the end of an agent’s final reply (up to 6,000 characters, with keys and tokens removed) passes through our server to an AI provider to write a one-line summary, and that line passes through our server to a voice provider to turn it into speech. We don’t store this text. We keep only how many lines and summaries you used each month, to apply the monthly limit.
Needs-you detection (Jev)
With a Pro plan or your own TypeSafe key, the end of an agent’s final reply (up to 4,000 characters, with keys and tokens removed) goes to Jev, TypeSafe’s decision model, which only answers whether the turn asks you something, finished, or is a progress note. Under your own key it goes straight to TypeSafe. With Pro it passes through our server, which asks Jev on our key. We don’t store this text. Setting the summary provider to none turns this off.
Voice replies
If you reply to an agent by voice from the notch, the microphone records only while the mic button is red. The short clip passes through our server to a speech-to-text provider (Pro), or goes straight to OpenAI under your own key (Free), and comes back as text for you to read and send. We don’t store the recording.
Who processes the data
Supabase stores usage stats and accounts, and runs the Pro hosted voice. OpenAI and Smallest.ai process Pro hosted voice requests. Google provides sign-in and Analytics. Vercel hosts the website. Usage stats don’t include an IP address column, but Supabase keeps short-lived request logs that do.
Deleting your data
Message us and we’ll delete your account and the stats linked to it. Contact the founder on X.