Buildshed — Last updated September 25, 2026
Buildshed does not collect, store, or transmit any personal data to external servers. There are no accounts and no sign-in.
With your permission, Buildshed reads Xcode's build logs in the DerivedData folder you choose, plus related build files there (dependency lists and compiler time traces). If you grant access to a project or repository folder, it reads file modification dates, the project's build settings, and the git reflog to find which commit a build came from. All of this is analysed on your Mac.
Only when you turn on Profiling for a project, Buildshed adds or removes a small set of compiler flags in that project's Debug build settings. A backup of the original project file is kept in the app's own container. Nothing else in your projects is modified.
Build history, timing history, folder permissions and preferences are stored locally in the app's sandbox container. This data is never transmitted externally. You can clear build history at any time in Settings.
Slowdown alerts are delivered as local notifications generated on your Mac. If you use jump to line, Buildshed sends Apple Events to Xcode on your Mac to open a file; this does not leave your device.
The optional Pro unlock is processed entirely by Apple through the App Store. Buildshed never sees your payment details; it only checks with StoreKit whether Pro has been purchased.
Buildshed does not use any third-party analytics, advertising, crash reporting, or tracking services.
Questions? Reach out at joem.dev@icloud.com.