--- title: "SubmitDiagInfo and ReportCrash: what they send to Apple, and whether to block them · Kilobat" url: "https://kilobat.app/processes/reportcrash" description: "SubmitDiagInfo sends diagnostic and usage data to Apple if you opted in, and ReportCrash saves crash reports. What they send, and how to stop it." --- Diagnostics, analytics and ads # What is SubmitDiagInfo? `ReportCrash` saves crash reports on the Mac. `SubmitDiagInfo` sends diagnostic information to Apple, but only if you opted in to sharing analytics. Process: `SubmitDiagInfo` · Also seen as: `ReportCrash` · Made by Apple · Applies to: macOS 14 Sonoma and later. Checked on macOS 27.2. · Checked: 1 November 2026 ## Short answer Part of macOS. ReportCrash saves crash reports on the Mac. SubmitDiagInfo sends diagnostic and usage information to Apple, but only if you opted in. Safe to block Blocking diagnostic uploads prevents Apple from receiving reports. To stop automatic analytics uploads, turn off Share Mac Analytics instead. Path `/System/Library/CoreServices/SubmitDiagInfo` `/System/Library/CoreServices/ReportCrash` launchd label `com.apple.SubmitDiagInfo` `com.apple.ReportCrash` `com.apple.ReportCrash.Root` Signing identifier `com.apple.SubmitDiagInfo` `com.apple.CrashReporter` ## What it is The `ReportCrash` man page says that it analyzes crashing processes and saves a crash report to disk. launchd starts it when a crash occurs. The `SubmitDiagInfo` man page says that it runs periodically. If the user opted in, it sends recent diagnostic information to Apple that has not been sent yet. The man page says that reports can include crashes, freezes and kernel panics. They can also include events, such as whether waking the Mac worked, and usage of Apple and third-party software. It also says that the information is collected anonymously, and that it cleans up reports older than a month. ## Why it uses the network - **Diagnostic uploads.** With Share Mac Analytics on, `SubmitDiagInfo` sends crash, hang and usage information to Apple. - **Reports that you send.** When you click Report after a crash, the report goes to Apple. ## How much is normal If you share analytics, the uploads are small and periodic. If you didn't opt in, the man page says that no information is sent automatically. `ReportCrash` itself writes to disk. Its man page doesn't describe network use. ## When it uses a lot, and why - **Many crashes.** An app that crashes again and again makes many reports. With sharing on, they all go up. - **Opting in after a crash.** The man page says that after you send a report by hand, macOS offers to share automatically. Saying yes starts the periodic uploads. ## Is it safe to block? Safe to block Blocking diagnostic uploads prevents Apple from receiving reports. To stop automatic analytics uploads, turn off Share Mac Analytics instead. What breaks if you block it - Apple stops getting your diagnostic reports, which help it fix bugs. - Developers who receive reports through Apple, with Share with app developers on, stop getting yours. Blocking means a firewall rule that refuses its connections. Don’t quit or disable a macOS process to save data: macOS starts it again, and other features depend on it. ## Reduce its use 1. Choose Apple menu › System Settings › Privacy & Security. Click Analytics & Improvements. 2. Turn off Share Mac Analytics. Turn off Share with app developers too, if you want. 3. Keep crash reporting itself. The reports on your Mac help when you contact a developer. ## See how much it uses 1. Open Console from Applications › Utilities. The man page says that reports eligible for sending are listed there. 2. In Terminal, see app crash reports on this Mac. ``` ls ~/Library/Logs/DiagnosticReports ``` ## With Kilobat 1. In the Kilobat app list, search for `SubmitDiagInfo`. Its row shows the live rate and what it moved today. 2. In Connections, click the ⓘ button on one of its rows. The popover shows this page’s short answer, without going online. 3. In Terminal, ask the same question. Add `--json` for scripts and agents. ``` kilobat explain 'SubmitDiagInfo' ``` 4. Show its traffic over one day. ``` kilobat bandwidth 'SubmitDiagInfo' day ``` 5. Through MCP, an AI agent asks `explain_connection` with the process name. It gets the same facts. The live view and the explanations are free. History in the app needs Kilobat Pro. Blocking needs Pro and the network filter: see the [network filter](https://kilobat.app/docs/blocking#filtering), [Protection](https://kilobat.app/docs/blocking#protection) and the [hotspot data saver](https://kilobat.app/save-hotspot-data). ## Questions **Where are crash reports on my Mac?** Console lists them. App reports are in `~/Library/Logs/DiagnosticReports`. **Does SubmitDiagInfo send data if I said no?** The man page says that it sends nothing automatically unless you opted in. ## Sources - ReportCrash(8) and SubmitDiagInfo(8), man pages installed with macOS 27.2 - launchd property lists com.apple.SubmitDiagInfo and com.apple.ReportCrash, macOS 27.2 - [Apple Support: Share analytics information from your Mac with Apple](https://support.apple.com/guide/mac-help/share-analytics-information-mac-mh27990/mac) Checked on 1 November 2026. ## Related - [analyticsd](https://kilobat.app/processes/analyticsd): Part of macOS. It collects diagnostics and usage data on the Mac for users who opted in to sharing analytics. - [adprivacyd](https://kilobat.app/processes/adprivacyd): Part of macOS. It manages advertising privacy for Apple's own ads in the App Store, Apple News and Stocks, including your opt-out from personalized ads.