What is cloudtelemetryd?

cloudtelemetryd is a launch daemon for handling system-wide telemetry events. That is the text of its man page.

Fix this with your agentCopies a prompt for Claude Code, Codex or any agent that can use Terminal.

I want to know what cloudtelemetryd is doing on my Mac and whether its network use is normal. Read https://kilobat.app/processes/cloudtelemetryd.md and work through it with me. Install the Kilobat CLI if it’s missing: brew install seifip/kilobat/kilobat. Run the guide’s Terminal and kilobat checks yourself and tell me what you find. List the steps only I can do. Ask before you change any setting.

Process: cloudtelemetrydAlso seen as: rtcreportingdMade by AppleApplies to: Checked on macOS 27.2.Checked: 7 November 2026

Short answer

Part of macOS. Its man page says it handles system-wide telemetry events. Apple lets you stop sharing Mac analytics in settings.

Safe to block

Blocking it only affects telemetry. Turning off Share Mac Analytics is the supported route.

Path
/System/Library/PrivateFrameworks/CloudTelemetry.framework/Support/cloudtelemetryd /usr/libexec/rtcreportingd
launchd label
com.apple.cloudtelemetryd com.apple.rtcreportingd
Signing identifier
com.apple.cloudtelemetryd com.apple.rtcreportingd

What it is

The program is cloudtelemetryd in the CloudTelemetry framework, signed by Apple. Its launchd label is com.apple.cloudtelemetryd. It is a system daemon with one Mach service.

The man page says there are no options and users should not run it.

Apple's analytics page says that if you opt in, your Mac can send crash reports, kernel panic details, event outcomes and usage data. Data goes over your internet connection. If you are offline, it is saved and sent later. Your Mac deletes analytics data after one month.

Apple does not say that cloudtelemetryd is the process that sends this data. The page names SubmitDiagInfo as the entry to look for in Console.

Apple says you can turn sharing off in System Settings › Privacy & Security › Analytics & Improvements.

rtcreportingd is a system daemon at /usr/libexec/rtcreportingd, signed by Apple, that runs as root. Its man page is titled Diagnostics and Usage Reporting. It says the daemon collects diagnostics and usage telemetry locally for users that opted in. It does not say that the daemon sends data.

Why it uses the network

  • Telemetry events. The man page ties the daemon to system-wide telemetry events.
  • Opted-in analytics. Apple says analytics are sent only if you opt in. Apple does not tie this to the daemon.

How much is normal

Small, rare messages are expected. Apple gives no figure.

Apple says reports are sent after an app quits unexpectedly or after a restart caused by an error.

A steady, large flow is not described by Apple.

When it uses a lot, and why

  • Many crashes. Apple says crash reports are sent after each event.

Is it safe to block?

Safe to block

Blocking it only affects telemetry. Turning off Share Mac Analytics is the supported route.

What breaks if you block it

  • Telemetry events are not sent.
  • Apple does not say that anything the user sees depends on it.

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. Open System Settings › Privacy & Security › Analytics & Improvements. Turn off Share Mac Analytics.

  2. Turn off Share with app developers on the same page.

  3. Open Console and choose Mac Analytics Data to see what your Mac has queued.

  4. Do not quit cloudtelemetryd in Activity Monitor. macOS starts it again.

See how much it uses

  1. Open Activity Monitor from Applications › Utilities. Click Network.

  2. Type cloudtelemetryd in the search field. The Sent Bytes and Rcvd Bytes columns show what it moved since it started.

  3. In Terminal, watch only this process. Press d to show the change per second, and q to quit.

    nettop -p 'cloudtelemetryd' -P

With Kilobat

  1. In the Kilobat app list, search for cloudtelemetryd. 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 'cloudtelemetryd'
  4. Show its traffic over one day.

    kilobat bandwidth 'cloudtelemetryd' 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, Protection and the hotspot data saver.

What isn’t documented

Apple does not say which events cloudtelemetryd handles.

Apple does not say which hosts it sends to.

Apple does not say how the two daemons differ from analyticsd.

Questions

Does cloudtelemetryd send my files?

Apple does not say so. Its man page says it handles telemetry events.

Does turning off Share Mac Analytics stop it?

Apple says the setting controls whether analytics are sent. Apple does not name this daemon.

Is cloudtelemetryd a virus?

No. It is signed by Apple and has a man page.

Sources

Checked on 7 November 2026.