Siphon

Privacy policy

What Siphon keeps on your devices, what the hosted relay and account service see, the daily usage counts and how to turn them off, crash reports, and who else is involved.

Effective 14 November 2026.

Siphon is made by Cory Logan (“we”, “us”). This policy covers the Siphon apps for Mac, Apple Watch and iPhone, the hosted relay and account service, and this website, siphon.watch. Questions or requests: [email protected].

The short version: what you say stays on your own devices and goes to the agent you choose. Our servers carry it only end-to-end encrypted, so they can’t read it. They know who you are (your email), which Macs, watches and iPhones you have, and counts of how you use Siphon. We don’t sell data, show ads or use trackers.

On your Mac, watch and iPhone

  • Speech-to-text runs on your Mac, on its Neural Engine. Thread titles and transcript cleanup use Apple’s on-device models. Your audio and words aren’t sent to us or to a speech service.
  • On the Mac, Siphon keeps each recording’s audio for 30 days, then deletes it (a message still waiting to reach your agent keeps its audio until it has gone). Transcripts, threads and your agent’s replies stay until you delete them. The Mac’s logs, in ~/Library/Logs/Siphon, include thread titles and the start of each reply.
  • A recording the Mac hears nothing in is kept too, in case something was said quietly or misheard. It isn’t in your threads and never goes to your agent: Settings → Recordings on the Mac lists these, and you can play each one, have it transcribed again, or delete it there. It’s deleted with its audio after the same 30 days. Only a recording with no sound in it at all (a button pressed by accident somewhere quiet) is deleted straight away.
  • A recording the Mac couldn’t transcribe (speech-to-text failed, or the Mac stopped part way) keeps its audio past the 30 days: the audio is all there is of it. Settings → Recordings lists these too. The audio stays until the recording has a transcript (Transcribe again there, or the watch or iPhone sending it again), after which the 30 days apply as for any other, or until you delete it.
  • On the watch and iPhone, a recording is kept until your Mac confirms it has it (or that there was no sound in it at all), then deleted. If you unpair with a recording still waiting, it stays on the device and goes to the computer you pair with next. The ones still on the device are listed under Threads, where you can delete any of them yourself. The app keeps a copy of your recent threads so it can show them offline. Waiting recordings and that copy are left out of iCloud and computer backups, and can only be read once the device has been unlocked after a restart. Pairing keys are kept in the Keychain.
  • Until it’s paired, the app sends nothing: no recordings, no requests. You can still record: it’s saved on the device, and goes to the computer you pair it with, once you do. Once paired, it talks only to your Mac, end-to-end encrypted, directly at home or through an https relay.
  • Pairing at home needs no relay. The device and your Mac exchange keys directly on your network, and you compare a code on both screens: nothing about it leaves your network, and no relay or account is involved. A device paired this way talks to your Mac at home only. It has nothing to do with the relay until your Mac is connected to one: then the Mac registers the device on your relay account (its name) and hands it what it needs at home, so it works away from home and can be notified.
  • The first time it runs, the Mac downloads the speech model (about 600 MB) from Hugging Face. That download sends nothing about you beyond what any download does (your IP address, for example).
  • The Mac app looks for a new version at download.siphon.watch when it starts and about once a day, and downloads it from there (Settings → About turns that off). Those requests say which Siphon version is asking, and nothing else about you beyond what any download does (your IP address, for example).
  • None of the apps include analytics, advertising or crash-reporting SDKs. Crash reports are Siphon’s own, kept on your devices and sent only as described below.

Your agent

When a recording finishes, the Mac sends its transcript to the agent you’ve set up (for example Hermes), on your Mac or wherever you run it. What the agent does with it, including which AI provider it uses, is up to your agent and its settings. That provider’s own privacy policy applies to what the agent sends it.

Share location (off unless you turn it on)

Each app has its own Share Location switch: in Settings on the watch and iPhone, and in Settings → Connectors on the Mac. It’s off until you turn it on, and the app only asks for location access then. While it’s on, the device works out the town it’s in (for example “Anacortes, WA”) and sends that name, and when it was there, with each message, so your agent can answer questions like “find coffee nearby”. Your agent sees one line such as [Location: Anacortes, WA · 3 min ago]. Siphon never sends your coordinates to your Mac, the relay or your agent: only the town name goes, encrypted like the rest of the message. Turning a position into a town name is done by Apple’s location services (as in Maps), under Apple’s privacy policy. The Mac keeps the town with the message only to hand it to your agent.

