Understand what happens to your data
Know what stays on your devices, what a feature sends, and how to control sharing and diagnostics.
Your Mac holds the workspace and runs your coding agents. Connecting a device, using a provider, or publishing a result introduces a specific data flow. Local storage does not mean that every optional action stays on-device.
On your Mac
Push keeps tracked work, threads, recordings, files, settings and local recovery data on the host Mac. Your coding agents also keep their own conversation history. Push can retain local conversation history when an agent removes its own older records.
Review Settings → Workspace → Your data for the local inventory and disk-encryption status. Local data and your backups need the same care as other project files. Purged session history → Clear purged history removes the retained history described by that control; read its scope before confirming.
What leaves your Mac
| Feature | What can leave | Your choice |
|---|---|---|
| Coding agents | Your requests, tool results and context sent to the model providers you configured. | Your runtime, model, credentials and tools. Provider policies apply. |
| Account and discovery | Account identity and workspace/device directory information. | Sign in to connect devices or collaborate. This directory is not a cloud copy of your workspace. |
| Remote access | Work text, comments, terminal output and files requested by an admitted device. | Account, workspace, folder and device access. See connections. |
| Slack | Requests and attachments sent in Slack, plus answers and files returned to the thread. | Connect Slack and choose who may act. Slack retention applies to its copies. |
| Recording transcription | Recording audio and relevant transcription context sent using your OpenRouter key. | Configure the key and request transcription. Provider policies apply. |
| Public links | The selected published item, plus title and item kind used in its preview. | Explicit publishing, expiry and revocation controls. |
| Updates | App version and ordinary connection metadata needed to check and download updates. | Update controls in Push. |
| Diagnostics | The low-detail product and crash information described below. | The diagnostics or telemetry setting. |
Agent-provider traffic uses your configured runtime and provider account. If you ask an agent to use local documents or context, relevant content can be included in its provider requests. Review the tools and account used for sensitive work.
Telemetry
The Mac's Settings → Permissions → Send anonymous telemetry controls its low-detail usage events and crash/hang reporting. Usage events describe actions such as opening a terminal, rather than recording terminal contents, file contents or work text. The control takes effect at the next launch.
The iPhone's optional diagnostics include app/device information, performance timings and crash details. Reports can include a pseudonymous workspace identifier associated with your workspace; they should not be described as wholly anonymous. Voice audio, task text, file contents and terminal contents are not attached as diagnostic content, and session replay is off.
On iPhone, use Settings → Manage → Privacy. Depending on the app version, the control is named Share Diagnostics or Share Anonymous Crash Reports. Changes take effect at the next launch.
What leaves your iPhone
Account and device information supports sign-in and discovery. Connected workspace requests send work, comments, terminal input and selected files between the phone and Mac. Notification registration and delivery use Apple's notification services. Optional diagnostics follow the setting above.
For voice capture, the phone can transcribe locally. If you configure OpenRouter processing, audio, text and relevant context or attachments can go to that provider. See what happens to your audio.
Captures can wait locally until the Mac reconnects. Check sync before removing the app or deleting your account: unsynced material may exist only on the phone. The workspace directory and relay are not an iCloud copy or managed workspace backup.
Public links
Anyone with an active public link can view the selected published item. Chat and social preview services can fetch its title and item kind. Publishing a file is separate from keeping it in a Push Session's Artifacts.
The trusted Push link frame supplies preview metadata; the published content is served on a separate content domain. Revoked, expired or unavailable links use a generic preview and stop serving the unavailable publication. Public share pages are marked not to appear in search indexes.
Review Publishing → Published for active links. Use the offered revoke or stop-publishing action when access should end. Revocation cannot erase copies someone already downloaded or cached. Check whether source updates are included before assuming a local edit changed a published item.
Leaving
Signing out, disconnecting a device, deleting an account and deleting a local workspace have different effects. Read account actions, export or back up what you need, and revoke public links separately.
See the Privacy Policy, permissions and hosting responsibilities for related choices.