What leaves your Mac
There are no analytics and no crash reporting.
What stays on your Mac
- Conversations, history and their screenshots, in Mobster’s journal, readable only by you. Deleting a conversation deletes its tasks and their screens.
- What Mobster remembers, in your words, in one file readable only by you. Nothing is saved until you choose Remember, and it never remembers passwords, codes or card numbers. Memory
- Files you attach. A task sends only what it reads from them. A file you add and no task uses is deleted within a day. Files
- Your notifications, if you use triggers. Mobster reads them on this Mac, with Full Disk Access, to check them against your triggers. They never leave your Mac, except what a trigger sends where you told it to. Mobster keeps no notification’s text. Notification triggers
- Your Messages, when you ask who’s waiting on you. Mobster reads
chat.dband your Contacts on this Mac, read-only, and drafts replies with Apple’s on-device model. No message text goes to a cloud model. The task keeps the names, the last message and the draft you see on the card. Who’s waiting on me - App X-ray’s maps, when you map an app. App X-ray reads the text of each screen it opens in the app you chose, with no model, and keeps a thumbnail of each screen. Keys, card numbers and codes it reads are masked before they are stored.
map.json,report.htmland the thumbnails are written toxray/apps/<bundle ID>/<date>-<time>/in Mobster’s data folder, a folder only you can open, and nothing is sent anywhere. The task keeps the screens’ names and thumbnails like any task, and deleting the task deletes those; the folder stays until you delete it. X-ray - Network X-ray reports, when you record your phone. What it reads is below. The report stays in Mobster’s data folder.
- Your API key, in the Mac app’s env file or yours.
What Network X-ray reads
Network X-ray records one iPhone’s network traffic when you press Network X-ray or runmobster xray network. It uses Apple’s packet capture service on the phone, which asks only that the phone trusts this Mac.
- It reads each connection’s hostname (from a DNS answer, the server name in a TLS or QUIC handshake, or an HTTP Host header), the process that made it, its sizes and its times. Every name passes Mobster’s secret filter before it reaches a report, a task or a log.
- It never keeps a page, a URL path, a header other than Host, a cookie, a body or an address. It decrypts nothing. Traffic on your local network counts as one total with no names.
- The capture file holds the first 256 bytes of each packet, more for DNS and the start of a TLS or QUIC handshake, which is where the hostname is. After the packet headers (54 to 94 bytes for TCP over IPv4 or IPv6), that leaves 160 to 200 bytes of payload a packet. Mobster deletes the file as soon as it has been read.
--keep-capturekeeps it in the same folder, readable only by you. - The report is
report.html,report.mdandnetxray.jsoninxray/network/<time>/in Mobster’s data folder, readable only by you. The task the Mac app makes holds the two tables and a note. Nothing is sent to a model, to Mobster or to anyone else. - Over the cable only. iOS offers the capture service on USB, and refuses it over Wi-Fi, so nothing it records crosses your network.
- Only the Mac app can start a recording through the local API: an API token alone can’t. Network X-ray is not an agent tool or an MCP tool, so no hostname reaches a model.
- The report’s task stays on this Mac. Mobster makes no share link of it, sends it to no destination and leaves it out of a feedback report. The local task API shows it only to the Mac app, so an agent over MCP or Mobster Remote can’t read it.
Checks and coding agents
- A launch-only check, or a check your coding agent drives without a key, sends nothing anywhere.
- A check’s failure evidence, the app’s log and its crash report, stays in the run folder on your Mac with the frames. Each line goes through the secret filter before it’s written. Mobster sends it nowhere; over MCP, the result your coding agent reads carries the log lines around the failure and the crash’s frames. Logs, crashes and video
- A check with steps sends each screen’s image and accessibility text to the provider whose key it runs on.
- Runs from a real iPhone are written to Mobster’s data folder unless you name another, so your phone’s screens never land in a repository.
Your Mobster account
Mobster for Mac signs in with Apple, Google, GitHub or a code sent to your email (Your Mobster account). Supabase runs the sign-in and holds the account, in its US East (N. Virginia) region.- What the account holds: your email address, which ways you’ve signed in, and a random user id. From Apple, the email Apple gives Mobster (with Hide My Email, a relay address) and Apple’s id for you. From Google, your Google email, Google’s id for you, and the name and profile photo address on your Google account. From GitHub, your primary verified email, your username, GitHub’s id for you, and the name and avatar address on your profile. With an email code, only the address. Sign-ins with the same verified email are one account. For each Mac: its name, a hashed id made on the Mac, and when it joined, last checked in and was removed. For each purchase: the plan, its status and when it ends, and the Stripe customer that paid. For a free trial: when it started and ends, and the keyed hashes that keep it to one per Mac, iPhone and sign-in, kept after the account is deleted so the trial stays used.
- What it never holds: a password, anything else from your Apple, Google or GitHub account, your tasks, your screens, your AI key, or anything from your iPhone.
- On your Mac: your sign-in in the Keychain, and your account’s details and a signed copy of your plan in
account.json, readable only by you. - Payments: Stripe takes the payment and keeps your card. Mobster never sees your card number.
Shared links
Nothing is shared unless you share it. Share on a result (Share a result) uploads one page to Mobster’s account service and gives you a link,https://mobster.dev/s/<id>, with an id of 128 random bits.
- What’s uploaded: the page you previewed, nothing more: its title, the answer, the cards you kept and their sources. Names and handles read “Person 1”, “Person 2” unless you show them, and screens are left out unless you include them. Mobster also keeps which account made it, its size, a SHA-256 hash, and when it was made, expires and was turned off.
- Where: a private Supabase Storage bucket and the account database, US East. The account service (api.mobster.dev, on Vercel) serves it.
- Who sees it: anyone with the link, without signing in. It’s never listed, and every answer says
X-Robots-Tag: noindex, nofollow, noarchive, the page has the same robots meta tag, and robots.txt disallows/s/. A pasted link shows its title and no preview. - How long: 1, 7, 30 or 90 days, or until you turn it off; 30 days by default. Turning it off stops it at once and deletes the page. An expired page is deleted within a day, and the record of a link that ended is deleted 30 days later.
Feedback you send
Nothing is sent unless you send it. Send feedback shows you everything first.- What’s sent: what you wrote (with passwords, codes, card numbers and keys masked), the reply-to email, Mobster’s and macOS’s versions, your iPhone’s model, iOS version and connection, and the task’s id when it’s about one. A screenshot of the Mobster window and the diagnostics bundle only if you add them.
- Where: the account database and a private Supabase Storage bucket, US East, through the account service (api.mobster.dev, on Vercel). A summary goes to a staff-only Discord channel, with links to the screenshot and diagnostics that stop working after 30 days.
- How long: the screenshot and diagnostics 90 days; the report until you ask us to delete it or delete your account.
Mobster Remote
Mobster Remote is off until you turn it on. Then an assistant you allow, such as Claude or Poke, can hand tasks to your iPhone through Mobster’s relay at remote.mobster.dev.- The relay passes tasks along and keeps none of them. A task’s text and its answer pass through the relay’s memory and are never written down or logged. Encryption ends at Cloudflare’s edge, so that text is in Cloudflare’s memory while it passes. No app ever gets a picture of your screen.
- What the relay keeps, for each Mac: the apps you allowed (name, domain, permissions, which phone, when), hashes of their tokens and keys, your phones’ names and states under ids made on your Mac, requests to connect until a day after they end, daily call counts for 30 days, and a note of each removed app for 90 days. Its logs hold the route, the status, the time taken, the tool’s name and sizes, never bodies, emails, names, task text or answers. Removing a Mac from your account deletes all of it.
- Client approval links (Ask your client first): the relay keeps a hash of each link and when it ends. The post passes through it from your Mac each time your client opens the link, and their answer and note pass back to your Mac, never written down. The page asks search engines not to index it and loads no outside script.
- What it reads from your account: your Macs, to list them on the connect page, and whether you have a plan. It writes nothing to your account. The connect page signs you in to Supabase, reads who you are and signs out again, keeping no Supabase token.
- What stays on your Mac: tasks from apps, in the sidebar like any other conversation; the key your Mac connects with, in the Keychain; your phones’ UDIDs; and the screen.
- The assistant keeps what it gets, under its maker’s rules: Anthropic’s, OpenAI’s, Poke’s, xAI’s.