DevBench is referred to in this policy as the App. The App is developed and maintained by Andrew Mastracchio (the Developer). This policy explains what information the App handles, where it is stored, and the choices available to you.
Privacy at a glance
-
Your library (apps, items, versions, builds, release notes, attachments and brand assets) is stored on your device.
-
iCloud Sync is optional and uses your private Apple iCloud account. The Developer does not operate a DevBench account or data server.
-
The App reads a project folder only when you choose one, and only to find the app’s name, icon, version, build number and branch. It does not upload your source code.
-
On Mac, the optional server for coding agents (MCP) is off until you set up an agent or turn it on, listens only on your Mac, and requires a private access token. Agents you set up in the App can make changes right away; any other agent needs your approval first.
-
There are no ads, third-party analytics, or cross-app tracking.
-
DevBench does not automatically upload its local diagnostic log or locally stored MetricKit reports. Apple may separately provide the Developer with crash, performance, and usage information according to your Apple analytics choices or as part of TestFlight.
1. Information stored on your device
By default, the App stores its information locally on your device. This includes the apps you track and their details (such as names, keys, bundle identifiers, links, App Store text and templates), your bugs, ideas, changes and tasks, their notes, checklists, release notes and resolutions, versions, builds, release history, automation rules, attachments you add (such as screenshots and crash logs), brand assets you add, preferences, and technical state needed to resume your work. The Developer does not automatically receive this information.
The App shares its local store with its widgets and its share and action extensions through an Apple App Group so those components can provide the features you request. That shared storage remains within the App’s Apple-managed container.
Item titles, app names and related details may appear in widgets, Spotlight, Siri, Shortcuts and Control Center on supported platforms. You can manage these in your device settings.
2. Optional iCloud Sync
The App asks whether to use iCloud when you set it up, and you can turn sync on or off at any time in Settings. If you turn it on, the App stores and synchronizes your library, including attachments and brand assets, through your private Apple iCloud account so it stays current across your Mac, iPad and iPhone. The App receives silent push notifications from Apple when another device has changes to sync; it does not show you notifications for them. The Developer does not operate the iCloud servers and does not have access to the data in your private CloudKit database.
Turning sync off does not necessarily delete copies that were previously stored in iCloud. You can manage iCloud app data through your Apple account and device settings, subject to Apple’s services and retention practices.
3. Project folders
You can link an app to its project folder. When you choose a folder through the system file interface, the App keeps permission to read it and reads the app’s name, icon, version, build number and branch from the project. On your other devices, the App can read the same folder from iCloud Drive after you confirm it on each device. A file from the project is copied into your library only when you, or a coding agent you connected, attach it to an item or add it to Brand Assets; it is then stored and synced like any other attachment. The App does not otherwise upload project files, and it does not transmit them to a server operated by the Developer.
4. Coding agents (MCP) on Mac
The Mac app includes an optional Model Context Protocol (MCP) server so coding agents you use, such as Claude Code, Codex or Cursor, can read and update your library. It is off until you set up an agent in Settings ▸ Coding Agents or turn on Allow Coding Agents to Connect.
-
Where it runs: The server listens only on your Mac (127.0.0.1). Every request must carry an access token that the App creates and keeps in your Mac’s Keychain. You can create a new token at any time.
-
Who can connect: Agents you set up in the App (with a copied command or settings, an install link, the agent plugin, or a project folder’s settings) can make changes right away. Any other agent can read, and the App asks for your approval before it can make changes. You can turn an agent off or forget it in Settings. An agent’s name is reported by the agent itself, so set up and approve only agents you run.
-
What agents can do: An agent that may make changes can read your apps, items, versions, builds, release notes, brand assets and attachment locations; create and update records, move them to Recently Deleted and restore them; record resolutions and release notes; attach files from an app’s linked project folder; and record builds and release steps. Only you can delete records permanently. In Settings you can have the App ask before an agent records a build, or never allow it, and turn off release steps.
-
What leaves the App: Information an agent reads is passed to that agent on your Mac. What the agent does with it, including whether it sends it to its own AI service, is governed by that agent’s and its provider’s terms and privacy practices, not this policy. Share with an agent only what you are comfortable sending to its provider.
-
Project settings: When you connect agents to a linked project folder, or link a folder after setting up an agent (you can turn this off in Settings), the App writes a DevBench entry into that project’s agent settings files (such as .mcp.json, .cursor/mcp.json and .codex/config.toml), approves DevBench for Claude Code in .claude/settings.local.json, and leaves their other settings unchanged. Setting up an agent for every project copies a command or settings to your clipboard, or opens the agent’s app so you can confirm it. If you save the agent plugin, the App writes it to a folder you choose.
The server keeps a record of connected agents and their last use on your Mac. Its activity log records which tools were used and which items were changed, but not the text agents send.
5. Exports and backups
When you export items for a coding agent, export release notes, or share items, the App writes files (which can include notes, screenshots and crash logs) to the destination you choose. While automatic backups are on, the App saves a daily backup of your library, including attachments and brand assets, in its own storage and keeps the newest few; you can also save a backup to a location you choose. Backups are not encrypted or password-protected by the App. A destination such as iCloud Drive or another file provider may store or synchronize the file under that provider’s terms. The Developer does not receive exports or backups unless you separately choose to send them.
Restoring a backup replaces the library on this device and, through iCloud Sync if it is on, on your other devices. The App saves a safety backup of the current library first.
6. Diagnostic logs and support
The App keeps a diagnostic log locally for troubleshooting, shared by the App and its extensions. It records technical events such as the App version and build, sync activity, operation outcomes and error types. Messages are scrubbed of tokens, passwords, cookies, email addresses and the query strings of web addresses, and the log is designed not to quote the titles, notes or contents of your items. Log files older than two weeks are removed automatically.
On supported Apple devices, the operating system also delivers MetricKit diagnostic reports to the App for crashes, hangs, excessive CPU use, disk writes, memory and launch problems. The App keeps up to the 50 newest reports, about 4 MB in total.
The App does not automatically upload its local diagnostic log or MetricKit reports. They leave the App only when you deliberately share or save them through the system interface. You can use the App without sharing this information.
Separately, Apple may provide the Developer with crash, performance, and usage information through App Store Connect or Xcode. For App Store versions, this generally depends on whether you have chosen to share diagnostics and usage information with app developers in your device’s Analytics & Improvements settings. TestFlight users automatically share crash reports with the Developer under Apple’s TestFlight practices. This Apple-operated reporting is governed by Apple’s terms and privacy practices.
If you contact the Developer through the support form on this website, the name, email address, device details and message you enter are sent through Web3Forms, the form service the website uses, and delivered to the Developer by email. Diagnostic information and support messages are used only to investigate issues, provide support, fix problems, improve the App, or comply with law.
7. Analytics, tracking, advertising, and sharing
The App does not use developer-operated analytics, advertising trackers, or data brokers. It does not track you across apps or websites and does not sell or rent personal information. The Developer does not maintain DevBench user accounts, advertising profiles, or a database of your App activity.
Information you voluntarily provide for support may be shared only when reasonably necessary to provide that support, operate or secure the App, comply with applicable law, or protect legal rights.
8. Retention, deletion, and your choices
-
Local App data: Retained on your device until you delete it in the App or remove the App and its data, subject to Apple device backups. Items moved to Recently Deleted stay there for 30 days unless you delete them sooner.
-
iCloud data: If sync is on, deletions synchronize to your other devices. You can also manage iCloud app data through your Apple account controls.
-
Coding agents: Turn off the server, turn off or forget an agent, or create a new token in Settings ▸ Coding Agents. Information an agent already read is held by that agent and its provider under their terms.
-
Backups and exports: Deleting an item does not remove it from earlier backups or files you exported. Delete those from their location.
-
Local diagnostic information: Removed automatically as described above, and you can clear it from the App’s log viewer.
-
Diagnostic information or messages received by the Developer: Retained only as long as reasonably necessary for the purposes described above. You may request deletion using the contact method below, subject to legal or recordkeeping obligations and information retained independently by Apple.
9. Children’s privacy
The App is a developer tool and is not directed to children. The Developer does not knowingly collect personal information from children.
10. Security
The App is designed to minimize the information available to the Developer and relies on Apple’s platform security, sandboxing, App Group, Keychain, iCloud and file permission systems. The MCP server accepts connections only from your Mac and only with its access token. No storage or transmission method can be guaranteed completely secure, but limiting collection and access reduces exposure.
11. Apple and third-party services
Features may rely on Apple services and frameworks including iCloud and CloudKit, iCloud Drive, MetricKit, Spotlight, Siri and Shortcuts, widgets and controls, system file and sharing interfaces, App Store Connect, and TestFlight. Coding agents you connect are provided by third parties. Information processed by Apple or by a coding agent and its provider is governed by their terms and privacy practices. See Apple’s Privacy Policy.
12. Changes to this policy
This policy may be updated when the App’s features, legal obligations, or privacy practices change. Material changes will be reflected in the policy, and the effective date at the top identifies the latest revision.
13. Contact
For questions about this policy, the App’s privacy practices, or a request concerning information previously provided to the Developer, use the support section at www.andrewmastracchio.com/devbench#support or email devbench@andrewmastracchio.com.