---
title: "What is calaccessd on a Mac? Why it uses the network and whether to block it · Kilobat"
url: "https://kilobat.app/processes/calaccessd"
description: "calaccessd is the macOS calendar data process. What it does for Calendar, why it uses the network, and what breaks if you block it."
---

# What is calaccessd?

`calaccessd` is the calendar data process of macOS. Its man page says the system uses it to coordinate access to calendar data and to post calendar notifications.

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

I want to know what calaccessd is doing on my Mac and whether its network use is normal. Read https://kilobat.app/processes/calaccessd.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: `calaccessd` · Made by Apple · Applies to: Checked on macOS 27.2. · Checked: 7 November 2026

## Short answer

Part of macOS. It coordinates access to calendar data and posts calendar notifications. Calendar account sync can show under it.

Block with care

Blocking it can stop calendar alerts and account refresh. Remove or pause a calendar account instead.

Path

`/System/Library/PrivateFrameworks/CalendarDaemon.framework/Support/calaccessd`

launchd label

`com.apple.calaccessd`

Signing identifier

`com.apple.calaccessd`

## What it is

The program is `calaccessd` in the CalendarDaemon framework, signed by Apple. Its launchd label is `com.apple.calaccessd`. It is a per-user agent that launchd starts on demand.

Its launchd file registers a Mach service named `com.apple.CalendarAgent`, and others for iCal notifications and for Spotlight calendar data.

The file lists launch events for database changes, time zone changes and a significant time change. It lists scheduled activities named `analytics`, `databasecleanup`, `changetablecleanup` and `attachmentcleanup`.

Apple's Calendar guide says Calendar can manage events from several accounts, such as iCloud or Google, in one app. It covers sending and receiving invitations, refreshing calendars and managing notifications.

The man page says there are no options and users should not run it. Apple does not say that calaccessd carries the account traffic. The Mach service name suggests it, but Apple does not state it.

## Why it uses the network

- **Calendar accounts.** Apple says Calendar works with accounts like iCloud and Google. Refresh and sync for those accounts needs the network.
- **Invitations and shared calendars.** Apple says you can send invitations and share calendars. These use the network.
- **Notifications.** The man page says calaccessd posts calendar notifications. Alerts for events work through it.
- **Maintenance.** The cleanup activities work on the local database. Apple does not say they use the network.

## How much is normal

Short bursts when you refresh or change a calendar are normal.

Account sync is small for a normal calendar. Apple gives no figure.

A constant flow suggests a calendar that changes often, such as a busy shared one.

## When it uses a lot, and why

- **Adding an account with a large calendar.** The first sync downloads past and future events.
- **Subscribed or shared calendars that change often.** Each change reaches every device.
- **Attachments.** The launchd file names an attachment cleanup activity, so attachments exist. Large ones add to sync.

## Is it safe to block?

Block with care

Blocking it can stop calendar alerts and account refresh. Remove or pause a calendar account instead.

What breaks if you block it

- Calendar accounts stop refreshing, so events change late or not at all.
- Event alerts may not appear.
- Invitations may fail to send or arrive late.

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 Calendar and review which calendars are shown. Hide the ones you do not use.
2. Choose Apple menu › System Settings › Internet Accounts. Turn off Calendars for accounts you do not need.
3. On a hotspot or a capped plan, turn on Low Data Mode. Choose Apple menu › System Settings › Wi-Fi. Click Details next to the network, then turn on Low Data Mode.
4. Do not quit `calaccessd` in Activity Monitor. macOS starts it again.

## See how much it uses

1. Open Activity Monitor from Applications › Utilities. Click Network.
2. Type `calaccessd` 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 'calaccessd' -P
   ```

## With Kilobat

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

   ```
   kilobat bandwidth 'calaccessd' 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).

## Hosts it contacts

Apple and the maker document these hosts for this feature. A process can also contact others; Kilobat’s Connections tab shows what it actually opens on your Mac.

- [*.icloud.com](https://kilobat.app/hosts/icloud-com): Apple's iCloud domain. Apple lists *.icloud.com for iCloud services; specific hosts under it have their own pages.

## What isn’t documented

Apple does not document which hosts `calaccessd` contacts. Account hosts depend on the provider.

Apple does not describe the analytics activity in the launchd file or what it sends.

Apple does not say whether the cleanup activities use the network.

## Questions

**Does calaccessd send my events to Apple?**

Apple does not document that. Its man page says it coordinates access to calendar data on the Mac.

**Why is it active when Calendar is closed?**

Alerts and refreshes run in the background. The launchd file lists database and time events that start it.

**Is calaccessd a virus?**

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

## Sources

- calaccessd(8), man page installed with macOS 27.2
- launchd property list com.apple.calaccessd, macOS 27.2
- [Apple Support: Calendar User Guide for Mac](https://support.apple.com/guide/calendar/welcome/mac)
- [Apple Support: Change which apps sync and store data with iCloud](https://support.apple.com/en-us/118225)

Checked on 7 November 2026.

## Related

- [remindd](https://kilobat.app/processes/remindd): Part of macOS. It runs Reminders data, alerts and sync. Apple says the full Reminders features need updated iCloud reminders.
- [contactsd](https://kilobat.app/processes/contactsd): Part of macOS. It manages the contacts database and background tasks for apps that use the Contacts API. Account sync can show under it.
- [cloudd](https://kilobat.app/processes/cloudd): Part of macOS. It syncs the iCloud data of apps that use CloudKit, so its traffic belongs to those apps.
- [Use Low Data Mode on a Mac](https://kilobat.app/guides/low-data-mode-mac)