The relay

Away from home, your watch or iPhone reaches your Mac through Siphon’s relay. Every request and reply is end-to-end encrypted between your device and your Mac, with keys made when you pair them (you compare a code on both screens). The relay can’t read what it carries.

What the relay does see:

  • Which Mac or device a request is for, its size, its timing, and whether it worked.
  • Your IP address. It’s used to limit abuse, and it’s written to the relay’s log when you pair a device. It isn’t stored anywhere else.
  • Your device’s name (for example “Apple Watch”), sent when you pair it through the relay, or when your Mac registers a device you paired at home, so it can be listed in your account.
  • What app, app build and OS version a device or Mac is (its User-Agent).
  • Your device’s push notification token, so the relay can ask Apple to wake it when a reply arrives. The notification’s visible text is generic (“Hermes replied”). The reply itself travels encrypted inside it and is opened on your device. A device paired at home, on a Mac with no relay, registers no token anywhere and gets no notifications.

The relay reports counts to the account service every minute, per Mac and per device per day: requests carried, bytes up and down, connections, failures by type, when each was last seen, and its app build and OS version.

Daily usage counts from your Mac

The relay can’t see what happens inside its encrypted requests, or anything on your home network. So once a day, a Mac that’s signed in to a relay account sends the account service a summary of the day before. It contains only numbers and versions:

  • how many recordings it took, directly or through the relay, and their total length;
  • how many typed messages;
  • how many recordings and messages went to your agent, by type of agent (for example “hermes”), and how many failed;
  • how many transcriptions failed;
  • the Siphon version and build, OS version and hardware model of your Mac and of each watch and iPhone that sent it something (for example “Watch7,5, watchOS 26.0”).

It never contains what you said, your audio, transcripts, replies or thread titles.

This is on by default. To turn it off, open Siphon on your Mac, go to Settings → Secure Relay, and switch off Share usage counts. A Mac without a relay account never sends it.

We use these counts, and the relay’s, to see how Siphon is used, to find problems, and to decide what to fix next.

Crash reports and diagnostics (off unless you turn them on)

When Siphon crashes, each app keeps a short report of it on the device: the Mac in ~/Library/Logs/Siphon/Crashes, the iPhone and watch in their own storage (left out of backups). The iPhone also keeps the crash and hang reports iOS gives apps (MetricKit), and the iPhone and watch keep a small log of the app’s own events: launches, the app coming on and off screen, “Talk to Siphon”, and recordings starting, stopping and being sent, with their times. Nothing leaves your device unless you send it.

What a report contains: the app’s version and build, the OS version and hardware model, and for each crash when it happened, which part of Siphon it was in, the signal or exception, its place in Siphon’s code (file and line, and the names of the functions it was in, or for the iPhone and watch the program and offset), and the crash message reduced to code and a fixed list of technical words. On the iPhone and watch, the event log above. And a few settings, each a fixed word: whether you use the relay or pair at home, whether automatic updates, usage counts, location sharing and automatic crash reports are on.

What a report never contains: your audio, transcripts, replies, thread titles, typed messages, logs, the names of your devices or your computer, your user name, files or folder names, tokens or keys, email addresses, IP addresses or web addresses. The apps build the report from a fixed list of fields and take out anything that looks like one of these, and our server refuses a report in which anything still does.

Seeing and sending one: Settings → About → Diagnostics on the Mac, or Settings → Diagnostics → Send Diagnostics → Show the Report on the iPhone and watch, shows exactly what would be sent. Nothing is sent until you choose Send to Siphon, which sends it to the account service, with the device’s relay credentials, so it’s stored with your account and Mac or device. It needs a Siphon relay account; without one (at home only, or with a relay of your own), save or share it as a file instead and email it to us if you like.

Automatic crash reports are off by default. Each app asks once (on the Mac in the setup checklist, on the iPhone and watch after pairing), and has a Send crash reports automatically switch in the same place. While it’s on, new crash reports (with the event log on the iPhone and watch) are sent by themselves, at most once an hour.

We keep reports for 90 days, then delete them, and use them only to find and fix what went wrong. A report is limited in size, and each Mac or device can send only a few a day.

Your account

When you sign in to siphon.watch, we keep:

  • your email address, and your name if you give it;
  • when you created the account and last signed in;
  • your Macs and devices: the label you give a Mac, each device’s name, when they were added and last seen, and the versions above;
  • your plan, and any free access we’ve given;
  • which relay your account uses. We choose the one nearest you, once, from the approximate location Cloudflare gives us for your request. We store only the relay we chose, not your location.

