Privacy policy
Privacy
Effective 9 October 2026
The short version
Jackie shows and steers the coding agents on your own computers. Your phone talks directly to the Jackie agent on each computer you link, over your own Tailscale network. Jackie’s servers are not in that path.
Your agents (Claude Code, and Codex or a local model if you choose them) run on your computers under your own accounts. Our relay only forwards Live Activity updates for the lock screen, sealed so it can’t read them.
There are no analytics, no advertising, no tracking, and nothing is used to train a model by us.
1. On your iPhone
Jackie keeps the list of computers you linked, a key for each (in the iPhone’s Keychain), and your settings. It does not keep your code, your sessions or your conversations; it reads them from your computers when you look.
Jackie used to be a personal planner. If you used that version, its data (tasks, routines, weekly goals, notes and old chats) is deleted from the iPhone once, the first time this version opens, along with the AI keys and sync keys it kept. Nothing of it is sent anywhere.
2. Your computers, when you link one
Linking a computer means installing the Jackie agent on it and scanning the one-time code it shows. From then on your phone talks to that agent directly, at the address your Tailscale network gives it. We do not run a server between them. What passes between the phone and the computer:
- What the computer shows the phone. Its projects and their status, the agents running there and their transcripts, the Lead’s and Foremen’s plans, git state and pull requests, usage of your AI subscriptions, alerts, the terminal you open, and the files you browse or open. The agent never lists, serves or writes into keys, credentials, shell history or its own folders.
- What the phone tells the computer. The actions you take: start a session or a Worker, send a prompt, tell the Lead or a Foreman what to do, Allow or Deny a step, approve a merge, interrupt, and files you send it.
- Your agents. The Lead, Foremen and Workers are Claude Code sessions (or Codex, or a local model) on your computer, under your own accounts. What they read and send to their model provider is governed by that provider’s terms, not ours. Workers run in a sandbox limited to their own copy of the project, and risky steps wait for your Allow.
- Chat. Each message runs Claude Code on the computer you chose, under your own Anthropic account, with your projects as context. Claude can search and fetch from the web, read files in your projects, and read your Google Calendar if you added it as a connector to your own claude.ai account. It cannot change anything. Chats are stored on that computer.
Notifications and Live Activities. When an agent needs you, an approval waits, or a Lead run progresses, the agent sends a push through Expo’s push service. The title, text and data are encrypted with a key your phone gave the computer when you linked it. Apple and Expo see “Jackie” and a generic line; your phone opens the rest. For Live Activities, our relay at api.jackie.amory.dev (hosted on Vercel, with storage at Upstash) holds your phone’s push-to-start token and a hash of each computer’s key. It sees sealed content, a computer identifier and a run identifier, never a project’s name.
Unlinking a computer stops your phone talking to it. It cannot erase what the agent already keeps on that computer, such as chats, session state and its history of agent runs. Remove those on the computer itself.
Other services Jackie uses
- Apple. Purchases, renewals and refunds go through the App Store. See Apple’s privacy policy.
- RevenueCat tells the app whether your subscription is active. It receives your App Store receipt and a random identifier the app creates. It does not receive your name, email or anything from your computers. See RevenueCat’s privacy policy.
- Tailscale carries the connection between your phone and your computers. You run it under your own account. We do not see that traffic, and Tailscale’s terms apply to it. See Tailscale’s privacy policy.
- Expo push and updates. The push service delivers sealed notifications from your computers (see section 2). The app also checks Expo’s update service for fixes. That check sends the app version, platform and an installation identifier, and no content. See Expo’s privacy policy.
What we don’t do
- No analytics or usage tracking inside the app.
- No advertising, and no tracking across other apps or websites.
- No selling or sharing of your data.
- Nothing is used by us to train any model.
- No crash-reporting SDK. If you test Jackie through TestFlight, Apple may share crash reports with us under its own terms.
Permissions
- Camera: only to scan the one-time QR code that links a computer.
- Face ID: before you allow a command, approve a merge or open a terminal on a computer. Apple’s Face ID data never reaches Jackie.
- Notifications: to tell you when an agent waits on you, an approval is ready, or a run finishes.
Each one is optional, and each can be withdrawn in iOS Settings at any time.
This website
If you join the waitlist, we keep the email address you typed so we can tell you when Jackie launches. It is held by Resend, our email provider, and used for nothing else. Every message has an unsubscribe link, and asking us to delete your address removes it.
Children
Jackie is not intended for children under 13, and we do not knowingly collect anything from them.
Your rights
Your data is on your own computers, where you can erase it yourself. For anything we hold (a Live Activity registration, a waitlist email), email us and we will delete it. Depending on where you live you may have further rights under the GDPR, UK GDPR or CCPA, and we will honour them.
Changes
If this policy changes, the effective date at the top changes with it. A change that affects how your data is handled will be flagged in the app before it takes effect.
Contact
Questions about privacy, or a request about your data: jackie@amory.dev