Yuki
Privacy

Private by design — and you can prove it.

Most apps ask you to trust their privacy policy. Yuki is built so we can't see your data in the first place — and so you can verify that yourself.

Your code, prompts, and files never leave your machine. The only thing Yuki shares between your devices is your agent's status — and even that travels through your own network or your own iCloud, never through us.

What stays on your machine

Everything you actually work on — your code, your prompts, your files, your terminal output, the names of your projects — stays on your machine. To tell whether your agent is busy, waiting, or idle, the Helper reads its activity locally on your Mac and derives just that coarse status. It never sends, stores, or shows your code, prompts, file contents, commands, or output.

What leaves your machine — and where it goes

When your agent's state changes, Yuki sends a tiny status update to your other devices. There are two paths, and both are private:

  • On your local network (the default). Your devices talk directly to each other over your own Wi-Fi/LAN. The update never leaves your home or office network.
  • Through your own iCloud (the fallback). When your devices aren't on the same network, the update is written to Apple's CloudKit private database — which lives in your iCloud account. We run no server in the middle, so it never passes through anything we control.

Every update is the same tiny payload — these six fields, and nothing else:

FieldWhat it is
stateworking · waiting · idle · done · error
activitya coarse label — reading · writing · running · planning · thinking (or none)
agentwhich tool — claude-code or codex
sessionIdan opaque id (e.g. "helper") — not a name or path
timestampwhen the state changed
ida random per-event identifier — carries nothing of yours

That is the whole payload. No code. No prompts. No file names or contents. No command text. No output. Ever.

Your private iCloud also holds one housekeeping record: a random pairing key the Helper generates so your own devices can connect without typing anything. It contains nothing about you or your work, and — like everything else — never leaves your iCloud account.

What the Helper sets up on your Mac

Two small conveniences, both visible and both reversible: the Helper starts at login, so the sensor is already running when you sit down to code; and it asks Claude Code to send it a tiny local ping when your agent stops and waits for you — the one moment that never shows up in the logs it reads. Everything involved stays on your Mac. The menu bar turns each off, and Uninstall removes both completely.

What we don't have — and never will

  • No server or backend of our own. Nothing for us to breach, log, hand over, or sell.
  • No Yuki account. You sign up for nothing. Sync uses the iCloud account already on your device.
  • No ads. Not now, not later.
  • No analytics, no telemetry, no crash reporting, no "anonymous usage stats."
  • No A/B testing. The app doesn't experiment on you.
  • No third-party code — anywhere. The apps and the Helper are native Swift with zero third-party dependencies, built only on Apple system frameworks. Nothing can phone home, because there is nothing but our code and Apple's.

You don't have to trust us — check

The Mac Helper is open source. You can read exactly what it sees and sends before you ever run it:

  • Read it on GitHub — the Helper is small and has zero third-party dependencies, so every line you'd audit is ours.
  • Confirm for yourself that the only things it talks to are your local network and Apple's CloudKit — there is no other endpoint in the code.
  • Build it yourself, or watch its network activity, if you'd rather verify than take our word.

Audit the Helper on GitHub ↗

In Apple's terms

Because we collect nothing, Yuki's App Store privacy label is “Data Not Collected.”

Questions

Privacy questions: [email protected]. If you're a developer, the technical version of this page lives in the Helper repo.

Last updated 2026-07-02