Admin accounts also have a second sign-in factor, and admin actions are recorded in an audit log.

Signing in goes through WorkOS. WorkOS emails you a sign-in code, or signs you in with Google where that’s offered and you choose it. We pass WorkOS your IP address and browser User-Agent when you sign in, for its security checks.

Signing in from the Mac’s command line (account sign-up in the Quickstart, which an agent can run for you) is the one sign-in whose code we email ourselves, through Cloudflare. That email has your address, the name of the Mac that asked and the code. We keep the request, with your address and the Mac’s name, for the 10 minutes the code works, then delete it. WorkOS gets only your email address, to find your sign-in or make one.

Paying goes through Stripe. Stripe gets your email address and handles your card details. We never see or store them. We keep your Stripe customer id and your subscription’s status and dates.

The waitlist

If you join the waitlist, we keep your email address and when you joined. We use it to tell you when there’s a build you can try, and for nothing else.

Cookies and this website

  • siphon.watch has no analytics, ads or third-party scripts, and its fonts are served from siphon.watch itself.
  • It sets cookies only when you sign in: siphon_session keeps you signed in for 30 days after you last use it, and 90 days at most, and siphon_oauth_state lasts 10 minutes while you sign in with Google. Both are needed for signing in, and neither tracks you. Alongside the session, siphon_signed_in holds only 1, so the site’s pages can show Account instead of Sign in; it goes when you sign out.
  • Cloudflare sits in front of the site and the account service, so it handles every request, including your IP address.

Who else is involved

Service What for What it gets
WorkOS Signing in Email, sign-in IP address and browser User-Agent
Stripe Payments Email, payment details
Cloudflare DNS, website and account service traffic, backups, our email Requests to siphon.watch, backups of the account database, mail you send us, and the sign-in code we email you when you sign in from the Mac’s command line (your address, the Mac’s name, the code)
DigitalOcean The servers Everything the account service and relays store (in Toronto, Canada)
Apple Push notifications Push tokens, and encrypted replies it can’t read

We don’t share your data with anyone else, except where the law requires it.

How long we keep it

  • Your account, devices and usage counts are kept while you have an account.
  • Crash reports and diagnostics you send are kept for 90 days, and deleted with your account.
  • Sign-in sessions end after 30 days without use, and 90 days after you sign in whatever happens. “Sign out everywhere” on your account’s Account page (siphon.watch/account/settings) ends them all at once.
  • Stripe keeps invoices and payment records for as long as tax law requires, even after you leave.
  • Server logs record events such as a Mac connecting or a device pairing, with account and device ids, and are deleted as the servers rotate them.

Your choices and rights

  • Turn off the daily usage counts in Settings, as above.
  • Crash reports are sent only when you send one, or turn on automatic crash reports; turn that off again in the same place.
  • Remove a Mac from your account’s Devices page (siphon.watch/account/devices) at any time.
  • Delete your account yourself: on your account’s Account page (siphon.watch/account/settings), under Delete account, type your email to confirm. Or write to [email protected] to have it deleted, or to see the data we hold about you, to correct it, or to get a copy.
  • Deleting your account signs your Macs out, stops your devices working through the relay, ends every sign-in session and cancels a subscription at once, with no refund of the period you’ve paid for; Siphon at home, without the relay, carries on as before. It deletes your email, name, devices, usage counts and crash reports from our database, and your sign-in at WorkOS. We keep only what billing needs (your Stripe customer id and your subscription’s history, and Stripe keeps its invoices), and our admin audit log’s record that the account (and its email) was deleted. It can’t be undone: signing in with the same email later starts a new account.

Depending on where you live (for example the EU, the UK, Canada or California), you have these rights in law, and you can complain to your data protection authority. We store data in Canada and the United States.

Siphon isn’t meant for children under 16.

Changes

When this policy changes, we update it here and change the date at the top. If a change affects how we use data you’ve already given us, we’ll email account holders first.

Local agent sign-ins

When you choose Claude Code or Codex, Siphon runs the installed agent on your host with its own sign-in. Siphon does not copy those credentials to your iPhone or watch. Your selected agent sends messages to its model provider under your account. Switching agents can send a compact digest of previous exchanges in that thread to the newly selected agent and its provider.